virtualenv v1.7.2

Author: Kenneth Reitz

bin/compile

@@ -74,7 +74,7 @@ indent() {
 
 # Virtualenv wrapper.
 function virtualenv (){
-  python "$ROOT_DIR/vendor/virtualenv-1.7/virtualenv.py" "$@"
+  python "$ROOT_DIR/vendor/virtualenv-1.7.2/virtualenv.py" "$@"
 }
 
 # Buildpack Steps.

vendor/virtualenv-1.7/AUTHORS.txt renamed to vendor/virtualenv-1.7.2/AUTHORS.txt

@@ -14,20 +14,38 @@ Contributors
 ------------
 
 Alex Grönholm
+Anatoly Techtonik
 Antonio Cuni
 Armin Ronacher
+Bradley Ayers
+Cap Petschulat
+CBWhiz
 Chris McDonough
 Christian Stefanescu
 Christopher Nilsson
+Cliff Xuan
 Curt Micol
+David Schoonover
+Doug Hellmann
+Doug Napoleone
 Douglas Creager
+Ethan Jucovy
 Gunnlaugur Thor Briem
+Greg Haskins
+Jason R. Coombs
 Jeff Hammel
+Jonathan Griffin
 Jorge Vargas
 Josh Bronson
+Konstantin Zemlyak
 Kumar McMillan
 Lars Francke
+Marc Abramowitz
+Mike Hommey
+Miki Tebeka
 Philip Jenvey
+Raul Leal
 Ronny Pfannschmidt
+Stefano Rivera
 Tarek Ziadé
 Vinay Sajip

vendor/virtualenv-1.7/LICENSE.txt renamed to vendor/virtualenv-1.7.2/LICENSE.txt

@@ -1,6 +1,6 @@
 Copyright (c) 2007 Ian Bicking and Contributors
 Copyright (c) 2009 Ian Bicking, The Open Planning Project
-Copyright (c) 2011 The virtualenv developers
+Copyright (c) 2011-2012 The virtualenv developers
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

vendor/virtualenv-1.7.2/MANIFEST.in

@@ -0,0 +1,11 @@
+recursive-include bin *
+recursive-include docs *
+recursive-include scripts *
+recursive-include virtualenv_support *.egg *.tar.gz
+recursive-include virtualenv_embedded *
+recursive-exclude docs/_templates *
+recursive-exclude docs/_build *
+include virtualenv_support/__init__.py
+include *.py
+include AUTHORS.txt
+include LICENSE.txt

vendor/virtualenv-1.7/virtualenv.egg-info/PKG-INFO renamed to vendor/virtualenv-1.7.2/PKG-INFO

@@ -1,38 +1,26 @@
-Metadata-Version: 1.0
+Metadata-Version: 1.1
 Name: virtualenv
-Version: 1.7
+Version: 1.7.2
 Summary: Virtual Python Environment builder
 Home-page: http://www.virtualenv.org
 Author: Jannis Leidel, Carl Meyer and Brian Rosner
 Author-email: [email protected]
 License: MIT
 Description: 
 
-        Status and License
-        ------------------
-        
-        ``virtualenv`` is a successor to `workingenv
-        <http://cheeseshop.python.org/pypi/workingenv.py>`_, and an extension
-        of `virtual-python
-        <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_.
-        
-        It was written by Ian Bicking, sponsored by the `Open Planning
-        Project <http://openplans.org>`_ and is now maintained by a
-        `group of developers <https://github.com/pypa/virtualenv/raw/master/AUTHORS.txt>`_.
-        It is licensed under an
-        `MIT-style permissive license <https://github.com/pypa/virtualenv/raw/master/LICENSE.txt>`_.
+        Installation
+        ------------
 
-        You can install it with ``pip install virtualenv``, or the `latest
-        development version <https://github.com/pypa/virtualenv/tarball/develop#egg=virtualenv-dev>`_
-        with ``pip install virtualenv==dev``.
+        You can install virtualenv with ``pip install virtualenv``, or the `latest
+        development version <https://github.com/pypa/virtualenv/tarball/develop>`_
+        with ``pip install https://github.com/pypa/virtualenv/tarball/develop``.
 
         You can also use ``easy_install``, or if you have no Python package manager
         available at all, you can just grab the single file `virtualenv.py`_ and run
         it with ``python virtualenv.py``.
 
         .. _virtualenv.py: https://raw.github.com/pypa/virtualenv/master/virtualenv.py
 
-        
         What It Does
         ------------
 
@@ -78,9 +66,9 @@ Description:
 
             $ python virtualenv.py --distribute ENV
 
-        You can also set the environment variable VIRTUALENV_USE_DISTRIBUTE.
+        You can also set the environment variable VIRTUALENV_DISTRIBUTE.
 
-        A new virtualenv also includes the `pip <http://pypy.python.org/pypi/pip>`_
+        A new virtualenv also includes the `pip <http://pypi.python.org/pypi/pip>`_
         installer, so you can use ``ENV/bin/pip`` to install additional packages into
         the environment.
 
@@ -100,7 +88,7 @@ Description:
           For example, to automatically install Distribute instead of setuptools
           you can also set an environment variable::
 
-              $ export VIRTUALENV_USE_DISTRIBUTE=true
+              $ export VIRTUALENV_DISTRIBUTE=true
               $ python virtualenv.py ENV
 
           It's the same as passing the option to virtualenv directly::
@@ -121,7 +109,7 @@ Description:
 
           virtualenv also looks for a standard ini config file. On Unix and Mac OS X
           that's ``$HOME/.virtualenv/virtualenv.ini`` and on Windows, it's
-          ``%HOME%\\virtualenv\\virtualenv.ini``.
+          ``%APPDATA%\virtualenv\virtualenv.ini``.
 
           The names of the settings are derived from the long command line option,
           e.g. the option ``--distribute`` would look like this::
@@ -236,11 +224,12 @@ Description:
         ~~~~~~~~~~~~~~~
 
         In a newly created virtualenv there will be a ``bin/activate`` shell
-        script, or a ``Scripts/activate.bat`` batch file on Windows.
+        script. For Windows systems, activation scripts are provided for CMD.exe
+        and Powershell.
 
         On Posix systems you can do::
 
-          $ source bin/activate
+            $ source bin/activate
 
         This will change your ``$PATH`` to point to the virtualenv's ``bin/``
         directory.  (You have to use ``source`` because it changes your shell
@@ -261,9 +250,65 @@ Description:
 
         On Windows you just do::
 
-          > \path\to\env\Scripts\activate.bat
+            > \path\to\env\Scripts\activate
+        
+        And type `deactivate` to undo the changes.
+        
+        Based on your active shell (CMD.exe or Powershell.exe), Windows will use
+        either activate.bat or activate.ps1 (as appropriate) to activate the
+        virtual environment. If using Powershell, see the notes about code signing
+        below.
+        
+        .. note::
+        
+            If using Powershell, the ``activate`` script is subject to the
+            `execution policies`_ on the system. By default on Windows 7, the system's
+            excution policy is set to ``Restricted``, meaning no scripts like the
+            ``activate`` script are allowed to be executed. But that can't stop us
+            from changing that slightly to allow it to be executed.
 
-        And use ``deactivate.bat`` to undo the changes.
+            In order to use the script, you have to relax your system's execution
+            policy to ``AllSigned``, meaning all scripts on the system must be
+            digitally signed to be executed. Since the virtualenv activation
+            script is signed by one of the authors (Jannis Leidel) this level of
+            the execution policy suffices. As an administrator run::
+        
+                PS C:\> Set-ExecutionPolicy AllSigned
+        
+            Then you'll be asked to trust the signer, when executing the script.
+            You will be prompted with the following::
+        
+                PS C:\> virtualenv .\foo
+                New python executable in C:\foo\Scripts\python.exe
+                Installing setuptools................done.
+                Installing pip...................done.
+                PS C:\> .\foo\scripts\activate
+        
+                Do you want to run software from this untrusted publisher?
+                File C:\foo\scripts\activate.ps1 is published by [email protected],
+                CN=Jannis Leidel, L=Berlin, S=Berlin, C=DE, Description=581796-Gh7xfJxkxQSIO4E0
+                and is not trusted on your system. Only run scripts from trusted publishers.
+                [V] Never run  [D] Do not run  [R] Run once  [A] Always run  [?] Help
+                (default is "D"):A
+                (foo) PS C:\>
+        
+            If you select ``[A] Always Run``, the certificate will be added to the
+            Trusted Publishers of your user account, and will be trusted in this
+            user's context henceforth. If you select ``[R] Run Once``, the script will
+            be run, but you will be prometed on a subsequent invocation. Advanced users
+            can add the signer's certificate to the Trusted Publishers of the Computer
+            account to apply to all users (though this technique is out of scope of this
+            document).
+        
+            Alternatively, you may relax the system execution policy to allow running
+            of local scripts without verifying the code signature using the following::
+        
+                PS C:\> Set-ExecutionPolicy RemoteSigned
+        
+            Since the ``activate.ps1`` script is generated locally for each virtualenv,
+            it is not considered a remote script and can then be executed.
+        
+        .. _`execution policies`: http://technet.microsoft.com/en-us/library/dd347641.aspx
 
         The ``--system-site-packages`` Option
         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -376,7 +421,16 @@ Description:
         If this option is provided, virtualenv will never try to download
         setuptools/distribute or pip. Instead, it will exit with status code 1
         if it fails to find local distributions for any of these required
-        packages.
+        packages. The local distribution lookup is done in this order and the
+        following locations:
+        
+            #. The current directory.
+            #. The directory where virtualenv.py is located.
+            #. A ``virtualenv_support`` directory relative to the directory where
+               virtualenv.py is located.
+            #. If the file being executed is not named virtualenv.py (i.e. is a boot
+               script), a ``virtualenv_support`` directory relative to wherever
+               virtualenv.py is actually installed.
 
         Compare & Contrast with Alternatives
         ------------------------------------
@@ -420,13 +474,15 @@ Description:
         ------------
 
         Refer to the `contributing to pip`_ documentation - it applies equally to
-        virtualenv.
+        virtualenv, except that virtualenv issues should filed on the `virtualenv
+        repo`_ at GitHub.
 
         Virtualenv's release schedule is tied to pip's -- each time there's a new pip
         release, there will be a new virtualenv release that bundles the new version of
         pip.
 
-        .. _contributing to pip: http://www.pip-installer.org/en/latest/how-to-contribute.html
+        .. _contributing to pip: http://www.pip-installer.org/en/latest/contributing.html
+        .. _virtualenv repo: https://github.com/pypa/virtualenv/
 
         Running the tests
         ~~~~~~~~~~~~~~~~~
@@ -478,16 +534,121 @@ Description:
           <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
 
         * `virtualenv commands
-          <http://thisismedium.com/tech/extending-virtualenv/>`_ for some more
+          <https://github.com/thisismedium/virtualenv-commands>`_ for some more
           workflow-related tools around virtualenv.
 
+        Status and License
+        ------------------
+        
+        ``virtualenv`` is a successor to `workingenv
+        <http://cheeseshop.python.org/pypi/workingenv.py>`_, and an extension
+        of `virtual-python
+        <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_.
+        
+        It was written by Ian Bicking, sponsored by the `Open Planning
+        Project <http://openplans.org>`_ and is now maintained by a
+        `group of developers <https://github.com/pypa/virtualenv/raw/master/AUTHORS.txt>`_.
+        It is licensed under an
+        `MIT-style permissive license <https://github.com/pypa/virtualenv/raw/master/LICENSE.txt>`_.
+        
         Changes & News
         --------------
 
+        .. warning::
+        
+           Python bugfix releases 2.6.8, 2.7.3, 3.1.5 and 3.2.3 include a change that
+           will cause "import random" to fail with "cannot import name urandom" on any
+           virtualenv created on a Unix host with an earlier release of Python
+           2.6/2.7/3.1/3.2, if the underlying system Python is upgraded. This is due to
+           the fact that a virtualenv uses the system Python's standard library but
+           contains its own copy of the Python interpreter, so an upgrade to the system
+           Python results in a mismatch between the version of the Python interpreter
+           and the version of the standard library. It can be fixed by removing
+           ``$ENV/bin/python`` and re-running virtualenv on the same target directory
+           with the upgraded Python.
+        
+        
+        1.7.2 (2012-06-22)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Updated to distribute 0.6.27.
+        
+        * Fix activate.fish on OS X. Fixes #8. Thanks David Schoonover.
+        
+        * Create a virtualenv-x.x script with the Python version when installing, so
+          virtualenv for multiple Python versions can be installed to the same
+          script location. Thanks Miki Tebeka.
+        
+        * Restored ability to create a virtualenv with a path longer than 78
+          characters, without breaking creation of virtualenvs with non-ASCII paths.
+          Thanks, Bradley Ayers.
+        
+        * Added ability to create virtualenvs without having installed Apple's
+          developers tools (using an own implementation of ``install_name_tool``).
+          Thanks Mike Hommey.
+        
+        * Fixed PyPy and Jython support on Windows. Thanks Konstantin Zemlyak.
+        
+        * Added pydoc script to ease use. Thanks Marc Abramowitz. Fixes #149.
+        
+        * Fixed creating a bootstrap script on Python 3. Thanks Raul Leal. Fixes #280.
+        
+        * Fixed inconsistency when having set the ``PYTHONDONTWRITEBYTECODE`` env var
+          with the --distribute option or the ``VIRTUALENV_USE_DISTRIBUTE`` env var.
+          ``VIRTUALENV_USE_DISTRIBUTE`` is now considered again as a legacy alias.
+        
+        1.7.1.2 (2012-02-17)
+        ~~~~~~~~~~~~~~~~~~~~
+        
+        * Fixed minor issue in `--relocatable`. Thanks, Cap Petschulat.
+        
+        1.7.1.1 (2012-02-16)
+        ~~~~~~~~~~~~~~~~~~~~
+        
+        * Bumped the version string in ``virtualenv.py`` up, too.
+        
+        * Fixed rST rendering bug of long description.
+        
+        1.7.1 (2012-02-16)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Update embedded pip to version 1.1.
+        
+        * Fix `--relocatable` under Python 3. Thanks Doug Hellmann.
+        
+        * Added environ PATH modification to activate_this.py. Thanks Doug
+          Napoleone. Fixes #14.
+        
+        * Support creating virtualenvs directly from a Python build directory on
+          Windows. Thanks CBWhiz. Fixes #139.
+        
+        * Use non-recursive symlinks to fix things up for posix_local install
+          scheme. Thanks michr.
+        
+        * Made activate script available for use with msys and cygwin on Windows.
+          Thanks Greg Haskins, Cliff Xuan, Jonathan Griffin and Doug Napoleone.
+          Fixes #176.
+        
+        * Fixed creation of virtualenvs on Windows when Python is not installed for
+          all users. Thanks Anatoly Techtonik for report and patch and Doug
+          Napoleone for testing and confirmation. Fixes #87.
+        
+        * Fixed creation of virtualenvs using -p in installs where some modules
+          that ought to be in the standard library (e.g. `readline`) are actually
+          installed in `site-packages` next to `virtualenv.py`. Thanks Greg Haskins
+          for report and fix. Fixes #167.
+        
+        * Added activation script for Powershell (signed by Jannis Leidel). Many
+          thanks to Jason R. Coombs.
+        
         1.7 (2011-11-30)
         ~~~~~~~~~~~~~~~~
 
-        * Updated embedded Distribute release to 0.6.24. Thanks Alex Grönholm.
+        * Gave user-provided ``--extra-search-dir`` priority over default dirs for
+          finding setuptools/distribute (it already had priority for finding pip).
+          Thanks Ethan Jucovy.
+        
+        * Updated embedded Distribute release to 0.6.24. Thanks Alex Gronholm.
 
         * Made ``--no-site-packages`` behavior the default behavior.  The
           ``--no-site-packages`` flag is still permitted, but displays a warning when
@@ -645,7 +806,7 @@ Description:
         * Fix problem with ``virtualenv --relocate`` when ``bin/`` has
           subdirectories (e.g., ``bin/.svn/``); from Alan Franzoni.
 
-        * If you set ``$VIRTUALENV_USE_DISTRIBUTE`` then virtualenv will use
+        * If you set ``$VIRTUALENV_DISTRIBUTE`` then virtualenv will use
           Distribute by default (so you don't have to remember to use
           ``--distribute``).