why virtualenv always creating directory with python2.7?

Question

virtual workspace always contains only python2.7

python -V
Python 3.6.5

virtualenv vitual_workspace
New python executable in vitual_workspace/bin/python2.7
Also creating executable in vitual_workspace/bin/python
Installing setuptools, pip, wheel...
done.

after activating the workspace

python -V
Python 2.7.15

try running `virtualenv virtual_workspace -p $(which python)` — Arne, Aug 20 '19 at 13:10

score 0 · Answer 1 · answered Aug 20 '19 at 13:11

0

You can create a new virtualenv with python3:

virtualenv -p python3 envname

answered Aug 20 '19 at 13:11

gCoh

2,431
1
20
39

why virtualenv always creating directory with python2.7?

1 Answers1