Re: zynjacku package - build log

[Asheesh Laroia]

On Wed, 7 Apr 2010, Jakub Wilk wrote:


* Asheesh Laroia , 2010-04-05, 23:05:

I just trying my package zynjacku get uploaded.
My sponsor asked me to show build log to some python expert.
Can someone on list review attached build log please?


Thanks for posting the build log!

Dear debian-python, as a prospective mentor, here are the things I'm 
concerned about in the build log:


First and foremost, it talks about Python 2.5 left and right. I don't want 
to slow down a Python 2.6 transition.


...well, actually, I think the rest of it looks fine. But would one of you 
Debian Python experts let me know if the Python 2.5 mentions are a red 
flag, and if so, how we should avoid them?


2.5 is still(!) the default version in Debian, so it's quite natural that it 
appears in the build log. I've rebuild zynjacku in an environment with 2.6 as 
default and it appears to build successfully, so there's nothing to worry 
about w.r.t. to Python 2.6 transition. On the other hand, it's always 
recommend to build Python extensions for all supported Python versions 
(rather than only for the default one).


Thanks! The package seems pretty good, and I think I will sponsor it. Do 
you see anything else possibly troublesome as far as its Python packaging?


If not, I'll just upload it! (-:

-- Asheesh.

--
Your love life will be happy and harmonious.


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/alpine.deb.2.00.1004140051070.5...@rose.makesad.us

How to properly provide packages for python3.x

[Sandro Tosi]

Hello,
I've seen that some modules/extensions are starting to ship
python3- packages, thus allowing to be installed for python3.x
interpreter. Well, I didn't see a discussion about that so I'm
starting one right away.

In particular I'd want to ask:

- was there a discussion and I simply don't remember about it?
- do the python helper tools support python3 packages?
- how to do that properly? simply build with python3.x and then ship
the /usr/lib/python3.x/ dir?
- shouldn't we just try to organize how to do that before creating
such packages and then impose their structure/method because "we are
already doing it this way" (in particular because the python
maintainer was the first to ship py3 mod/ext for his packages)?

Thanks & Regards,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


-- 
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/n2z8b2d7b4d1004132220z3f62ed5fgd937e24eb2ef0...@mail.gmail.com