Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-October/113885.html below:

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

• 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 ]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4