Devops: adopt PEP 621 and move build spec to pyproject.toml
#230
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.
Following PEP 621 it is now possible to fully define the build procedure
of your package in
pyproject.toml
. Since this PEP is now wellsupported, and for example
pip
can use it, we migrate to it since itprovides a bunch of benefits:
setup.py
to install the package.MANIFEST.in
is no longer necessary. Theflit
build tool willautomatically include anything. The
pyproject.toml
has a toolsection for
flit
that excludes thetests
anddocs
folders.pyproject.toml
.