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 Benedikt.Morbach
Recipients Benedikt.Morbach
Date 2014-10-25.00:00:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1414195253.67.0.0565018805165.issue22724@psf.upfronthosting.co.za>
In-reply-to
Content
alternatively, introduce a $(PYTHON_FOR_INSTALL), which doesn't set PYTHONPATH.

Then run those steps using that, with the Makefile setting PYTHONPATH=$(DESTDIR)$(LIBDEST), which doesn't contain the compiled modules at that point.

The first solution looks cleaner to me, but might be more tricky to implement, as e.g. Modules/getpath.c makes some assumptions about the location of the build dir.
History
Date User Action Args
2014-10-25 00:00:53Benedikt.Morbachsetrecipients: + Benedikt.Morbach
2014-10-25 00:00:53Benedikt.Morbachsetmessageid: <1414195253.67.0.0565018805165.issue22724@psf.upfronthosting.co.za>
2014-10-25 00:00:53Benedikt.Morbachlinkissue22724 messages
2014-10-25 00:00:53Benedikt.Morbachcreate