On Oct 06, 2011, at 04:12 PM, Éric Araujo wrote: >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.
Time to hit the hardware store and stock up on bikeshed paint! I agree we can't use virtualenv, and shouldn't use virtualize. I'm afraid that picking something cute might make it harder to discover. `pythonv` or `cpythonv` seem like good choices to me. Maybe the former, so we could potentially have jythonv, etc. -Barry _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
