Improve test matrix and build tools
zerolab opened this issue · comments
- move to tox for greater control e.g. test against python 3.11 (but exclude Wagtail 2.15)
- move to flit for build
- consolidate dev/test requirements
should we also consider implementing modernized packaging with pyproject.toml? With metadata per PEP 621 we can specify grouped dependencies. I'm not sure how it would impact the rest of the build and release pipeline. I've been slowly converting all of my personal project to use pyproject.toml with poetry in place of pip for dependency management.
yes to pyproject.toml, but flit for the build/release. IMHO poetry is too bloated for this.
wagtail/cookiecutter-wagtail-package#32 for reference
I only use poetry as a package manager, not a build tool... I continue to use setuptools. I'll have to check flit out after eoy.
I found the whole package/publish to PyPi experience so much nicer (and faster) with flit.
However, it doesn't do build steps, so setuptools or others are better for that
I don't think I need build steps. I pretty much only work on pure python projects... Do that extends to deps that need build steps, like pillow, psycopg, etc?