WIP: [python-package] [ci] move some configuration to setup.cfg #5762
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.
Contributes to #5061 .
Reduces the number of changes that need to be reviewed when switching build backends for the Python package (work-in-progress in #5759).
This PR proposes moving some configuration for the Python package out of
setup.py
and into asetup.cfg
file. This moves the project one step closer to having PEP 517 / 518 compliant Python package builds.For reference, see:
setuptools
usingsetup.cfg
files" (setuptools docs)