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 ned.deily
Recipients Arfrever, John.Malmberg, larry, loewis, matrixise, ned.deily, python-dev, twouters, vstinner
Date 2014-10-15.18:29:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413397767.93.0.835192978343.issue17095@psf.upfronthosting.co.za>
In-reply-to
Content
Stéphane, as I understand it, this issue covers two problems:
(1) Building and installing shared modules using Modules/Setup was broken for current Python 3 releases;
(2) Using those shared modules when running Python from a build directory (rather than from a normal installed Python) is broken.

Problem (1) is now fixed.  Problem (2) remains to be properly fixed; it's a little tedious to get right as a fix needs to take into account the SO_ABI and ensure built modules get properly cleaned and all the right Makefile dependencies work.  I'd be happy to review a patch if someone gets to it before I do.  But it seems to me that (1) was the serious problem; (2) is more of a minor annoyance for developers with easy workarounds, e.g. use PYTHONPATH or install Python to a temporary location for testing.
History
Date User Action Args
2014-10-15 18:29:27ned.deilysetrecipients: + ned.deily, loewis, twouters, vstinner, larry, Arfrever, python-dev, matrixise, John.Malmberg
2014-10-15 18:29:27ned.deilysetmessageid: <1413397767.93.0.835192978343.issue17095@psf.upfronthosting.co.za>
2014-10-15 18:29:27ned.deilylinkissue17095 messages
2014-10-15 18:29:27ned.deilycreate