-
Notifications
You must be signed in to change notification settings - Fork 4
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
Users on Python 3.7 only find unusable dev1
version and can't update
#3
Comments
This was supposed to be fixed in dev2. You have dev1 installed. Can you reproduce if you upgrade the package? |
The fixer was 1eb8b64 |
For some reason I am not able to install that version:
I tripple checked the version, being a dyslexic, but can't find any issue. |
It is available on PyPI website, so I'm stumped: https://pypi.org/project/ferrypick/0.1.dev2/#history |
Oooh, got it. I'm using Python 3.7 and the |
The first one isn't though, so it installed and refused to update. |
|
dev1
version and can't update
The code is 3.7 incompatible. The packaging issues made it possible to install dev1 on 3.7, but without the actual code. The only way I can think of to fix this is to remove dev1 from PyPI. |
I would say that's a good idea. |
We can either yank or delete it, I'll figure out what is more appropriate https://twitter.com/di_codes/status/1253166894158417926 |
I figure we should yank it. Yank is reversible, so I've done it now. |
The above is not perfect, but only affects users who pin.
That is bad either way :/ |
I wonder if this is expected behavior of pip. pypa/pip#8262 |
Yeah, not perfect. I would consider deleting it outright, but either way is reasonable enough. |
Thanks! |
I am not deleting it now, because I want to use it as a reproducer for the pip issue. If they deem the behavior appropriate, I'll delete it. |
Hi,
ferrypick installed (--user) from PyPI doesn't work. It fails with:
Steps to reproduce:
It seems the module actually isn't there. When uninstalling ferrypick, only the binary and dist-info are listed:
The text was updated successfully, but these errors were encountered: