-
Notifications
You must be signed in to change notification settings - Fork 42
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
Dependency resolution fails due to unnecessary upper bound #155
Comments
This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs. |
This issue is still present and relevant, which I have just confirmed on the latest Hcloud-Python v1.17.0 release. I have correspondingly updated the issue description to account for these details. @LKaemmerling: Would you be so kind as to consider addressing this issue in the next Hcloud-Python release? |
Hey @justinmayer, will be fixed with the next release :) |
Much appreciated, Lukas. I look forward to those enhancements landing in a published release soon. ✨ |
I confirmed that v1.18.0 addresses this issue. Once again, thank you for the prompt attention. 👏 |
Bug Report
Current Behavior
If you have a project that specifies Python in its pyproject.toml file like so:
… and then try to add Hcloud-Python as a dependency:
… dependency resolution will fail:
Expected behavior/code
The expected behavior is that dependency resolution would not fail.
Environment
Possible Solution
The best way to address this problem is most likely to remove the upper bound from the relevant line in
setup.py
.As was noted when the Black project dropped upper bounds:
The text was updated successfully, but these errors were encountered: