[Python-Dev] Status of the built-in virtualenv functionality in 3.3

[Carl Meyer]

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

On 10/06/2011 12:12 PM, Nick Coghlan wrote:
> sandbox is a bit close to Victor's pysandbox for restricted execution
> environments.
> 
> 'nest' would probably work, although I don't recall the 'egg'
> nomenclature featuring heavily in the current zipimport or packaging
> docs, so it may be a little obscure.
> 
> 'pyenv' is another possible colour for the shed, although a quick
> Google search suggests that may have few name clash problems.
> 
> 'appenv' would be yet another colour, since that focuses on the idea
> of 'environment per application'.

I still think 'venv' is preferable to any of the other options proposed
thus far. It makes the virtualenv "ancestry" clearer, doesn't repeat
"py" (which seems entirely unnecessary in the name of a stdlib module,
though it could be prepended to a script name if we do a script), and
doesn't try to introduce new semantic baggage to the concept, which is
already familiar to most Python devs under the name "virtualenv".

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

iEYEARECAAYFAk6N9H4ACgkQ8W4rlRKtE2doVACcChCim7CNS0czZisjEmw9NblS
MqkAn1FyT+A/UiKodCh1siHrQXf2/yZQ
=TAUV
-----END PGP SIGNATURE-----