When my project uses really big dependencies like PyTorch, I like to use hatch -v to know what the h*ck is going on during the 3 to 75 minutes while it is " .. Installing project in development mode".
I first noticed that hatch -v test no longer does this, and wondered why until I realized that it is now using uv by default. That's cool, but it means that I am now using twice the disk space and network bandwidth unless I also use uv in my default environment... and also I need to make sure to set UV_EXTRA_INDEX_PATH if I don't want 10 gigabytes of NVidia garbage to download along with torch. I'll submit a documentation PR :)
But also, uv is deathly silent even when -v is passed to hatch. So, I dunno... is my network broken? Did I run out of disk space again because of those 10 gigabytes of NVidia nonsense? (yes)
When my project uses really big dependencies like PyTorch, I like to use
hatch -v
to know what the h*ck is going on during the 3 to 75 minutes while it is " .. Installing project in development mode".I first noticed that
hatch -v test
no longer does this, and wondered why until I realized that it is now usinguv
by default. That's cool, but it means that I am now using twice the disk space and network bandwidth unless I also useuv
in my default environment... and also I need to make sure to setUV_EXTRA_INDEX_PATH
if I don't want 10 gigabytes of NVidia garbage to download along withtorch
. I'll submit a documentation PR :)But also, uv is deathly silent even when
-v
is passed tohatch
. So, I dunno... is my network broken? Did I run out of disk space again because of those 10 gigabytes of NVidia nonsense? (yes)It looks like maybe we can just pass on
-v
touv
?