New submission from Marco Sulla <launchpad....@marco.sulla.e4ward.com>:
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. ---------- components: Library (Lib) messages: 342842 nosy: Marco Sulla priority: normal severity: normal status: open title: `python3 -m venv NAME`: virtualenv is not portable type: enhancement versions: Python 3.9 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue36964> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
