Update poetry to 2.1.3 #586
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
matentzn
approved these changes
May 22, 2025
|
THANK YOU @cthoyt for your contribution!! |
|
I don't know if it's best practice or not. I would rather not do it and rely on the most recent version, but I didn't want this update to be controversial |
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.
This repository is currently using poetry 1.6.1, released in August 2023. A lot has changed in Python packaging since then, including the crystallization of the pyproject.toml standard metadata, dependency groups, and more.
This PR gets ready for revitalizing SSSOM-py by first updating Poetry to a newer version. This makes a small amount of diff in the poetry lock file.
Note: poetry fixed its resolver since 1.6.1 and it's also muchhhh faster now