-
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
pip behaves poorly when legacy package does not generate a record file #7450
Comments
I think the cause of this is most often #9393 fixes this by raising the exception before the temp directory is created. |
Note that |
Environment
Should apply across all pip, Python, and OS versions.
Description
When pip installs a legacy package (calling
setup.py install
directly) it passes--record /tmp/path/to/install-record.txt
. setuptools should be populating this with the list of installed files.If a file is not generated, then pip silently continues processing the next requirement to install. This leads to:
Expected behavior
In all likelihood this would result from user error, as demonstrated in the script below. In case it is not - both distutils and setuptools have supported this option for at least 10 years, so it's reasonable to expect legacy-installable packages to treat it correctly.
How to Reproduce
Run the following script
t.sh
Output
Output
Notice the presence of
'~ello-0.1.0-py3.8.egg-info'
in site-packages and the warning onpip freeze
as described in #7269.The text was updated successfully, but these errors were encountered: