Python 3.3 venv

Open
#529 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
38/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Start by reading the virtualenvs page linked in the issue and verify how Python 3.3's built-in venv relates to the standalone virtualenv package. Done means the guide accurately explains the distinction and tells readers which option applies; the issue provides no repository file path or named test.

Written by the indexing model from the issue text.

Description

I'm still learning Python, so I could be way off here. It's from my understanding that virtualenv was a standalone package, and now Python 3 has it built-in? I didn't see that in the guide, but people online seem to repeat this information. For example: http://askubuntu.com/a/353903

This would be in reference to this page: http://docs.python-guide.org/en/latest/dev/virtualenvs/

Dominant language
Batchfile
Stars
29.8k
Forks
5.9k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from realpython/python-guide

All issues in realpython/python-guide

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.