Message342842
I'm telling about python3 -m venv VIRTUALENV_NAME, not about the virtualenv binary.
Some remarks:
1. `VIRTUAL_ENV` variable in `activate` script is the absolute path of the virtualenv folder
2. A symlink to the `python3` bin of the machine is created.
This makes the virtualenv difficult to export to another machine. The VIRTUAL_ENV variable must be manually changed.
Furthermore I do not understand why the simlink is created. I suppose that `python3` is already on the `PATH`, so what's the purpose of simlink?
I propose to makes VIRTUAL_ENV eqauls to the parent folder of the directory where `activate` resides. It makes it possible to move the virtualenv and copy it to another machine with the same OS. |
|
Date |
User |
Action |
Args |
2019-05-19 12:07:19 | Marco Sulla | set | recipients:
+ Marco Sulla |
2019-05-19 12:07:19 | Marco Sulla | set | messageid: <1558267639.25.0.0700835222258.issue36964@roundup.psfhosted.org> |
2019-05-19 12:07:19 | Marco Sulla | link | issue36964 messages |
2019-05-19 12:07:18 | Marco Sulla | create | |
|