Use unittest
instead of setuptools
(where possible)
#161
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.
What are you trying to accomplish?
setuptools
has dropped its test-running capabilities in v72.Python 3.12 dropped
setuptools
from the builtins.My hope is that we'll be able to use PEP 517-compatible methods for testing on modern Pythons (#147), while still keeping the old
setup.py
method for old versions. We'll see.What approach did you choose and why?
If you are testing a pure-Python module, you can simply call
python -m unittest
to have your tests run.However, since we're a compiled C-extension, we have to create the source distribution and install it first.
What should reviewers focus on?
🤷
The impact of these changes
We are testing using the preferred method, at least for modern Pythons.