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
Right now, we assume a specific structure for the virtualenvs that we create, and it's necessary (I think?) that this structure matches the sysconfig.get_paths() returned by the interpreter in the virtual environment later. The paths seem to be correct for CPython, but they're not quite right for PyPy, and could be wrong in general for unusual distros.
If you look at virtualenv, my understanding is that it does something like...
Call sysconfig.get_path() without expanding variables.
## Summary
This PR migrates our virtualenv creation from a setup that assumes prior
knowledge of the correct paths, to a technique borrowed from
`virtualenv` whereby we use `sysconfig` and `distutils` to determine the
paths. The general trick is to grab the expected paths with `sysconfig`,
then make them all relative, then make them absolute for a given
directory.
Closes#2095.
Closes#2153.
Right now, we assume a specific structure for the virtualenvs that we create, and it's necessary (I think?) that this structure matches the
sysconfig.get_paths()
returned by the interpreter in the virtual environment later. The paths seem to be correct for CPython, but they're not quite right for PyPy, and could be wrong in general for unusual distros.If you look at virtualenv, my understanding is that it does something like...
sysconfig.get_path()
without expanding variables.The text was updated successfully, but these errors were encountered: