Remove upper bound from Python version specifier#452
Open
sisp wants to merge 1 commit intoollama:mainfrom
Open
Remove upper bound from Python version specifier#452sisp wants to merge 1 commit intoollama:mainfrom
sisp wants to merge 1 commit intoollama:mainfrom
Conversation
Member
|
If we end up keeping poetry will get this in :) |
Author
|
Any reason not to merge this, even if you consider migrating away from Poetry at some point? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Capping the Python version (e.g.
<4) is a bad practice.Hence, I've removed the upper bound, i.e. I've replaced the version specifier
^by>=.