Skip to content

Correct package license metadata - #64

Closed
charliermarsh wants to merge 1 commit into
mainfrom
charlie/correct-license-metadata
Closed

charliermarsh wants to merge 1 commit into
mainfrom
charlie/correct-license-metadata

Conversation

@charliermarsh

Copy link
Copy Markdown
Member

We declare (MIT OR Apache-2.0) AND Python-2.0.1 in the crate's package metadata to account for the generated character-reference data derived from CPython. The parser code remains dual-licensed under MIT or Apache-2.0.

We update both READMEs to distinguish the parser code from the generated data. Downstream license checks can use the crate's metadata without a local license clarification.

Related to astral-sh/uv#22203.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant