Skip to content

Commit 70960bd

Browse files
committed
Simplify RunCode virtual environment installation and usage instructions
1 parent fc0a87e commit 70960bd

File tree

1 file changed

+10
-16
lines changed

1 file changed

+10
-16
lines changed

en/cloud_development_setup/instructions.md

Lines changed: 10 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -34,30 +34,24 @@ $ mkdir djangogirls
3434
$ cd djangogirls
3535
```
3636

37-
We will make a virtualenv called `myvenv`.
37+
We will make a virtualenv called `myvenv` by running `python3 -m venv myvenv`.
38+
It will look like this:
3839

39-
To create a new `virtualenv` on RunCode, you first need to install the `virtualenv` module. To do so, first you need to update
40-
the packages in your environment
41-
>```
42-
>$ sudo apt-get update -y
43-
>```
44-
> then install `virtualenv` by running the command:
45-
>```
46-
>$ sudo apt-get install -y virtualenv
47-
>```
40+
{% filename %}command-line{% endfilename %}
41+
```
42+
$ python3 -m venv myvenv
43+
```
4844

49-
> After this you can create the `virtualenv` run the command:
50-
>```
51-
>$ virtualenv -p python myvenv
52-
>```
53-
> and a new `virtualenv` with the name `myvenv` or whatever name you chose should be created in your `djangogirls` folder.
45+
`myvenv` is the name of your `virtualenv`. You can use any other name, but stick to lowercase and use no spaces. It is also a good idea to keep the name short as you'll be referencing it a lot!
5446

5547
## Working with a Virtual Environment
5648
>Start your virtual environment by running:
5749
>```
58-
>$ . myvenv/bin/activate
50+
>$ source myvenv/bin/activate
5951
>```
6052
53+
Remember to replace `myvenv` with your chosen `virtualenv` name!
54+
6155
### Installing packages with requirements
6256
6357
A requirements file keeps a list of dependencies to be installed using

0 commit comments

Comments
 (0)