fix: correct pyproject.toml license field per PEP 621#330
Open
Avinash-yadav103 wants to merge 1 commit into
Open
fix: correct pyproject.toml license field per PEP 621#330Avinash-yadav103 wants to merge 1 commit into
Avinash-yadav103 wants to merge 1 commit into
Conversation
The `project.license` field used a bare string ('Apache-2.0'), which is
not a valid form per PEP 621. Modern setuptools (>= 80) rejects this with:
ValueError: invalid pyproject.toml config: project.license.
configuration error: project.license must be valid exactly by one
definition (2 matches found)
This breaks `pip install` from source on macOS / newer toolchains
(reported in OpenBMB#233). PEP 621 requires a table with either `text` or
`file` key, so use the explicit `{text = ...}` form.
Closes OpenBMB#233
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The
project.licensefield used a bare string ('Apache-2.0'), which is not a valid form per PEP 621. Modern setuptools (>= 80) rejects this with:This breaks
pip installfrom source on macOS / newer toolchains (reported in #233). PEP 621 requires a table with eithertextorfilekey, so use the explicit{text = ...}form.Closes #233