[Python-Dev] Status of the built-in virtualenv functionality in 3.3 (original) (raw)
Vinay Sajip vinay_sajip at yahoo.co.uk
Thu Oct 6 19:34:37 CEST 2011
- Previous message: [Python-Dev] Status of the built-in virtualenv functionality in 3.3
- Next message: [Python-Dev] [Python-checkins] r88904 - tracker/instances/python-dev/html/issue.item.js
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Éric Araujo <merwok netwok.org> writes:
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.
Another possible name would be "isolate":
python -m isolate /project/env
doesn't look too bad. There's no eponymous package on PyPI, and note also that in addition to the common usage of isolate as a verb, it's also a noun with an appropriate meaning in this context.
Regards,
Vinay Sajip
- Previous message: [Python-Dev] Status of the built-in virtualenv functionality in 3.3
- Next message: [Python-Dev] [Python-checkins] r88904 - tracker/instances/python-dev/html/issue.item.js
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]