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

Loosen python version requirement from >=3.9,<3.13 to >=3.9 #523

Open
Ravencentric opened this issue Sep 14, 2024 · 1 comment
Open

Loosen python version requirement from >=3.9,<3.13 to >=3.9 #523

Ravencentric opened this issue Sep 14, 2024 · 1 comment
Assignees

Comments

@Ravencentric
Copy link

Describe the Bug
This project has an upper bound on python version:

python = ">=3.8,<3.13"

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
@Zeitsperre
Copy link

Any word on when this metadata update will happen? This is the sole blocker preventing some of my projects from being able to try out Python3.13.

I can open a PR if you'd like!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants