Migrate to pytest + migrate to pyproject.toml #16
Conversation
christophbuermann
force-pushed
the
migrate-to-pytest
branch
from
4d68f6c to
aa09daf
Compare
|
Seems like we hit a rate limit for coverage: https://github.com/anexia/django-future-tasks/actions/runs/18406676001/job/52448125727?pr=16#step:7:34 |
There was a problem hiding this comment.
I need some guidance for the publishing workflow. This is mostly copy-pasted from: https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/
| "Programming Language :: Python :: 3.12", | ||
| "Programming Language :: Python :: 3.13", | ||
| ] | ||
| dynamic = ["version"] |
There was a problem hiding this comment.
I'm not sure if this works in conjunction with the setup.py as-is.
| [build-system] | ||
| requires = ["setuptools"] | ||
| build-backend = "setuptools.build_meta" |
There was a problem hiding this comment.
The new build installs the django_future_tasks as editable package. Therefore, we can now run the tests inside the tests instead of the root folder, and we don't need any symlinks or python path customizations.
If one uses uv, the tests can be run via uv run --all-extras pytest tests which also sets up a venv, installls all necessary packages including the django_future_tasks as editable package and/or updates anything if necessary.
2 participants
pytest.pyproject.toml.