-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Please also yank 5.2.1 #729
Comments
The best way to yank 5.2.1 is probablt by releasing a 5.2.2, isn't it? Just like in Debian, I packaged 5.2.1 with a patch (5.2.1.post0 isn't a good version number)... |
Even if a new version is released, the bad version should be yanked. A yanked release is treated differently by pip. In particular it is ignored unless that version is specifically requested with an equality requirement. |
@SnarkBoojum Was there a |
Replying to my own comment, I don't see any yanked versions on PyPI, so I'm assuming |
@SnarkBoojum Actually, from $ curl -s https://pypi.org/simple/traitlets/ | grep 5.2.2.post0
<a href="https://files.pythonhosted.org/packages/30/b6/43f78c203f11e7ce353ca7ca326332f8c020863b7904cc8aedea5a415f90/traitlets-5.2.2.post0-py3-none-any.whl#sha256=7109d1daa09aaf3aefd823eadde1d81508d039c74d9bed6b1812c58bea0cfe20" data-requires-python=">=3.7" >traitlets-5.2.2.post0-py3-none-any.whl</a><br /> even though it's not in the PyPI release history nor the |
@SnarkBoojum @danking Please, if you would, kindly take a look at |
@blink1073 From the report, it seems you submitted the package to PyPI on May 31, 2022. Would you also mind taking a look? |
5.2.1 was never yanked but there’s enough subsequent releases that this issue now feels irrelevant. Closing. Thanks all |
Hi there!
We noticed that 5.2.1 had some issue related to the _version module. I see you have released 5.2.1.post0. Thank you! Could you also yank 5.2.1 from PyPI to further limit the impact of this release? Thank you in advance.
The text was updated successfully, but these errors were encountered: