Exclude venv folders from checks

[dannystaple]

Only a tiny one, but it's not uncommon on a dev setup to have a .venv folder, which these checks will try to run on.

[Gadgetoid]

Interesting, I use one big hot mess of a "dev" venv but ratifying this approach as part of the boiletplate - make dev - could be useful.

Totally haven't had builds/commands fail because I didn't have the right packages installed in whatever venv I happened to be using at the time, and then just run make dev-deps into that random venv nooo.

[dannystaple]

Interesting, I use one big hot mess of a "dev" venv but ratifying this approach as part of the boiletplate - make dev - could be useful.

Totally haven't had builds/commands fail because I didn't have the right packages installed in whatever venv I happened to be using at the time, and then just run make dev-deps into that random venv nooo.

I've been migrating stuff I've been using to uv, having previously used poetry before. It is starting to lead to much tidier venvs - but I used to use 1 or 2 venvs for many projects too. That gets harder as the number of projects I'm juggling increases so I started to mostly say 1 repo gets 1 venv.

[Gadgetoid]

I've been meaning to check out uv for a while. I'll get 'round to it... one day...

[coveralls]

Pull Request Test Coverage Report for Build 16140299768

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 91.667%

---

Totals
Change from base Build 11123021070:	0.0%
Covered Lines:	11
Relevant Lines:	12

---

💛 - Coveralls