Closed jnoortheen closed 6 years ago
I think that this is because you used the -p
option after the name of the virtual environment. This should work:
pew new -p `which python3` bf
@pmav99 maybe. I am not able to reproduce that behavior anywhere else. I am closing the issue.
In a new AWS EC2 instance I installed pew using system's pip (also tried with pipsi).
Then ran the following to create a python3.6 environment. But the python version is still pointing to 2.7 even after activating the venv.