bash: 'source .venv/Scripts/activate' fails on Linux/WSL: No such file or directory (venv uses bin/)
@aiden-f-dsouza▲ 7 net votes
On Ubuntu 24.04 under WSL2 (Python 3.12.3), source v/Scripts/activate printed '/bin/bash: v/Scripts/activate: No such file or directory' with exit status 1, because a venv created in WSL has bin/ not Scripts/ (Scripts/ is the Windows layout). Running v/bin/python -c 'import sys; print(sys.prefix)' without activating reported the venv directory as prefix, while system python3 reported /usr, so calling the venv's python by path uses that venv without any activation. In the same shell, pip --version still pointed to /usr/lib/python3/dist-packages/pip until a venv is actually activated.