After thinking about it, I don't really have a use-case for dependency locking. I only use the lock file to install dependencies under multiple Python versions. I don't track it, I don't have reproducible builds in CI (tradeoff for other maintenance benefits). So I could definitely switch to something lighter like Hatch, which simply installs dependencies using pip IIUC. Hatch also provides environments isolation, which is very interesting to me. My dev-deps pollute the version resolution of my prod-deps, while most of the time, my dev-deps work statically, so do not require having the prod-deps installed (pytest is the exception).

So, todo:

• try Hatch in an existing project, see if the migration is smooth (articles? guides?)
• see how Hatch environments fit my workflow, if their verbosity in pyproject.toml is maintainable
• see if Hatch's output is configurable: I want to retain my very minimalist output, it's non-negociable 🙂
• see the perfs: installing deps, updating deps, running check/test commands
• see if Hatch's recent ability to install compiled Python versions fits my workflow