Comment 23 for bug 293082

Revision history for this message
Tim Burrell (tim-burrell) wrote :

That sounds preferable to me too.

I don't have time to look into it just now, but I can take a look later. I don't think it should be a significant change. I keep wondering if any other packages are dealing with this right now as well?

From the threads here: http://lists.debian.org/debian-python/2008/03/msg00034.html

and here: http://lists.debian.org/debian-python/2008/03/msg00033.html

The python defect relating to this is here: http://www.python.org/dev/peps/pep-0353/

This may be relevant as well: https://launchpad.net/+search?field.text=Py_InitModule4_64+undefined

It seems like it might just be a build thing, with an additional flag being required by bjam. I wonder, does Ubuntu's build call bjam with python 2.5 specified?

Googling for this produces quite a few results actually, but unfortunately most of the resolutions I see involve linking against python 2.4 instead of 2.5 :(.

So far I'm not sure what the fix is, but I ran out of time for the moment. Will have to come back to this later.

Tim.