Devops: adopt PEP 621 and move build spec to pyproject.toml
#779
Conversation
This file contains 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
sphuber
force-pushed
the
fix/778/pep-621-build
branch
from
ecb990a
to
57d098e
Compare
Following PEP 621 it is now possible to fully define the build procedure of your package in `pyproject.toml`. Since this PEP is now well supported, and for example `pip` can use it, we migrate to it since it provides a bunch of benefits: * No longer need the deprecated `setup.py` to install the package. * Version number is now dynamically fetched from the package. So the utility script to make sure the `setup.json` specifies the same version can be removed. * The `MANIFEST.in` is no longer necessary. The `flit` build tool will automatically include anything. The `pyproject.toml` has a tool section for `flit` that excludes the `tests` and `docs` folders.
sphuber
force-pushed
the
fix/778/pep-621-build
branch
from
57d098e
to
390bb70
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #778
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
pipcan use it, we migrate to it since itprovides a bunch of benefits:
setup.pyto install the package.utility script to make sure the
setup.jsonspecifies the sameversion can be removed.
MANIFEST.inis no longer necessary. Theflitbuild tool willautomatically include anything. The
pyproject.tomlhas a toolsection for
flitthat excludes thetestsanddocsfolders.