You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In general I can imagine a few options I would be interested in, validate the name of the license, validate the text of the license up to some template (i.e. should match some standard text + copyright lines), only unknown licenses for specifically named dependencies, some distinction on PEP 639 license expressions vs. previous ad-hoc license text.
Not sure how much of an ask this is, understand if it's not a priority for Astral.
The text was updated successfully, but these errors were encountered:
I, too, would be interested in this. At present there aren't many options available for modern Python codebases without resorting to use different tools altogether, so having one capable of benefiting from uv's existing metadata would certainly help.
It occurs to me that uv is in a good position to some kind of license check as part of pre-commit. Especially with PEP 639 recently added.
Maybe it would depend on astral-sh/uv#8156 / astral-sh/uv#10292
In general I can imagine a few options I would be interested in, validate the name of the license, validate the text of the license up to some template (i.e. should match some standard text + copyright lines), only unknown licenses for specifically named dependencies, some distinction on PEP 639 license expressions vs. previous ad-hoc license text.
Not sure how much of an ask this is, understand if it's not a priority for Astral.
The text was updated successfully, but these errors were encountered: