search

django-crispy-forms / crispy-tailwind

A Tailwind template pack for django-crispy-forms
MIT License
329 stars 56 forks source link

Automate versioning and releases #149

Closed GitRon closed 5 months ago

GitRon commented 5 months ago

Previous ticket: #147

@justinmayer He's a separate ticket so we don't mess around too much in the other one (which is unrelated to the actual task)

GitRon commented 5 months ago

Question: Would it make sense to migrate to flit? I heard it's a newer and better way for package releasing and though I use it in my packages and it works great, I have no real clue about alternatives.

justinmayer commented 5 months ago

These days there are a number of tools related to packaging, often with varying scopes and target use cases. While I have never used Flit, I have experience with other build back-ends such as PDM and Hatch/Hatchling. When it comes to the build process itself, I get the impression that all of these build back-ends perform sufficiently well when used with the Python build package as the build front-end.

I usually reach for tools like PDM / Hatch because they provide more features such as virtual environment handling and dependency management. Moreover, I prefer how they store the canonical version number in pyproject.toml instead of Flit's location inside packagename/__init__.py.

There are many articles out there that talk about how these projects differ from one another. One of the more comprehensive articles concluded that "PDM is really close to the ideal", which aligns with my own assessment as well: https://chriswarrick.com/blog/2023/01/15/how-to-improve-python-packaging/#summary

GitRon commented 5 months ago

Awesome, happy to learn why "your" solution is better than flit 🙂