| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
… of the creating interpreter.
|
Don't touch distutils - it's going to be deleted in this release anyway, and there are no maintenance releases where it is undeprecated. If we're using it within the stdlib, update the references elsewhere. If setuptools is impacted, they need the patch. I haven't looked any deeper than that - it's late. I'll try and take a look later this week |
Sorry, something went wrong.
|
The changes to distutils are only to keep it from raising exceptions. Since it is being removed, I saw no need to keep private functions around just for use within distutils which would prevent a more straight forward implementation. Hence the modifications to distutils. The changes to stdlib sysconfig have no impact on setuptools distutils.sysconfig so nothing to do there. |
Sorry, something went wrong.
In practice, setuptools now injects its own distutils flavor, so I am not sure that it's worth it to modify it here. At least, you should get your change merged first in https://github.com/pypa/distutils/ |
Sorry, something went wrong.
|
distutils.sysconfig and distutils.test.test_sysconfig in the stdlib have diveraged from those in setuptools (PR #23142). Therefore the changes included here have ZERO correspondance to those in setuptools. distutils.sysconfig in setuptools does not rely on any private functions from sysconfig so there is no change to merge. |
Sorry, something went wrong.
|
To make it absolutely clear, the changes here to distutils modules are solely to prevent an ImportError from occurring wherever distutils modules are still used in the stdlib. The changes are intended to keep it "working" until it can be fully removed at a later date. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM, and appears to handle the case on Windows where a venv is created from a source build. I can only assume the behaviour is correct on other platforms?
Sorry, something went wrong.
|
As far as other platforms go, it is tested on Ubuntu (WSL). |
Sorry, something went wrong.
|
Sorry, @jkloth and @vsajip, I could not cleanly backport this to 3.10 due to a conflict. |
Sorry, something went wrong.
|
Sorry @jkloth and @vsajip, I had trouble checking out the 3.11 backport branch. |
Sorry, something went wrong.
…roperty of the creating interpreter (pythonGH-92899) (cherry picked from commit 0675975) Co-authored-by: Jeremy Kloth <jeremy.kloth@gmail.com>
|
GH-94567 is a backport of this pull request to the 3.11 branch. |
Sorry, something went wrong.
… of the creating interpreter (pythonGH-92899) (cherry picked from commit 0675975)
|
GH-94572 is a backport of this pull request to the 3.10 branch. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
There is a discrepancy between a symlink venv and a copied venv when determining whether the interpreter is considered to be from a source build. A symlink venv indicates True for sysconfig.is_python_build() whereas a copied venv returns False.
Since symlink venvs are the default for POSIX (where the majority of source builds would be used/tested), I have opted to use that behavior as correct. Windows users are far more likely to use the binary installer so odds of venvs being created from source builds are quite low. Likewise with venv --copies on POSIX.
These changes will allow for building extensions out of venvs created from source builds without any pre-configuration steps (see this section from pyperformance documentation).
Adding @zooba for Windows and @vsajip for venv