-
Notifications
You must be signed in to change notification settings - Fork 35
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
Edge case error with calculated constrains #897
Comments
In that case we just don't declare |
Closing because pinning to the maximum known valid release lower than what was specified before ( |
Yeah, just that I would not call this an edge case, but exactly the very reason this check was added. We want to know that the newly allowed version is installable and compatible. |
Fair. I was really overlooking it's purpose, thanks for pointing out. |
I've just hit a very unlike edge case that can happen if a package skips a Y release (here).
The following scenario apparently doesnt make sense, unless you see that there isnt any
3.45.*
in the PyGObject release history.It doesnt feel like the calc_constrain code should validate the version, but maybe we can introduce a special comment syntax to deal with those edge cases, like:
The text was updated successfully, but these errors were encountered: