MNT: unify static configuration files into pyproject.toml, update PEP 639 license metadata#371
Conversation
neutrinoceros
force-pushed
the
mnt/pyproject-all
branch
4 times, most recently
from
fd7f385 to
2b9ae0e
Compare
| from Cython.Build import cythonize | ||
| from setuptools import Command, Extension, setup | ||
|
|
||
| # https://github.com/Unidata/cftime/issues/34 |
There was a problem hiding this comment.
note: direct invocations of setup.py as a scripts are deprecated in setuptools, so gh-34 should not be an issue now.
| requires-python = ">=3.8" | ||
|
|
||
| [dependency-groups] | ||
| dev = [ |
There was a problem hiding this comment.
note that I redefined requirements-tests.txt as a PEP 735 dependency group, which accomplishes the same thing: dev-only, and user-invisible dependencies. This PEP is already supported by pip, uv, cibuildwheel, tox and (I suspect) pdm.
neutrinoceros
force-pushed
the
mnt/pyproject-all
branch
from
2b9ae0e to
0c5df2e
Compare
…EP 639 license metadata
neutrinoceros
force-pushed
the
mnt/pyproject-all
branch
from
0c5df2e to
170e42d
Compare
|
I was able to reproduce and fix the failure locally. Hopefully this should be good to go now, unless I broke something else specifically in CI configuration. |
|
I see the build timed-out on manylinux+aarch64 (which is done via emulation). However it's not trivial to guess whether this PR has anything to do with it, given the last successful run was more than 6 months ago and its logs are long gone. |
2 participants
In preparation for a PR in the spirit of Unidata/netcdf4-python#1427, modernize the project configuration around
pyproject.toml