Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork66
Remind user about virtualenv and using python -m#41
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Just to provide an optional hue for the bikeshed, I prefer not to activate virtual environments:
$python3 -m venv env$env/bin/python -m pip install python-docs-theme
I recognize that I'm likely a minority opinion on this, though, so this looks good as is :)
@zware: You are certainly not alone. Inever activate virtual environments, and almost never interact with them directly. Thankfully, we have tools that do these things for us. |
I'm not worried about advanced and experienced users who know what to do with venv. |
@Mariatta: I wasn't suggesting that you should hold off; given the current prevailing recommendations for workspace management, your change is the right thing. |
No description provided.