Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to hatch as a build backend, environment manager and publishing tool #612

Open
AnesBenmerzoug opened this issue Jul 8, 2024 · 1 comment
Labels
CI GH actions for testing and packaging enhancement New feature or request packaging Library packaging and releasing

Comments

@AnesBenmerzoug
Copy link
Collaborator

We should consider switching to hatch to simplify our setup and reduce the number of tools we use:

  • setuptools
  • twine
  • tox

See here for a comparison to other tools and reasons for using hatch.

@AnesBenmerzoug AnesBenmerzoug added enhancement New feature or request CI GH actions for testing and packaging packaging Library packaging and releasing labels Jul 8, 2024
@mdbenito
Copy link
Collaborator

mdbenito commented Jan 13, 2025

There's this wonderful principle which I really love... "if it works, don't fix it" 😄

I mean, I'm sure hatch is nice and all, but I'm also 100% sure it will have bugs, not support something basic or break in some unexpected way, just because it hasn't been tested by thousands of people for a decade, like setuptools and tox have. Don't get me wrong, I don't love our setup, but just changing to ruff I stumbled upon at least one bug that made me reconsider my life choices for a few minutes ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI GH actions for testing and packaging enhancement New feature or request packaging Library packaging and releasing
Projects
None yet
Development

No branches or pull requests

2 participants