Switching to pyproject.toml
for specifying package metadata
#173
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.
Switches from current
setup.py
approach of specifying package metadata to instead use apyproject.toml
configuration file and sets upsetuptools_scm
to automatically set package version number from Git release tags.I think I've directly translated all the arguments passed to
setup
function in previoussetup.py
to equivalentpyproject.toml
properties, so this should retain same metadata when publishing to PyPI, other than there was previously a slight typo in one argument (pacakge_data
instead ofpackage_data
) which is now fixed. I've also added the additional requirements files as optional dependencies which can be installed withpip
using the extras syntax, for examplepip install s2fft[tests]
. I also integrated the previous content inpytest.ini
in to thepyproject.toml
file.