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
I have no idea if this is a pip, setuptools or a venv issue.
The script wrappers generated installed in virtual environments (from venv) don't appear to install consistently and depend upon how the cache is built.
Sometimes the wrappers are built with easy_install and sometimes not. The problem for me is that the easy_install wrappers don't support virtual environments in long named paths (due always using a shebang). Whereas the wrappers not built with easy_install will use an exec if the path of the virutalenv is too long.
The problem appears to be with how the cache is built. If the package was installed globally with a clean cache, then the non-easy_install wrappers are built in subsequent venvs.
Expected behavior
Never to use easy_install, or at least build consistently regardless of the cache state.
pip needs wheel to build the package without setuptools, so a fresh venv wouldn’t be able to achieve your expectation. The behaviour can indeed be confusing, see #7709 for a proposal for improvements.
Also note that if you’re a maintainer of the package, one way to avoid this problem is to adopt PEP 518, by creating a pyproject.toml with the following content:
Environment
Description
I have no idea if this is a pip, setuptools or a venv issue.
The script wrappers generated installed in virtual environments (from venv) don't appear to install consistently and depend upon how the cache is built.
Sometimes the wrappers are built with easy_install and sometimes not. The problem for me is that the easy_install wrappers don't support virtual environments in long named paths (due always using a shebang). Whereas the wrappers not built with easy_install will use an
exec
if the path of the virutalenv is too long.The problem appears to be with how the cache is built. If the package was installed globally with a clean cache, then the non-easy_install wrappers are built in subsequent venvs.
Expected behavior
Never to use easy_install, or at least build consistently regardless of the cache state.
How to Reproduce
Run this:
myvenv/bin/lit
has a wrapper that appears to be built from easy_installNow run:
Now the lit wrapper doesn't use easy_install.
Output
The text was updated successfully, but these errors were encountered: