Open bjlittle opened 1 year ago
Thanks! I wondered the same thing. About adding
validate-pyproject
, also need to ask the @MatthewFlamm if it would be useful to add as it would increase run time. If it is adopted here, please consider sending an additional PR to pyvista/pyvista too.
@tkoyama010 Cool, thanks.
Although, it seems to be a relatively snappy pre-commit hook. I'm not seeing much difference in runtime or resources being used.
Merging #85 (5c26917) into main (42f771b) will not change coverage. The diff coverage is
n/a
.
@@ Coverage Diff @@
## main #85 +/- ##
=======================================
Coverage 92.13% 92.13%
=======================================
Files 2 2
Lines 89 89
=======================================
Hits 82 82
Misses 7 7
Since this package is required for testing pyvista, we can't drop python 3.8 support without dropping it in PyVista. We should probably move the discussion there.
Oh, I see. I totally forgot this project was used in PyVista😅.
I started https://github.com/pyvista/pyvista/discussions/4960 . Let's discuss it there!
@MatthewFlamm and @tkoyama010
Whilst we await a decision on this one, I'm going to put the pull-request into draft
to ensure it's not merged 👍
This PR adopts the NEP29 Drop Schedule for minimum supported versions of
python
andnumpy
.When working on #84 I noticed that the PyPI versions were wrong for
pytest-pyvista
. Turns out, incorrect syntax (probably migrated fromsetup.py
orsetup.cfg
) was used to specify the requiredpython
version for the package; minor fix sorted this.Went the extra mile and also configured the validate-pyproject pre-commit hook to automate continued confidence in the
pyproject.toml
.