-
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
Set project name to UNKNOWN when empty #9838
Set project name to UNKNOWN when empty #9838
Conversation
57cfa05
to
c157449
Compare
Solves the issue for me. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
c157449
to
a5ded57
Compare
For compatibility with distutils. This is only done when pip is not inside a virtual environment due to a quirk in pip's previous implementation to the header path.
a5ded57
to
e7b1722
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hello, just reporting the following: Mac OS 11.2.3, using pyenv, fresh 3.9.4 install, updated PIP to 21.1, went to update setuptools and wheel and got the following, let me know if I can provide any further details that might assist you:
|
Please read this: #9617 (comment) |
Side note: we apparently don't do much with "scheme.headers" except passing them to the legacy setup.py install command ? Does that mean there are user expectations around that and we should take care of it when deprecating the setup.py install code path ? |
got this while installing conda on macOS Catalina 10.15.7.
|
Please see #9617. |
For compatibility with distutils. This should fix the flood of incoming reports in #9617.