Closed
Conversation
Member
|
no it's not |
Author
Could you please elaborate on why you would rather stay with the setup.cfg and setup.py approach? |
Member
|
just because the peps exist does not mean that setup cfg is deprecated. nobody asked for this drive by patch |
Author
|
Fair enough |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
pyproject.toml is the modern replacement for setup.cfg and setup.py.
This pyproject.toml was generated using ini2toml 0.15, then in the second commit the dev dependencies were moved from requirements-dev.txt to
[project.optional-dependencies] devand tox.ini amended. Tox functionality was tested and works as expected,python3 -m buildalso runs without issue