Move project configuration to pyproject.toml #242
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
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.
Move project, backend, and development tool configuration to pyproject.toml.
Only configuration change was moving the Python 3.6 extra dependencies specification to main dependencies (conditioned on Python being 3.6). I'm pretty sure Setuptools v61+ doesn't support Python 3.6 anyway, so this MR might be predicated on dropping Python 3.6.
Flake8 configuration couldn't be moved due to PyCQA/flake8#234. I guess this could be moved to .flake8 if you want setup.cfg to be removed.
Downsides: lose Git history on those files, require Setuptools v61+ (and therefore Python 3.7+), longer pyproject.toml to read for tool configuration