mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-31 06:05:44 +00:00
4262e28d06
While we're addressing virtualenv foo, let's ensure we are running the latest version. This also pulls in newer versions of pip (8.1.1), setuptools (20.3), and wheel (0.29.0). MozReview-Commit-ID: G5uSy66Kd6u --HG-- extra : rebase_source : 804f230adcf77335c79a93537d9623ac3836d9bf
88 lines
3.3 KiB
Plaintext
88 lines
3.3 KiB
Plaintext
Metadata-Version: 1.1
|
|
Name: virtualenv
|
|
Version: 15.0.1
|
|
Summary: Virtual Python Environment builder
|
|
Home-page: https://virtualenv.pypa.io/
|
|
Author: Jannis Leidel, Carl Meyer and Brian Rosner
|
|
Author-email: python-virtualenv@groups.google.com
|
|
License: MIT
|
|
Description: Virtualenv
|
|
==========
|
|
|
|
`Mailing list <http://groups.google.com/group/python-virtualenv>`_ |
|
|
`Issues <https://github.com/pypa/virtualenv/issues>`_ |
|
|
`Github <https://github.com/pypa/virtualenv>`_ |
|
|
`PyPI <https://pypi.python.org/pypi/virtualenv/>`_ |
|
|
User IRC: #pypa
|
|
Dev IRC: #pypa-dev
|
|
|
|
Introduction
|
|
------------
|
|
|
|
``virtualenv`` is a tool to create isolated Python environments.
|
|
|
|
The basic problem being addressed is one of dependencies and versions,
|
|
and indirectly permissions. Imagine you have an application that
|
|
needs version 1 of LibFoo, but another application requires version
|
|
2. How can you use both these applications? If you install
|
|
everything into ``/usr/lib/python2.7/site-packages`` (or whatever your
|
|
platform's standard location is), it's easy to end up in a situation
|
|
where you unintentionally upgrade an application that shouldn't be
|
|
upgraded.
|
|
|
|
Or more generally, what if you want to install an application *and
|
|
leave it be*? If an application works, any change in its libraries or
|
|
the versions of those libraries can break the application.
|
|
|
|
Also, what if you can't install packages into the global
|
|
``site-packages`` directory? For instance, on a shared host.
|
|
|
|
In all these cases, ``virtualenv`` can help you. It creates an
|
|
environment that has its own installation directories, that doesn't
|
|
share libraries with other virtualenv environments (and optionally
|
|
doesn't access the globally installed libraries either).
|
|
|
|
.. comment:
|
|
|
|
Release History
|
|
===============
|
|
|
|
15.0.1 (2016-03-17)
|
|
-------------------
|
|
|
|
* Print error message when DEST_DIR exists and is a file
|
|
|
|
* Upgrade setuptools to 20.3
|
|
|
|
* Upgrade pip to 8.1.1.
|
|
|
|
|
|
15.0.0 (2016-03-05)
|
|
-------------------
|
|
|
|
* Remove the `virtualenv-N.N` script from the package; this can no longer be
|
|
correctly created from a wheel installation.
|
|
Resolves #851, #692
|
|
|
|
* Remove accidental runtime dependency on pip by extracting certificate in the
|
|
subprocess.
|
|
|
|
* Upgrade setuptools 20.2.2.
|
|
|
|
* Upgrade pip to 8.1.0.
|
|
|
|
|
|
`Full Changelog <https://virtualenv.pypa.io/en/latest/changes.html>`_.
|
|
Keywords: setuptools deployment installation distutils
|
|
Platform: UNKNOWN
|
|
Classifier: Development Status :: 5 - Production/Stable
|
|
Classifier: Intended Audience :: Developers
|
|
Classifier: License :: OSI Approved :: MIT License
|
|
Classifier: Programming Language :: Python :: 2
|
|
Classifier: Programming Language :: Python :: 2.6
|
|
Classifier: Programming Language :: Python :: 2.7
|
|
Classifier: Programming Language :: Python :: 3
|
|
Classifier: Programming Language :: Python :: 3.3
|
|
Classifier: Programming Language :: Python :: 3.4
|
|
Classifier: Programming Language :: Python :: 3.5
|