3 comments

[ 5.3 ms ] story [ 18.3 ms ] thread
This is a huge release! I'm still getting my head around what the Python-in-hatch inversion means. I'd expect to do 'pip install --user hatch' to get hatch on my system. Does this mean that hatch itself is distributed separately from a Python installation?
Hatch itself still is written in and runs on Python but it uses its own distribution which is set up at runtime once. The goal is to provide an experience similar to other ecosystems like Rust and Go. You download the tool that does everything rather than something (Python) as a requirement for executing the tool.
How does Hatch interact with conda envs? It is possible to just use that instead of venv/virtualenv? I'm also curious about pip-compile as well