[Python-Dev] Status of the built-in virtualenv functionality in 3.3 (original) (raw)

Carl Meyer carl at oddbird.net
Thu Oct 6 18:14:28 CEST 2011

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi Éric,

Vinay is more up to date than I am on the current status of the implementation. I need to update the PEP draft we worked on last spring and get it posted (the WIP is at https://bitbucket.org/carljm/pythonv-pep but is out of date with the latest implementation work).

On 10/06/2011 08:12 AM, Éric Araujo wrote:

Oh, let’s not forget naming. We can’t reuse the module name virtualenv as it would shadow the third-party module name, and I’m not fond of “virtualize”: it brings OS-level virtualization to my mind, not isolated Python environments.

What about "venv"? It's short, it's already commonly used colloquially to refer to virtualenv so it makes an accurate and unambiguous mental association, but AFAIK it is currently unused as a script or module name.

Carl -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk6N0+QACgkQ8W4rlRKtE2fCOwCg1YOWcMCZH6HOdyKepcQG3RgB T48AoIIqol+sUpOAFI+4HJH/dAdX5Xwm =DLjq -----END PGP SIGNATURE-----

More information about the Python-Dev mailing list