Use pyproject.toml instead of setup.py #1100
Merged
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.
Related Issue(s):
Description:
While tackling #1085, I took the opportunity to migrate our
setup.py
configuration topyproject.toml
. As of PEP 621,pyproject.toml
is the preferred way to specify project metadata, and setuptools began supporting it in version 61.0.0.This should mostly be a noop, with the following exceptions:
authors
fromstac-utils
to @lossyrob and @duckonthewebmaintainer
requirements-*.txt
files intopyproject.toml
as optional dependencies, and updated the docs accordingly~=
to reduce our dependabot noisev1
vanilla
CI check to be namedwithout-orjson
to be more clear about what it doesNo code changes. If this change works well, we should do the same for stactools and pystac-client.
PR Checklist:
pre-commit
hooks pass locallyscripts/test
)vanilla
towithout-orjson