Move project metadata from setup.py to pyproject.toml #1930
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
mwtoews
force-pushed
the
pyproject-toml
branch
from
890f3df to
d2b7b81
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Similar to keras-team/keras#20427, this PR migrates the core project metadata into
pyproject.tomlusing PEP 621, as supported by setuptools.Some changed metadata is to use the same name and contact email as
keras(the former seemed to have a bogus email, not that it's a big deal). It adds some useful URLs.The resulting *.whl file excludes installing
benchmark(this is a fix), but includesintegration_tests(neutral change).