Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Include pre-release versions if Python dependency manifest uses pre-release versions #161

Open
nickiemc opened this issue Oct 15, 2020 · 1 comment
Open

Include pre-release versions if Python dependency manifest uses pre-release versions #161

nickiemc opened this issue Oct 15, 2020 · 1 comment
Labels
python Parsing Python dependencies

Comments

@nickiemc
Copy link
Contributor

A number of Python dependencies are unable to be found because the only versions that have ever been released are pre-release versions and/or the manifest references a pre-release version.

Similar to the Ruby implementation in PR #154, assume that if the manifest references a pre-release version, then they want to absolute latest version of that dependency even if it is a pre-release.

Example:

Manifest Latest stable Latest unstable Value to use
1.1b1 0.9 1.1b2 1.1b2
0.8 0.9 1.1b2 0.9
@nickiemc nickiemc added the python Parsing Python dependencies label Oct 15, 2020
@nickiemc
Copy link
Contributor Author

Relevant examples from https://github.com/mailpile/Mailpile:

spambayes==1.1b1
spambayes>=1.1b1

This was referenced Oct 15, 2020
Closed
Closed
@mscottford mscottford moved this to Backlog in Freshli Apr 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
python Parsing Python dependencies
Projects
Freshli
Status: Icebox
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nickiemc