building a module for 2 versions

[Jamie Wilkinson]

I've had a request from a user to build my pymad package for python2.3, but
I don't want to get rid of the version built for 2.2 yet.  I can see a way
to build a binary package for each source version, but it's a bit ugly, and
I'm wondering if anyone has any nice methods of building python modules for
multiple versions of python.

-- 
[EMAIL PROTECTED]   http://people.debian.org/~jaq

Re: building a module for 2 versions

[Jamie Wilkinson]

This one time, at band camp, Ben Burton wrote:
>Specifically, in debian/rules you replace your calls to $(PYTHON)/setup.py
>with three separate calls running three different versions of python (or
>however many versions you want to support).  There's also calls to
>debian/pathmangle.sh to fix the interpreters called by the various
>runtime scripts.

Cool, thanks.

-- 
[EMAIL PROTECTED]   http://people.debian.org/~jaq

Re: Python 2.3 transition status query: pyvorbis, python-pmw, python-id3, pymad

[Jamie Wilkinson]

This one time, at band camp, Tommi Virtanen wrote:
>>  Hi. What's the status of the python 2.2->2.3 transition of the
>>  following packages:

>>  pymad

When I get a round tuit.  I plan on building new packages next weekend, I'm
currently engrossed in gnucash as it's tax time.

-- 
[EMAIL PROTECTED]   http://people.debian.org/~jaq