Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add venv activation to user .bashrc #26

Merged
merged 1 commit into from
May 20, 2024

Conversation

Jongmassey
Copy link
Contributor

Fixes #20

so venv is always activated regardless of which extensions activated
@Jongmassey Jongmassey force-pushed the Jongmassey/activate-venv-bashrc branch from 92334da to 4267b9e Compare May 17, 2024 14:34
@Jongmassey Jongmassey merged commit 2174025 into main May 20, 2024
2 checks passed
@Jongmassey Jongmassey deleted the Jongmassey/activate-venv-bashrc branch May 20, 2024 07:34
Jongmassey added a commit to opensafely/research-template that referenced this pull request May 20, 2024
venv is activated prior to this script execution following
opensafely-core/research-template-docker#26
so --user installation no longer possible
Jongmassey added a commit to opensafely/research-template that referenced this pull request May 21, 2024
Following opensafely-core/research-template-docker#26
which added venv activation into .bashrc for the rstudio user (the default
user for our codespaces/devcontainer configuration), calling `pip3` would
call /opt/venv/bin/pip3. Within a virtualenv, the `--user` option is not
allowed and users reported this error. Instead we decouple the installation
of opensafely-cli from the venv so it is always available regardless of
virtualenv state.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The Python venv isn't activated in VS Code's Terminal
2 participants