Migrate away from deprecated setup.py usages ,add pyproject.toml & update docs #653
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.
Fix deprecation warnings from setuptools by migrating project metadata to pyproject.toml and updating contributor docs.
What I changed
pyproject.toml
(PEP 518/621) and declared build backendsetuptools.build_meta
withsetuptools>=61
andwheel
.setup.py
contents with a minimal compatibility wrapper that defers to pyproject metadata (removestest
anddevelop
logic).Makefile
targetinstall
to usepython -m pip install -e .
.pip
+pytest
instead ofsetup.py develop/test
.Why
The project was using
setup.py
commands (notablydevelop
andtest
) that setuptools has deprecated and that print warnings. Moving topyproject.toml
and PEP 660-compatible editable installs avoids deprecation warnings and is the modern packaging recommended approach.Notes for maintainers
pyproject.toml
to ensuredependencies
exactly mirrorinstall_requires
from the previoussetup.py
.setuptools.build_meta
for minimal-impact migration.Closes: #647