Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed python requirements,
The current setup is correct in a very strict sense, but it enforces the users of the library that uses poetry to have also this type of strict requirements and is unpractical.
For instance I had python = "^3.11" in my requirements which is also perfectly correct for my code as python 3.13 is still not in public release and even when is released is still most likely compatible.
When you do "poetry add river", If you put python = "^3.11" then you get:
Notice that this is the only package in a long list of dependencies that made me change my own toml python version.
I suggest to relax the requirements, as I don't think that preventing future python versions makes much sense, also if I want tomorrow to test the beta test python 3.13 I will get this issue again.
Other topic would be if a current version, already released in python is not working, then I would let the stricter requirements.