third_party/python/virtualenv/PKG-INFO
author Andrew Halberstadt <ahalberstadt@mozilla.com>
Wed, 23 May 2018 16:07:32 -0400
changeset 419738 fdf92ddfbf862b8a2c801e06c032c01a906f7898
parent 416673 b7e922e95a70e66742557bcc485a54ed59cf118b
child 419831 1bdf8e7d1cfe6d8b9bfa891f43473345210ee281
permissions -rw-r--r--
Bug 1464038 - Upgrade vendored copy of virtualenv to version 16.0.0, r=davehunt This will in turn upgrade our version of pip from 9.0.3 -> 10.0.1 MozReview-Commit-ID: 4K7eUzgbSKk

Metadata-Version: 1.2
Name: virtualenv
Version: 16.0.0
Summary: Virtual Python Environment builder
Home-page: https://virtualenv.pypa.io/
Author: Ian Bicking
Author-email: ianb@colorstudy.com
Maintainer: Jannis Leidel, Carl Meyer and Brian Rosner
Maintainer-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
        ===============
        
        16.0.0 (2018-05-16)
        -------------------
        
        * Drop support for Python 2.6.
        
        * Upgrade pip to 10.0.1.
        
        * Upgrade setuptools to 39.1.0.
        
        * Upgrade wheel to 0.31.1.
        
        
        15.2.0 (2018-03-21)
        -------------------
        
        * Upgrade setuptools to 39.0.1.
        
        * Upgrade pip to 9.0.3.
        
        * Upgrade wheel to 0.30.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.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Programming Language :: Python :: 3.6
Requires-Python: >=2.7,!=3.0.*,!=3.1.*,!=3.2.*