This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author barry
Recipients amaury.forgeotdarc, barry, dmalcolm, doko, eric.araujo, eric.smith, fdrake, loewis, pitrou, r.david.murray
Date 2010-09-30.20:52:01
SpamBayes Score 4.5444666e-09
Marked as misclassified No
Message-id <1285879923.18.0.829998217348.issue9807@psf.upfronthosting.co.za>
In-reply-to
Content
I have a some code available for review here:

http://codereview.appspot.com/2340041/

I've actually gone down a farther path than I originally intended, but I do kind of like where this is heading.  It will allow me to install different Python builds of the same version without collision, at least when you use 'make altinstall'.  There are different versions even of python-config (with an added --abiflag option) so you can tell exactly what you're getting.

Note that 'make install' still adds all the symlinks so that you get a 'python3' and 'python3-config' as defaults.

Still broken are importing extensions.  E.g. if I do the following:

./configure --prefix=/tmp/python && make altinstall
./configure --prefix=/tmp/python --with-wide-unicode --with-pydebug && make altinstall
(cd some simple module with an extension)
/tmp/python/bin/python3.2dmu setup.py install
/tmp/python/bin/python3.2m
>>> import myextension

it tries to import the 3.2dmu version and fails.  I'm still investigating that, but in the meantime, please go to codereview and let me know what you think so far.
History
Date User Action Args
2010-09-30 20:52:03barrysetrecipients: + barry, loewis, fdrake, doko, amaury.forgeotdarc, pitrou, eric.smith, eric.araujo, r.david.murray, dmalcolm
2010-09-30 20:52:03barrysetmessageid: <1285879923.18.0.829998217348.issue9807@psf.upfronthosting.co.za>
2010-09-30 20:52:01barrylinkissue9807 messages
2010-09-30 20:52:01barrycreate