Update flit to use PEP 639 #530
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
srittau
approved these changes
Feb 19, 2025
|
this change causing the regression - pip-licenses is detecting the license not as PSF anymore but as unknown: $ pip-licenses \
--allow-only "\
Python Software Foundation License;\
"
license UNKNOWN not in allow-only licenses was found for package typing_extensions:4.13.1with 4.12.2 same check was passing |
Contributor
Author
|
@actionless This is an issue with pip-licenses. It doesn't support PEP 639 license-expressions yet. See raimon49/pip-licenses#225. |
|
@cdce8p thanks for clarification! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Flit
3.11was released today with basic support for PEP 639.https://flit.pypa.io/en/stable/history.html#version-3-11
Followup to #507, replaces #451.