➜

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 xdegaye
Recipients Benedikt.Morbach, doko, ncoghlan, puchenyaka, rpetrov, thomas-petazzoni, xdegaye
Date 2020-01-24.20:12:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579896721.71.0.87886262292.issue22724@roundup.psfhosted.org>
In-reply-to
Content 
PYTHON_FOR_BUILD does not use PYTHONPATH in the implementation of (closed) PR 17420 and should fix the current issue as a side effect.

FWIW, PR 17420 fixes cross-compilation of third-party extension modules by replacing the complex PYTHON_FOR_BUILD command line set in configure.ac by the more simple command:

    "PYTHON_FOR_BUILD='PYTHON_PROJECT_BASE=$(abs_builddir) '$interp"

In this PR finding the path name of the target sysconfigdata module when needed is done by the sysconfig module and by distutils using the Misc/python-config.sh.in script instead of using PYTHONPATH.

Since PYTHONPATH is not used in PR 17420, the current issue should also be fixed by the PR. See also Benedikt OP that provided a hint for the fix.
History
Date User Action Args
2020-01-24 20:12:01xdegayesetrecipients: + xdegaye, doko, ncoghlan, rpetrov, Benedikt.Morbach, thomas-petazzoni, puchenyaka
2020-01-24 20:12:01xdegayesetmessageid: <1579896721.71.0.87886262292.issue22724@roundup.psfhosted.org>
2020-01-24 20:12:01xdegayelinkissue22724 messages
2020-01-24 20:12:01xdegayecreate