Remove upper bounds from package dependencies#136
Merged
timothyngo merged 4 commits intodevfrom Dec 19, 2025
Merged
Conversation
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
2 participants
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.
Closes #135
Closes KEM-10
This PR removes upper bounds on the package dependencies in TATM, following the guidance in this article. The upper bounds (which are frequently default in poetry) are overly restrictive and make it hard for package managers to resolve dependencies for any downstream projects that import TATM.
In addition, I have also added dependency groups following PEP 735. This doesn't impact the poetry build, but allows us to switch to other package managers like uv which do not use poetry's custom format. Poetry doesn't yet look at this field, but it is a planned enhancement, after which we can remove the poetry specific fields.