[issue9807] deriving configuration information for different builds with the same prefix
Barry A. Warsaw
report at bugs.python.org
Thu Sep 30 22:52:03 CEST 2010
Barry A. Warsaw <barry at python.org> added the comment:
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.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9807>
_______________________________________
More information about the Python-bugs-list
mailing list