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.

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

option to prefer versions without local version identifier #3267

Closed
2 tasks done
StefanSchulz-Tesyo opened this issue Oct 22, 2020 · 2 comments
Closed
2 tasks done

option to prefer versions without local version identifier #3267

StefanSchulz-Tesyo opened this issue Oct 22, 2020 · 2 comments
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged

Comments

@StefanSchulz-Tesyo
Copy link

StefanSchulz-Tesyo commented Oct 22, 2020

  • I have searched the issues of this repo and believe that this is not a duplicate.
  • I have searched the documentation and believe that my question is not covered.

Feature Request

Assume a package "mypackage" exists with the following versions:

  • 0.1.0
  • 0.1.0+dirty.1
  • 0.1.1

And we define the following dependency in poetry:
mypackage = {version = ">=0.1.0,<0.1.1", allow-prereleases = false}
Poetry will resolve to version 0.1.0+dirty.1.

A feature similar to allow-prereleases that disables local version identifiers in the search would be helpful.
Example:
mypackage = {version = ">=0.1.0,<0.1.1", allow-local = false} should resolve to 0.1.0.

AFAIK the only possible way to do that now is:
mypackage = {version = ">=0.1.0,<0.1.1,!=0.1.0+dirty.1"}, i.e. listing any version with a local identifier.

Possibly related to #2543

@StefanSchulz-Tesyo StefanSchulz-Tesyo added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Oct 22, 2020
@ralbertazzi
Copy link
Contributor

Duplicate of #7256

@ralbertazzi ralbertazzi marked this as a duplicate of #7256 May 20, 2023
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/feature Feature requests/implementations status/triage This issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants