Package management

[tony]

Earlier mention: jazzband/django-robots#137 (comment)

• Poetry (PyPI, gh, docs)
• Hatch (PyPI, gh, docs)
• pipenv (PyPI, gh, docs)
• pdm (PyPI, gh, docs)
• uv (PyPI, gh, docs)
• None of the above? General comments and experiences with these?

Thoughts on standardizing these? Doing a sprint to add them?

[ofek]

I can help with Hatch! (creator)

[ofek]

django-commons/django-debug-toolbar#1690

[ofek]

prettytable/prettytable#212

[ofek]

https://github.com/jazzband/django-simple-history

[webknjaz]

This seems to mixing up packaging and workflow tools. While hatchling is good for packaging, I'd stick w/ tox for automation.

[ofek]

Is that preference out of familiarity or feature set?

[webknjaz]

Both, in part. Also personal involvement, I suppose. Additionally, I don't like to have tools overload with more than one purpose. Single-purpose tooling is easier to mix and match.
For example, I have a reusable-tox.yml project that allows adding CI jobs for tox with a few lines of YAML, skipping copy-paste of a bunch of boilerplate. This idea can be scaled to other tools but it wasn't the goal for me. It probably will at some point.
I've also been working on some tox plugins API improvements and it's now possible to have shareable toxenvs.
I'm highly interested in reducing burden as the volume of projects I'm involved in is rather big. And having multiple differing infra scaffolds is working against me in this situation. So, where possible and makes sense, I'm trying to reduce boilerplate and make it more approachable when it comes to starting new things too.