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

• Previous message: [Python-Dev] [Python-checkins] cpython: Fix find_module_path(): make the string ready
• Next message: [Python-Dev] Status of the built-in virtualenv functionality in 3.3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

I started to play with virtualenv recently and wondered about the status
of the similar feature in 3.3 (cpythonv).  The last thread mentioned two
bugs; one has been fixed since.

Apart from the implicit vs. explicit download of distribute, are there
design issues to discuss?  Can we do that with a patch on a bug report?

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.

Cheers

• Previous message: [Python-Dev] [Python-checkins] cpython: Fix find_module_path(): make the string ready
• Next message: [Python-Dev] Status of the built-in virtualenv functionality in 3.3
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]