Making python virtual environments less of an annoyance to use

.bashrc.sh

venv() {
    # Check if already activated
    if [[ "$VIRTUAL_ENV" != "" ]]; then
        echo -e "\n\e[1;33mDeactivating current virtual environment...\e[0m"
        deactivate
        return
    fi

    # Check if the venv directory exists
    if [ -d "venv" ]; then
        echo -e "\n\e[1;33mActivating virtual environment...\e[0m"
        source venv/bin/activate
    else
        echo -e "\n\e[1;33mCreating and activating virtual environment...\e[0m"
        python3 -m venv venv
        source venv/bin/activate
    fi
}

For development purposes on my local box, I have all the virtual envs in a centralized location /home/$USER/virtualsevs/

Your current resource config assumes that I have (or will need) a virtual environment in the CWD. Is there a way to ask the user for the path they want to configure their virtual environment at?

I guess I can add that in but currently it just creates a venv in the default DIR which happens to be CWD by running

python3 -m venv venv

You can always change the above to be

python -m venv /path/to/new/virtual/environment