chore(python): Rename venv folder to .venv

[stinodego]

Triggered by #7782

I actually wanted to make this change a while ago. The naming of the venv folder does not matter much, but I think .venv is a bit nicer than simply venv for a few reasons, explained well in PEP 704:

The name .venv was picked since it:

• does not conflict with any valid Python import name
• does not conflict venv module in the standard library
• has pre-existing usage in the Python community
• has support for auto-detection in common text editors
• can be typed without modifier keys on common keyboard layouts

Now that maturin will offer some automatic support when using .venv, I think that's a valid reason for switching.

[konstin]

this is great, thanks!

[alexander-beedie]

(Doh... for some reason I thought you already committed this 😅 - you'll need a quick rebase).

[stinodego]

(Doh... for some reason I thought you already committed this 😅 - you'll need a quick rebase).

That's fine, I've become quite adept at rebasing 😬 and this is about as simple as they come.

[alexander-beedie]

One thing here - I wouldn't remove the original venv from the gitignore quite yet, or 18000 files will suddenly spring into being until the existing venv dir is deleted and recreated in favour of .venv 😇

[stinodego]

Yea in hindsight that was unnecessary - I'd approve a PR that re-adds it, however, probably best to delete the old folder and re-create the virtual env anyway, right?

[alexander-beedie]

Yea in hindsight that was unnecessary - I'd approve a PR that re-adds it, however, probably best to delete the old folder and re-create the virtual env anyway, right?

For sure - but it causes minor havoc until you do so; I just ran a pre-commit and typos went absolutely bananas, spraying megabytes of Jupyter notebook text into my terminal 🤣 (I guess it uses the gitignore to help it determine which directories to look at). I'll add venv back in to the PR I'm about to raise to smooth things over for now 👍

Update: here it is - #7830