disabled virtualenvwrapper from bashrc

- because it requires the virtualenvwrapper utility /usr/local/bin/virtualenvwrapper.sh, which I don't really use (I installed it when I worked with django) so I didn't install it

fixes [https://bugzilla.ipr.univ-rennes.fr/show_bug.cgi?id=4405]
This commit is contained in:
Guillaume Raffy 2026-06-17 16:35:49 +02:00
parent 0944f9feca
commit 863e08606b
1 changed files with 13 additions and 6 deletions

View File

@ -177,10 +177,17 @@ if ! shopt -oq posix; then
fi fi
fi fi
# 14/01/2022 : graffy added virtualenvwrapper environment as suggested by https://developer.mozilla.org/en-US/docs/Learn/Server-side/Django/development_environment if false # was used for django, disabled because graffy doesn't use it anymore
export WORKON_HOME=$HOME/.virtualenvs then
export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3 # 14/01/2022 : graffy added virtualenvwrapper environment as suggested by https://developer.mozilla.org/en-US/docs/Learn/Server-side/Django/development_environment
export VIRTUALENVWRAPPER_VIRTUALENV_ARGS=' -p /usr/bin/python3 ' # virtualenvwrapper is a utility that eases the use of python virtual environments:
export PROJECT_HOME=$HOME/work/venvwrapperprojects # - Centralized Management: Stores all virtual environments in one directory (e.g., ~/.virtualenvs).
source /usr/local/bin/virtualenvwrapper.sh # - Easier Navigation: Provides commands like workon, mkvirtualenv, and rmvirtualenv to quickly switch, create, or delete environments.
# - Project Association: Allows you to associate a virtual environment with a specific project directory, so the environment is automatically activated when you cd into the project.
export WORKON_HOME=$HOME/.virtualenvs
export VIRTUALENVWRAPPER_PYTHON=/usr/bin/python3
export VIRTUALENVWRAPPER_VIRTUALENV_ARGS=' -p /usr/bin/python3 '
export PROJECT_HOME=$HOME/work/venvwrapperprojects
source /usr/local/bin/virtualenvwrapper.sh
fi