misc: use .venv by default instead of venv

[superlopuh]

I didn't want to have this discussion before we merged uv, but it definitely feels like it really prefers .venv, and makes lots of things easier if this name is used. How do we feel about using this name by default? It can still easily be overridden locally, but will change to .venv by default for everyone.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.15%. Comparing base (3e999aa) to head (257e25a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3629   +/-   ##
=======================================
  Coverage   90.15%   90.15%           
=======================================
  Files         465      465           
  Lines       58733    58733           
  Branches     5629     5629           
=======================================
  Hits        52949    52949           
  Misses       4345     4345           
  Partials     1439     1439           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[EdmundGoodman]

Just a note that this may break some dev phonies in the Makefile for existing users with a venv/ already generated, as it will create a new .venv directory when they are run, but not install the VENV_EXTRAS into them unless make venv is run first.

This is not necessarily a big problem as they can just run make .venv/ && rm -rf venv, but might confuse some people?

[EdmundGoodman]

The venv make target on line 32 should also be renamed to .venv, as that is now what uv sync will create

[superlopuh]

I tested it locally and make venv still creates a .venv

[compor]

exactly, that's the default

[compor]

so do we want this suggestion?

[compor]

Just a note that this may break some dev phonies in the Makefile for existing users with a venv/ already generated, as it will create a new .venv directory when they are run, but not install the VENV_EXTRAS into them unless make venv is run first.

This is not necessarily a big problem as they can just run make .venv/ && rm -rf venv, but might confuse some people?

We can't account for everything, this is what I did locally as well.
A very rudimentary competency with managing a virtual environment is a basic necessity.