I'm not sure how to best address this, but there are some initial setup issues we encountered when using this on fresh devices tonight:
- Sometimes venv creation fails because the venv module isn't installed. The root cause of this problem is that the Ubuntu developers are morons, but this seems like a challenging problem to solve directly. I don't really want to automate the creation of
python3.12-venv or whatever, so maybe this just is what it is. (At least the extension did report the problem clearly.)
- Worse, though, the creation of the
.venv folder will succeed but then actual venv creation will fail. Then the extension freaks out and fails to re-create the venv, instead complaining that it can't find the Python interpreter. This should be fixed by letting the venv module create the .venv folder, I think.
I'm not sure how to best address this, but there are some initial setup issues we encountered when using this on fresh devices tonight:
python3.12-venvor whatever, so maybe this just is what it is. (At least the extension did report the problem clearly.).venvfolder will succeed but then actual venv creation will fail. Then the extension freaks out and fails to re-create the venv, instead complaining that it can't find the Python interpreter. This should be fixed by letting the venv module create the .venv folder, I think.