common-workflow-language / common-workflow-language/cwltool
switch from setuptools to hatchling?
Open
- Dominant language
- Python
- Stars
- 376
- Forks
- 255
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 12
Description
Looks like switching to [`hatchling`](https://pypi.org/project/hatchling/) from setuptools will allow us to get rid of our hack-filled `setup.py` and adopt a fully modern ([PEP 517](https://peps.python.org/pep-0517/)/[PEP 660](https://peps.python.org/pep-0660/)/([PEP 621](https://peps.python.org/pep-0621/)/[PEP 631](https://peps.python.org/pep-0631/) `pyproject.toml` build configuration for `cwltool`, `schema-salad`, etc..
`black` switched to Hatchling last year, and they had similar `mypyc`, and `setuptools-scm` hacks: https://github.com/psf/black/pull/3233
Contributor guide
Assessment
This issue has not been assessed yet.