Skip to content

Use License Expressions in pyproject.toml - #1111

Merged
csmarchbanks merged 1 commit into
masterfrom
pep-639
Jun 2, 2025
Merged

Use License Expressions in pyproject.toml#1111
csmarchbanks merged 1 commit into
masterfrom
pep-639

Conversation

@csmarchbanks

@csmarchbankscsmarchbanks commented May 29, 2025

Copy link
Copy Markdown
Member

With the release of PEP-639 the best practice for specifying the license is now to use a license expression in the license field and specify any license files in license-files rather than the table-based approach from PEP-621. Including the license in the classifiers is also no longer allowed when using PEP-639 and has been removed.

@csmarchbanks
csmarchbanksforce-pushed the pep-639 branch 2 times, most recently from 2150f8f to 7bb3bf8CompareMay 29, 2025 01:01
@csmarchbankscsmarchbanks mentioned this pull request May 29, 2025
With the release of PEP-639 the best practice for specifying the license
is now to use a license expression in the license field and specify any
license files in license-files rather than the table-based approach from
PEP-621. Including the license in the classifiers is also no longer
allowed when using PEP-639 and has been removed.
Signed-off-by: Chris Marchbanks <csmarchbanks@gmail.com>
Comment threadpyproject.toml
description = "Python client for the Prometheus monitoring system."
readme = "README.md"
license = { file = "LICENSE" }
license = "Apache-2.0 AND BSD-2-Clause"

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BSD-2-Clause is from the decorators file we embed into this library.

Sign up for freeto 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

@csmarchbanks