[Python-Dev] Status of the built-in virtualenv functionality in 3.3 (original) (raw)
Christian Heimes lists at cheimes.de
Thu Oct 6 16:49:21 CEST 2011
- Previous message: [Python-Dev] Status of the built-in virtualenv functionality in 3.3
- Next message: [Python-Dev] Status of the built-in virtualenv functionality in 3.3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 06.10.2011 16:12, schrieb Éric Araujo:
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.
How about clutch? A virtualenv is a clutch of Python eggs, all ready to hatch. (Pun intended). :)
Christian
- Previous message: [Python-Dev] Status of the built-in virtualenv functionality in 3.3
- Next message: [Python-Dev] Status of the built-in virtualenv functionality in 3.3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]