-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistent behaviour of installed wrappers in venv #7716
Comments
pip needs 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 [build-system]
requires = ["setuptools", "wheel"] |
Many thanks for the response. Installing wheel in my venv nicely works around the issue. |
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: