Migrate setup.cfg
logic to pyproject.toml
#4541
Merged
+71
−87
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.
Converted the
setup.cfg
settings to a format thatpyproject.toml
can utilize. Consequently,setup.cfg
was removed, as everything is now handled in thepyproject.toml
; "source" arrays have had their values swapped as necessary. The only discrepancies in the migration are:metadata.group
was removed. This simply isn't a valid option inpyproject.toml
, and this info can be extrapolated fromproject.classifiers
.options.data_files
was removed. This is considered a discouraged & largely unsupported option, with the listed files already getting caught bytool.setuptools.package-data
anyway.The only other change made is fixing the
mypy
section ofpyproject.toml
; turns out its syntax was incorrect this whole time. Unsure if explicit tests are necessary in this instance, as they're already validated by the buildsystem itself.Contributor Checklist:
CHANGES.txt
(and read theREADME.rst
)