Skip to content

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 15, 2020

Conversation

Mariatta
Copy link
Member

No description provided.

Copy link
Member

@zware zware left a 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 :)

@freddrake
Copy link
Member

@zware: You are certainly not alone. I never activate virtual environments, and almost never interact with them directly. Thankfully, we have tools that do these things for us.

@Mariatta
Copy link
Member Author

I'm not worried about advanced and experienced users who know what to do with venv.
This note is more for the newbies who may not have been initiated in the ways of virtual environments.

@Mariatta Mariatta merged commit 628a664 into master Jan 15, 2020
@Mariatta Mariatta deleted the Mariatta-patch-1 branch January 15, 2020 14:38
@freddrake
Copy link
Member

@Mariatta: I wasn't suggesting that you should hold off; given the current prevailing recommendations for workspace management, your change is the right thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants