Fail to order pre-release versions for Python dependencies
Closed this issue · 7 comments
Describe the bug
The extension displays ❌ with the pre-release version next to the newer stable version.
To Reproduce
- Prepare a
requirements.txt
with the following content:
typer==0.12.3
datashader==0.16.3
- Open the file in VS Code with the extension. The extension displays
❌ 0.12.dev2
fortyper
and❌ 0.16.3rc0
fordatashader
. The extension settings are all set to defaults.
Expected behavior
The extension shows ✅
for both cases, as they are the latest stable versions. Also, I want "0.12.dev2" to be regarded as older than "0.12.3" and "0.16.3rc0" older than "0.16.3".
The Semantic Versioning requires a hyphen between the version core and pre-release, and I'm guessing that may be the cause of this. But it seems to be the standard in Python. See Version specifiers - Python Packaging User Guide.
Desktop (please complete the following information):
- OS: Linux (WSL2 Ubuntu)
- Version: v0.7.5
As a whole, pre-releases should probably not be recommended at all. Most Python tools require to explicitly opt-in to pre-releases when dependencies are installed.
As a whole, pre-releases should probably not be recommended at all. Most Python tools require to explicitly opt-in to pre-releases when dependencies are installed.
Thanks for the info. We defined a setting for that , means they are excluded by default but if you insist yo see them.
@shunichironomura does this works for you ?
@serayuzgur Yes, that's what I expect to see.
Hi @shunichironomura , we have fixed this issue per your request.
We'd be really happy if you could review Dependi, here is our reviews page.