You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Ensure venv works with source builds when using --copies #92897
Currently a venv created with --copies or on Windows doesn't respect the sysconfig.is_python_build() property of the creating interpreter. This leads to compilation errors when attempting to build extensions in the virtual environment.
After the PR, this builds without error (kinda). There is a bug in setuptools that causes an additional error. This can be worked around by setting the environment variable SETUPTOOLS_USE_DISTUTILS=no.
I'll add that prior to 3.8 this problem did not occur. Just that source builds on Windows are a rare thing to start with much less compiling in virtual environments from a source build so this change in behavior has gone relatively unnoticed.
Is there any plan for the removal of the check_home argument in sysconfig.is_python_build, whose deprecation was introduced in GH-92899?
Keeping deprecated as-is doesn't really create much maintenance burden, and removing it can break user code, though searching for such usages on Github didn't yield any results. Perhaps we could schedule its removal for 3.15 or 3.16, and clearly state that in the deprecation warning? What do you folks think?
Activity
pythongh-92897: Ensure `venv --copies` respects source build property…
jkloth commentedon May 17, 2022
An example error when building psutil.
After the PR, this builds without error (kinda). There is a bug in setuptools that causes an additional error. This can be worked around by setting the environment variable
SETUPTOOLS_USE_DISTUTILS=no.vstinner commentedon May 18, 2022
@jkloth proposed #92899 to fix this issue.
jkloth commentedon May 25, 2022
I'll add that prior to 3.8 this problem did not occur. Just that source builds on Windows are a rare thing to start with much less compiling in virtual environments from a source build so this change in behavior has gone relatively unnoticed.
gh-92897: Ensure `venv --copies` respects source build property of th…
[3.11] pythongh-92897: Ensure `venv --copies` respects source build p…
pythongh-92897: Ensure `venv --copies` respects source build property…
[3.11] gh-92897: Ensure `venv --copies` respects source build propert…
vsajip commentedon Jul 5, 2022
Closing, as PRs merged for
mainand3.11branches.FFY00 commentedon Jan 20, 2025
Is there any plan for the removal of the
check_homeargument insysconfig.is_python_build, whose deprecation was introduced in GH-92899?Keeping deprecated as-is doesn't really create much maintenance burden, and removing it can break user code, though searching for such usages on Github didn't yield any results. Perhaps we could schedule its removal for 3.15 or 3.16, and clearly state that in the deprecation warning? What do you folks think?
vstinner commentedon Jan 20, 2025
The deprecated check_home parameter can be removed in Python 3.15.
pythonGH-92897: schedule the check_home deprecation to 3.15
GH-92897: schedule the check_home deprecation to 3.15 (#129102)
pythonGH-92897: schedule the check_home deprecation to 3.15 (python#1…
[3.13] pythonGH-92897: schedule the check_home deprecation to 3.15 (p…
[3.12] pythonGH-92897: schedule the check_home deprecation to 3.15 (p…
[3.13] GH-92897: schedule the check_home deprecation to 3.15 (GH-129102…
[3.12] GH-92897: schedule the check_home deprecation to 3.15 (GH-129102…
gh-92897: Doc: the check_home removal has been scheduled for 3.15 (#1…
pythongh-92897: Doc: the check_home removal has been scheduled for 3.…
gh-92897: document removal of `check_home` in `Doc/whatsnew/3.15.rst` (…
pythongh-92897: document removal of `check_home` in `Doc/whatsnew/3.1…
pythongh-92897: document removal of `check_home` in `Doc/whatsnew/3.1…