You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This results in a failed installation in other poetry managed projects if they do not define an upper constraint.
To Reproduce
Create a new project without an upper python version constraint with poetry
Run poetry add coveralls
Expected Behavior
Remove the upper bound so libraries aren't forced to add an upper constraint to get a successful install
Package Versions
coveralls 4.0.1
Trace Logs
❯ poetry add coveralls -G dev
Using version ^4.0.1 for coveralls
Updating dependencies
Resolving dependencies... (0.2s)
The current project's supported Python range (>=3.9) is not compatible with some of the required packages Python requirement:
- coveralls requires Python <3.13,>=3.8, so it will not be satisfied for Python >=3.13
Because no versions of coveralls match >4.0.1,<5.0.0
and coveralls (4.0.1) requires Python <3.13,>=3.8, coveralls is forbidden.
So, because pocketbase depends on coveralls (^4.0.1), version solving failed.
• Check your dependencies Python requirement: The Python requirement can be specified via the `python` or `markers` properties
For coveralls, a possible solution would be to set the `python` property to ">=3.9,<3.13"
https://python-poetry.org/docs/dependency-specification/#python-restricted-dependencies,
https://python-poetry.org/docs/dependency-specification/#using-environment-markers
The text was updated successfully, but these errors were encountered:
Describe the Bug
This project has an upper bound on python version:
coveralls-python/pyproject.toml
Line 34 in ff75b50
This results in a failed installation in other poetry managed projects if they do not define an upper constraint.
To Reproduce
poetry add coveralls
Expected Behavior
Remove the upper bound so libraries aren't forced to add an upper constraint to get a successful install
Package Versions
Trace Logs
The text was updated successfully, but these errors were encountered: