Updates table to contain poetry-core version supporting PEP 639 #1915
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
Contributor
Author
|
See also, the closed poetry-core PR listing this change: python-poetry/poetry-core#885 |
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.
I happened to notice that the latest version of poetry does indeed support PEP639 (See: https://python-poetry.org/history/#220---2025-09-14) so I figured this table should be updated 🙂
FWIW I did also validate myself that the same dummy project build with poetry 2.1.4 and 2.2.0 result in slightly different PKG-INFO outputs as expected.
Old:
New:
📚 Documentation preview 📚: https://python-packaging-user-guide--1915.org.readthedocs.build/en/1915/