-
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
Release 21.2.1 #10198
Release 21.2.1 #10198
Conversation
Did any of the automation try to do that? |
The docs just say Push all of the changes including the tag. Step 6 here: https://pip.pypa.io/en/stable/development/release-process/#creating-a-new-release |
I wonder if we should update that to be more specific:
|
- When pip is asked to uninstall a project without the dist-info/RECORD file | ||
it will no longer traceback with FileNotFoundError, | ||
but it will provide a better error message instead, such as:: | ||
|
||
ERROR: Cannot uninstall foobar 0.1, RECORD file not found. You might be able to recover from this via: 'pip install --force-reinstall --no-deps foobar==0.1'. | ||
|
||
When dist-info/INSTALLER is present and contains some useful information, the info is included in the error message instead:: | ||
|
||
ERROR: Cannot uninstall foobar 0.1, RECORD file not found. Hint: The package was installed by rpm. (`#8954 <https://github.com/pypa/pip/issues/8954>`_) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's always that one changelog entry that's closer to a full commit message, than a one-line summary. :)
Hmm why is the deprecation warning suddenly starts failing. |
Ah because we're supposed to remove it 🤦 I really should have filed this before releasing. |
I can't push directly to main; this should work as well.