Issue with creating VENV

• I’m submitting a …

  • bug report
  • feature request
  • [X ] support request

• What is the current behavior? Hi Pierre, In the installation process via command line (only way to install on Linux afaik), the following step is not working for me.

xkra@computer:~/node-launcher$ python3.7 -m venv venv
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

    apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

Failing command: ['/home/xkra/node-launcher/venv/bin/python3.7', '-Im', 'ensurepip', '--upgrade', '--default-pip']

I have installed python3-venv, see as follows:

xkra@computer:~/node-launcher$ sudo apt-get install python3-venv
Reading package lists... Done
Building dependency tree       
Reading state information... Done
python3-venv is already the newest version (3.6.7-1~18.04).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

I also did the following: sudo apt-get install python-pip I am a command line n00b and have not much experience in how to fix this - would greatly appreciate if you could help me out.

• If the current behavior is a bug, please provide the steps to reproduce N/A

• What is the expected behavior? Not sure 😃

• What is the motivation / use case for changing the behavior? Get your Node Launcher running!

• Please tell us about your environment:

  • Operating System: [ Ubuntu 18.04.2 LTS]

[Sosthene00]

Hi @xkra, I just tried it on a Ubuntu 18.04, first installed python3.7.1 with sudo apt install python3.7, nothing special, but then I got tricked too by the error message that asked me to install python3-venv, because it is in fact already installed. I installed python3.7-venv instead, and after that python3.7 -m venv venv works as intended. To sum it up, sudo apt install python3.7-venv should solve your issue. [EDIT] it seems that creating a venv with the --without pip flag doesn’t allow you to install new packages, that’s why you got those error messages.

[PierreRochard]

Thank you @BobleChinois ! I’ve added that line to the readme