Adopted the relatively new pyproject.toml standard for configuring Python package build and other tools in a way that still plays nice with setuptools and editable installations
Motivation and Context
A few months ago I moved (almost) all of the package configuration out of setup.py and into a declarative setup.cfg file, if only as a first step towards aligning textacy with new standards and best practices in Python packaging. This PR takes the next step.
How Has This Been Tested?
Installed textacy from scratch in a new env, CI builds are fine, all tests still pass.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation, and I have updated it accordingly.
Description
pyproject.tomlstandard for configuring Python package build and other tools in a way that still plays nice withsetuptoolsand editable installationsMotivation and Context
A few months ago I moved (almost) all of the package configuration out of
setup.pyand into a declarativesetup.cfgfile, if only as a first step towards aligningtextacywith new standards and best practices in Python packaging. This PR takes the next step.How Has This Been Tested?
Installed
textacyfrom scratch in a new env, CI builds are fine, all tests still pass.Types of changes
Checklist: