Repository navigation
Use declarative package configuration - #5784
Merged
Merged
Conversation
hugovk
added
the
Packaging
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
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.
We can move much of the static packaging metadata from
setup.pyto a declarative package configuration file,setup.cfg.This is happening in many Python projects (and pure Python projects can have a minimal or no
setup.py).A benefit for us is we can get to this metadata without scrolling to the end of 1,000 lines of logic, making it more visible and easier to edit. If it doesn't need any logic, it's cleaner to move it out.