[New-bugs-announce] [issue36964] `python3 -m venv NAME`: virtualenv is not portable

Marco Sulla report at bugs.python.org
Sun May 19 08:07:19 EDT 2019


New submission from Marco Sulla <launchpad.net at 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 <report at bugs.python.org>
<https://bugs.python.org/issue36964>
_______________________________________


More information about the New-bugs-announce mailing list