pip lists latest version as 2.3.1, but latest tag is 2.3.0
See original GitHub issueHi,
The latest version for this according to this repos tags is 2.3.0
However, pypi has the latest version as 2.3.1
Using 2.3.1 breaks things like pre-commit:
[INFO] Initializing environment for https://github.com/asottile/reorder_python_imports.
An unexpected error has occurred: CalledProcessError: command: ('/usr/bin/git', 'checkout', 'v2.3.1')
return code: 1
expected return code: 0
stdout: (none)
stderr:
error: pathspec 'v2.3.1' did not match any file(s) known to git.
Can we remove v2.3.1 from pypi or publish a v2.3.1 if it was deleted by accident?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
`pip list -o` doesn't signal a very old pre-existing lock file ...
1 is available. You should consider upgrading via the 'python -m pip install --upgrade pip' command. λ pip list -o Package Version Latest...
Read more >Python and pip, list all versions of a package that's available?
I'm trying to install a version for a third party library, but the newest version is too new, there were backwards incompatible changes...
Read more >Changelog - pip documentation v22.3.1
Add new subcommand pip index used to interact with indexes, and implement pip index version to list available versions of a package. (#7975)....
Read more >Install spaCy · spaCy Usage Documentation
The latest spaCy releases are available over pip and conda. ... When updating to a newer version of spaCy, it's generally recommended to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
the contents are byte identical with 2.3.2
Thanks for the quick response @asottile