Better cleanup PYTHONPATH for Mercurial calls (support for PDM)#1080
Better cleanup PYTHONPATH for Mercurial calls (support for PDM)#1080RonnyPfannschmidt merged 1 commit intopypa:mainfrom
Conversation
RonnyPfannschmidt
left a comment
There was a problem hiding this comment.
i wonder if there is a good integration test for this
|
I don't think there is a specific test about this mechanism. However, A problem is that pep 517 does not specify how the frontends implement the isolated build (https://peps.python.org/pep-0517/#build-environment), so we can just try to avoid known issues. |
|
Thanks @RonnyPfannschmidt. Do you think a new version could be released on PyPI? I see that the last version was released on May 2024. |
|
I'll try, but no promises, I'm suffering a stomach infection |
|
Oh I hope you will recover soon. Be brave. I'm working on modernizing Mercurial setup.py and I'd like to try to use setuptools-scm. But of course your health is more important than open-source! Beside, do not hesitate to tell me if I can help on anything for setuptools-scm. |
PDM uses the same strategy as pip for the build isolation except that the path of the temporary directory starts with "pdm-build-env-" and not "pip-build-env-".
Therefore, Mercurial (a Python application) installations can be broken and we need to clean up
PYTHONPATHfrom such paths.