PyBuild available in raring

[Barry Warsaw]

On Jan 25, 2013, at 05:43 PM, Scott Kitterman wrote:

>There's another case as well.  If there is pure python code that is python3 
>version specific.  This is rare, but exists.  To make sip4/python-qt4 support 
>multiple python versions I had to do some really unfortunate and painful 
>things to make it work.  It would be nice if we had a general solution for 
>this.

Perhaps in those cases, a pybuild option to install into the version specific
location would be appropriate?

Matthias reminded me with more detail of why this is.  It's not necessary for
distutils based packages because the .so's will always get the right PEP 3149
tag, so you always know what version of Python a shlib is for by looking at
its file name.

It's for non-distutils based builds which may create unadorned shared libs.
Unfortunately, the only way I know of to determine the version of Python for
such shlibs is to brute forcing an import with every available Python, and
watch for the fatal exception (presumably with a non-zero exit status - I
haven't tried it).  The one that doesn't fail is the winner.

Cheers,
-Barry