Repository navigation
Transition setup.py to pyproject.toml and other software tools to potentially replace tox #69
Description
I am raising this one to transition from setup.py to pyproject.toml. This is in line with the PEP 621, where the Python community selected pyproject.toml as a standard way of specifying project metadata. Similarly, in this issue we can track better software practices to improve testing experience with python standards (e.g. nox, Invoke, etc).
Investigate GitHub actions for nox, invoke
- https://github.com/marketplace/actions/setup-nox
- can we use tox with conda?
References
https://pybit.es/articles/how-to-package-and-deploy-cli-apps/
Activity
tidying up steps; updates requirements-dev and gitignore (#69)
distilling steps, adds ssh ref and updates gitignore list for dev (#69)
adds pyproject.toml and works locally, removes setup.py for the main …
optimise imports, reformats code tests/test_template (#69)
cosmetic changes to main README (#69)
removes obsolte weisslab, cmic and gitlab references (#69, #43)
adds {{cookiecutter.project_slug}}/pyproject.toml & locally tested; r…
temporally skipping test_requirements_vs_setup() for the migration to…
refactors skip condition when there is no `setup.py` and udpates ci f…
minor cosmetic changes (#69)
removing doc in ./tests/ at {{cookiecutter.project_slug}}/tox.ini (#69)
updates keyworks in pyproject.toml files (#69)
updates around tox to build docs and its requirements (#69)
remove unecessary python versions in template/tox.ini (#69)
cleaner workflow (#69)
refactoring `pyproject.toml` to pass tox local tests (#69)
passed local pytest, pylint, coverage using tox for template (#69)
remove {{cookiecutter.project_slug}}/tests/test_requirements.py (#69)