Open w-k-jones opened 3 months ago
Thanks for raising this, @w-k-jones. I think this should be a high priority to get out with 1.6. Given the noise around Anaconda, we may want to consider making tobac available on PiPy at the same time.
I agree, it would be nice to add tobac to PiPy. I think we can then automate publishing new releases, as you can automate pushing from github to PiPy, and from PiPy to conda-forge.
For the pyproject.toml
file, we could start just by adding the most minimal example, and then migrating metadata from setup.py
with future releases:
[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"
As using a
pyproject.toml
file has become standard for python packages, and pip is starting to complain about installing using asetup.py
file directly, we should update tobac to the new standard. This shouldn't be too complex, as we can keep the existingsetup.py
if we are installing usingsetuptools
: https://packaging.python.org/en/latest/guides/modernize-setup-py-project/