[Python-Dev] Status of the built-in virtualenv functionality in 3.3 (original) (raw)
Brian Curtin brian.curtin at gmail.com
Thu Oct 6 17:06:17 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 ]
On Thu, Oct 6, 2011 at 09:12, Éric Araujo <merwok at netwok.org> 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.
How about we just drop the "virtual" part of the name and make it "env"?
(or something non-virtual)
- 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 ]