/s/src/vendor

2026-06-05 23:10:16 +00:00 · 2012-03-23 15:59:47 -04:00
parent d87f88ee4d
commit bf2372101f
40 changed files with 0 additions and 0 deletions
@@ -0,0 +1,33 @@
+Author
+------
+
+Ian Bicking
+
+Maintainers
+-----------
+
+Brian Rosner
+Carl Meyer
+Jannis Leidel
+
+Contributors
+------------
+
+Alex Grönholm
+Antonio Cuni
+Armin Ronacher
+Chris McDonough
+Christian Stefanescu
+Christopher Nilsson
+Curt Micol
+Douglas Creager
+Gunnlaugur Thor Briem
+Jeff Hammel
+Jorge Vargas
+Josh Bronson
+Kumar McMillan
+Lars Francke
+Philip Jenvey
+Ronny Pfannschmidt
+Tarek Ziadé
+Vinay Sajip
@@ -0,0 +1,16 @@
+virtualenv
+==========
+
+See docs/index.txt for user documentation.
+
+Contributor notes
+-----------------
+
+* virtualenv is designed to work on python 2 and 3 with a single code base. 
+  Use Python 3 print-function syntax, and always use sys.exc_info()[1]
+  inside the `except` block to get at exception objects.
+
+* virtualenv uses git-flow_ to `coordinate development`_.
+
+.. _git-flow: https://github.com/nvie/gitflow
+.. _coordinate development: http://nvie.com/posts/a-successful-git-branching-model/
@@ -0,0 +1,22 @@
+Copyright (c) 2007 Ian Bicking and Contributors
+Copyright (c) 2009 Ian Bicking, The Open Planning Project
+Copyright (c) 2011 The virtualenv developers
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
@@ -0,0 +1,9 @@
+recursive-include docs *.txt
+recursive-include scripts *
+recursive-include virtualenv_support *.egg *.tar.gz
+recursive-exclude virtualenv_support *.py
+recursive-exclude docs/_templates *.*
+include virtualenv_support/__init__.py
+include *.py
+include AUTHORS.txt
+include LICENSE.txt
@@ -0,0 +1,906 @@
+Metadata-Version: 1.0
+Name: virtualenv
+Version: 1.7
+Summary: Virtual Python Environment builder
+Home-page: http://www.virtualenv.org
+Author: Jannis Leidel, Carl Meyer and Brian Rosner
+Author-email: python-virtualenv@groups.google.com
+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>`_.
+        
+        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 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
+        ------------
+        
+        ``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).
+        
+        The basic usage is::
+        
+            $ python virtualenv.py ENV
+        
+        If you install it you can also just do ``virtualenv ENV``.
+        
+        This creates ``ENV/lib/pythonX.X/site-packages``, where any libraries you
+        install will go.  It also creates ``ENV/bin/python``, which is a Python
+        interpreter that uses this environment.  Anytime you use that interpreter
+        (including when a script has ``#!/path/to/ENV/bin/python`` in it) the libraries
+        in that environment will be used.
+        
+        It also installs either `Setuptools
+        <http://peak.telecommunity.com/DevCenter/setuptools>`_ or `distribute
+        <http://pypi.python.org/pypi/distribute>`_ into the environment. To use
+        Distribute instead of setuptools, just call virtualenv like this::
+        
+            $ python virtualenv.py --distribute ENV
+        
+        You can also set the environment variable VIRTUALENV_USE_DISTRIBUTE.
+        
+        A new virtualenv also includes the `pip <http://pypy.python.org/pypi/pip>`_
+        installer, so you can use ``ENV/bin/pip`` to install additional packages into
+        the environment.
+        
+        Environment variables and configuration files
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        virtualenv can not only be configured by passing command line options such as
+        ``--distribute`` but also by two other means:
+        
+        - Environment variables
+        
+          Each command line option is automatically used to look for environment
+          variables with the name format ``VIRTUALENV_<UPPER_NAME>``. That means
+          the name of the command line options are capitalized and have dashes
+          (``'-'``) replaced with underscores (``'_'``).
+        
+          For example, to automatically install Distribute instead of setuptools
+          you can also set an environment variable::
+        
+              $ export VIRTUALENV_USE_DISTRIBUTE=true
+              $ python virtualenv.py ENV
+        
+          It's the same as passing the option to virtualenv directly::
+        
+              $ python virtualenv.py --distribute ENV
+        
+          This also works for appending command line options, like ``--find-links``.
+          Just leave an empty space between the passsed values, e.g.::
+        
+              $ export VIRTUALENV_EXTRA_SEARCH_DIR="/path/to/dists /path/to/other/dists"
+              $ virtualenv ENV
+        
+          is the same as calling::
+        
+              $ python virtualenv.py --extra-search-dir=/path/to/dists --extra-search-dir=/path/to/other/dists ENV
+        
+        - Config files
+        
+          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``.
+        
+          The names of the settings are derived from the long command line option,
+          e.g. the option ``--distribute`` would look like this::
+        
+              [virtualenv]
+              distribute = true
+        
+          Appending options like ``--extra-search-dir`` can be written on multiple
+          lines::
+        
+              [virtualenv]
+              extra-search-dir =
+                  /path/to/dists
+                  /path/to/other/dists
+        
+        Please have a look at the output of ``virtualenv --help`` for a full list
+        of supported options.
+        
+        Windows Notes
+        ~~~~~~~~~~~~~
+        
+        Some paths within the virtualenv are slightly different on Windows: scripts and
+        executables on Windows go in ``ENV\Scripts\`` instead of ``ENV/bin/`` and
+        libraries go in ``ENV\Lib\`` rather than ``ENV/lib/``.
+        
+        To create a virtualenv under a path with spaces in it on Windows, you'll need
+        the `win32api <http://sourceforge.net/projects/pywin32/>`_ library installed.
+        
+        PyPy Support
+        ~~~~~~~~~~~~
+        
+        Beginning with virtualenv version 1.5 `PyPy <http://pypy.org>`_ is
+        supported. To use PyPy 1.4 or 1.4.1, you need a version of virtualenv >= 1.5.
+        To use PyPy 1.5, you need a version of virtualenv >= 1.6.1.
+        
+        Creating Your Own Bootstrap Scripts
+        -----------------------------------
+        
+        While this creates an environment, it doesn't put anything into the
+        environment.  Developers may find it useful to distribute a script
+        that sets up a particular environment, for example a script that
+        installs a particular web application.
+        
+        To create a script like this, call
+        ``virtualenv.create_bootstrap_script(extra_text)``, and write the
+        result to your new bootstrapping script.  Here's the documentation
+        from the docstring:
+        
+        Creates a bootstrap script, which is like this script but with
+        extend_parser, adjust_options, and after_install hooks.
+        
+        This returns a string that (written to disk of course) can be used
+        as a bootstrap script with your own customizations.  The script
+        will be the standard virtualenv.py script, with your extra text
+        added (your extra text should be Python code).
+        
+        If you include these functions, they will be called:
+        
+        ``extend_parser(optparse_parser)``:
+            You can add or remove options from the parser here.
+        
+        ``adjust_options(options, args)``:
+            You can change options here, or change the args (if you accept
+            different kinds of arguments, be sure you modify ``args`` so it is
+            only ``[DEST_DIR]``).
+        
+        ``after_install(options, home_dir)``:
+        
+            After everything is installed, this function is called.  This
+            is probably the function you are most likely to use.  An
+            example would be::
+        
+                def after_install(options, home_dir):
+                    if sys.platform == 'win32':
+                        bin = 'Scripts'
+                    else:
+                        bin = 'bin'
+                    subprocess.call([join(home_dir, bin, 'easy_install'),
+                                     'MyPackage'])
+                    subprocess.call([join(home_dir, bin, 'my-package-script'),
+                                     'setup', home_dir])
+        
+            This example immediately installs a package, and runs a setup
+            script from that package.
+        
+        Bootstrap Example
+        ~~~~~~~~~~~~~~~~~
+        
+        Here's a more concrete example of how you could use this::
+        
+            import virtualenv, textwrap
+            output = virtualenv.create_bootstrap_script(textwrap.dedent("""
+            import os, subprocess
+            def after_install(options, home_dir):
+                etc = join(home_dir, 'etc')
+                if not os.path.exists(etc):
+                    os.makedirs(etc)
+                subprocess.call([join(home_dir, 'bin', 'easy_install'),
+                                 'BlogApplication'])
+                subprocess.call([join(home_dir, 'bin', 'paster'),
+                                 'make-config', 'BlogApplication',
+                                 join(etc, 'blog.ini')])
+                subprocess.call([join(home_dir, 'bin', 'paster'),
+                                 'setup-app', join(etc, 'blog.ini')])
+            """))
+            f = open('blog-bootstrap.py', 'w').write(output)
+        
+        Another example is available `here
+        <https://github.com/socialplanning/fassembler/blob/master/fassembler/create-venv-script.py>`_.
+        
+        activate script
+        ~~~~~~~~~~~~~~~
+        
+        In a newly created virtualenv there will be a ``bin/activate`` shell
+        script, or a ``Scripts/activate.bat`` batch file on Windows.
+        
+        On Posix systems you can do::
+        
+          $ 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
+        environment in-place.) This is all it does; it's purely a convenience.  If
+        you directly run a script or the python interpreter from the virtualenv's
+        ``bin/`` directory (e.g.  ``path/to/env/bin/pip`` or
+        ``/path/to/env/bin/python script.py``) there's no need for activation.
+        
+        After activating an environment you can use the function ``deactivate`` to
+        undo the changes to your ``$PATH``.
+        
+        The ``activate`` script will also modify your shell prompt to indicate
+        which environment is currently active.  You can disable this behavior,
+        which can be useful if you have your own custom prompt that already
+        displays the active environment name.  To do so, set the
+        ``VIRTUAL_ENV_DISABLE_PROMPT`` environment variable to any non-empty
+        value before running the ``activate`` script.
+        
+        On Windows you just do::
+        
+          > \path\to\env\Scripts\activate.bat
+        
+        And use ``deactivate.bat`` to undo the changes.
+        
+        The ``--system-site-packages`` Option
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        If you build with ``virtualenv --system-site-packages ENV``, your virtual
+        environment will inherit packages from ``/usr/lib/python2.7/site-packages``
+        (or wherever your global site-packages directory is).
+        
+        This can be used if you have control over the global site-packages directory,
+        and you want to depend on the packages there.  If you want isolation from the
+        global system, do not use this flag.
+        
+        Using Virtualenv without ``bin/python``
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        Sometimes you can't or don't want to use the Python interpreter
+        created by the virtualenv.  For instance, in a `mod_python
+        <http://www.modpython.org/>`_ or `mod_wsgi <http://www.modwsgi.org/>`_
+        environment, there is only one interpreter.
+        
+        Luckily, it's easy.  You must use the custom Python interpreter to
+        *install* libraries.  But to *use* libraries, you just have to be sure
+        the path is correct.  A script is available to correct the path.  You
+        can setup the environment like::
+        
+            activate_this = '/path/to/env/bin/activate_this.py'
+            execfile(activate_this, dict(__file__=activate_this))
+        
+        This will change ``sys.path`` and even change ``sys.prefix``, but also allow
+        you to use an existing interpreter.  Items in your environment will show up
+        first on ``sys.path``, before global items.  However, global items will
+        always be accessible (as if the ``--system-site-packages`` flag had been used
+        in creating the environment, whether it was or not).  Also, this cannot undo
+        the activation of other environments, or modules that have been imported.
+        You shouldn't try to, for instance, activate an environment before a web
+        request; you should activate *one* environment as early as possible, and not
+        do it again in that process.
+        
+        Making Environments Relocatable
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        Note: this option is somewhat experimental, and there are probably
+        caveats that have not yet been identified.  Also this does not
+        currently work on Windows.
+        
+        Normally environments are tied to a specific path.  That means that
+        you cannot move an environment around or copy it to another computer.
+        You can fix up an environment to make it relocatable with the
+        command::
+        
+            $ virtualenv --relocatable ENV
+        
+        This will make some of the files created by setuptools or distribute
+        use relative paths, and will change all the scripts to use ``activate_this.py``
+        instead of using the location of the Python interpreter to select the
+        environment.
+        
+        **Note:** you must run this after you've installed *any* packages into
+        the environment.  If you make an environment relocatable, then
+        install a new package, you must run ``virtualenv --relocatable``
+        again.
+        
+        Also, this **does not make your packages cross-platform**.  You can
+        move the directory around, but it can only be used on other similar
+        computers.  Some known environmental differences that can cause
+        incompatibilities: a different version of Python, when one platform
+        uses UCS2 for its internal unicode representation and another uses
+        UCS4 (a compile-time option), obvious platform changes like Windows
+        vs. Linux, or Intel vs. ARM, and if you have libraries that bind to C
+        libraries on the system, if those C libraries are located somewhere
+        different (either different versions, or a different filesystem
+        layout).
+        
+        If you use this flag to create an environment, currently, the
+        ``--system-site-packages`` option will be implied.
+        
+        The ``--extra-search-dir`` Option
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        When it creates a new environment, virtualenv installs either
+        setuptools or distribute, and pip.  In normal operation, the latest
+        releases of these packages are fetched from the `Python Package Index
+        <http://pypi.python.org>`_ (PyPI). In some circumstances, this
+        behavior may not be wanted, for example if you are using virtualenv
+        during a deployment and do not want to depend on Internet access and
+        PyPI availability.
+        
+        As an alternative, you can provide your own versions of setuptools,
+        distribute and/or pip on the filesystem, and tell virtualenv to use
+        those distributions instead of downloading them from the Internet.  To
+        use this feature, pass one or more ``--extra-search-dir`` options to
+        virtualenv like this::
+        
+            $ virtualenv --extra-search-dir=/path/to/distributions ENV
+        
+        The ``/path/to/distributions`` path should point to a directory that
+        contains setuptools, distribute and/or pip distributions.  Setuptools
+        distributions must be ``.egg`` files; distribute and pip distributions
+        should be `.tar.gz` source distributions.
+        
+        Virtualenv will still download these packages if no satisfactory local
+        distributions are found.
+        
+        If you are really concerned about virtualenv fetching these packages
+        from the Internet and want to ensure that it never will, you can also
+        provide an option ``--never-download`` like so::
+        
+            $ virtualenv --extra-search-dir=/path/to/distributions --never-download ENV
+        
+        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.
+        
+        Compare & Contrast with Alternatives
+        ------------------------------------
+        
+        There are several alternatives that create isolated environments:
+        
+        * ``workingenv`` (which I do not suggest you use anymore) is the
+          predecessor to this library.  It used the main Python interpreter,
+          but relied on setting ``$PYTHONPATH`` to activate the environment.
+          This causes problems when running Python scripts that aren't part of
+          the environment (e.g., a globally installed ``hg`` or ``bzr``).  It
+          also conflicted a lot with Setuptools.
+        
+        * `virtual-python
+          <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_
+          is also a predecessor to this library.  It uses only symlinks, so it
+          couldn't work on Windows.  It also symlinks over the *entire*
+          standard library and global ``site-packages``.  As a result, it
+          won't see new additions to the global ``site-packages``.
+        
+          This script only symlinks a small portion of the standard library
+          into the environment, and so on Windows it is feasible to simply
+          copy these files over.  Also, it creates a new/empty
+          ``site-packages`` and also adds the global ``site-packages`` to the
+          path, so updates are tracked separately.  This script also installs
+          Setuptools automatically, saving a step and avoiding the need for
+          network access.
+        
+        * `zc.buildout <http://pypi.python.org/pypi/zc.buildout>`_ doesn't
+          create an isolated Python environment in the same style, but
+          achieves similar results through a declarative config file that sets
+          up scripts with very particular packages.  As a declarative system,
+          it is somewhat easier to repeat and manage, but more difficult to
+          experiment with.  ``zc.buildout`` includes the ability to setup
+          non-Python systems (e.g., a database server or an Apache instance).
+        
+        I *strongly* recommend anyone doing application development or
+        deployment use one of these tools.
+        
+        Contributing
+        ------------
+        
+        Refer to the `contributing to pip`_ documentation - it applies equally to
+        virtualenv.
+        
+        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
+        
+        Running the tests
+        ~~~~~~~~~~~~~~~~~
+        
+        Virtualenv's test suite is small and not yet at all comprehensive, but we aim
+        to grow it.
+        
+        The easy way to run tests (handles test dependencies automatically)::
+        
+            $ python setup.py test
+        
+        If you want to run only a selection of the tests, you'll need to run them
+        directly with nose instead. Create a virtualenv, and install required
+        packages::
+        
+            $ pip install nose mock
+        
+        Run nosetests::
+        
+            $ nosetests
+        
+        Or select just a single test file to run::
+        
+            $ nosetests tests.test_virtualenv
+        
+        
+        Other Documentation and Links
+        -----------------------------
+        
+        * James Gardner has written a tutorial on using `virtualenv with
+          Pylons
+          <http://wiki.pylonshq.com/display/pylonscookbook/Using+a+Virtualenv+Sandbox>`_.
+        
+        * `Blog announcement
+          <http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/>`_.
+        
+        * Doug Hellmann wrote a description of his `command-line work flow
+          using virtualenv (virtualenvwrapper)
+          <http://www.doughellmann.com/articles/CompletelyDifferent-2008-05-virtualenvwrapper/index.html>`_
+          including some handy scripts to make working with multiple
+          environments easier.  He also wrote `an example of using virtualenv
+          to try IPython
+          <http://www.doughellmann.com/articles/CompletelyDifferent-2008-02-ipython-and-virtualenv/index.html>`_.
+        
+        * Chris Perkins created a `showmedo video including virtualenv
+          <http://showmedo.com/videos/video?name=2910000&fromSeriesID=291>`_.
+        
+        * `Using virtualenv with mod_wsgi
+          <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
+        
+        * `virtualenv commands
+          <http://thisismedium.com/tech/extending-virtualenv/>`_ for some more
+          workflow-related tools around virtualenv.
+        
+        Changes & News
+        --------------
+        
+        1.7 (2011-11-30)
+        ~~~~~~~~~~~~~~~~
+        
+        * Updated embedded Distribute release to 0.6.24. Thanks Alex Grönholm.
+        
+        * Made ``--no-site-packages`` behavior the default behavior.  The
+          ``--no-site-packages`` flag is still permitted, but displays a warning when
+          used. Thanks Chris McDonough.
+        
+        * New flag: ``--system-site-packages``; this flag should be passed to get the
+          previous default global-site-package-including behavior back.
+        
+        * Added ability to set command options as environment variables and options
+          in a ``virtualenv.ini`` file.
+        
+        * Fixed various encoding related issues with paths. Thanks Gunnlaugur Thor Briem.
+        
+        * Made ``virtualenv.py`` script executable.
+        
+        1.6.4 (2011-07-21)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Restored ability to run on Python 2.4, too.
+        
+        1.6.3 (2011-07-16)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Restored ability to run on Python < 2.7.
+        
+        1.6.2 (2011-07-16)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Updated embedded distribute release to 0.6.19.
+        
+        * Updated embedded pip release to 1.0.2.
+        
+        * Fixed #141 - Be smarter about finding pkg_resources when using the
+          non-default Python intepreter (by using the ``-p`` option).
+        
+        * Fixed #112 - Fixed path in docs.
+        
+        * Fixed #109 - Corrected doctests of a Logger method.
+        
+        * Fixed #118 - Fixed creating virtualenvs on platforms that use the
+          "posix_local" install scheme, such as Ubuntu with Python 2.7.
+        
+        * Add missing library to Python 3 virtualenvs (``_dummy_thread``).
+        
+        
+        1.6.1 (2011-04-30)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Start to use git-flow.
+        
+        * Added support for PyPy 1.5
+        
+        * Fixed #121 -- added sanity-checking of the -p argument. Thanks Paul Nasrat.
+        
+        * Added progress meter for pip installation as well as setuptools. Thanks Ethan
+          Jucovy.
+        
+        * Added --never-download and --search-dir options. Thanks Ethan Jucovy.
+        
+        1.6
+        ~~~
+        
+        * Added Python 3 support! Huge thanks to Vinay Sajip and Vitaly Babiy.
+        
+        * Fixed creation of virtualenvs on Mac OS X when standard library modules
+          (readline) are installed outside the standard library.
+        
+        * Updated bundled pip to 1.0.
+        
+        1.5.2
+        ~~~~~
+        
+        * Moved main repository to Github: https://github.com/pypa/virtualenv
+        
+        * Transferred primary maintenance from Ian to Jannis Leidel, Carl Meyer and Brian Rosner
+        
+        * Fixed a few more pypy related bugs.
+        
+        * Updated bundled pip to 0.8.2.
+        
+        * Handed project over to new team of maintainers.
+        
+        * Moved virtualenv to Github at https://github.com/pypa/virtualenv
+        
+        1.5.1
+        ~~~~~
+        
+        * Added ``_weakrefset`` requirement for Python 2.7.1.
+        
+        * Fixed Windows regression in 1.5
+        
+        1.5
+        ~~~
+        
+        * Include pip 0.8.1.
+        
+        * Add support for PyPy.
+        
+        * Uses a proper temporary dir when installing environment requirements.
+        
+        * Add ``--prompt`` option to be able to override the default prompt prefix.
+        
+        * Fix an issue with ``--relocatable`` on Windows.
+        
+        * Fix issue with installing the wrong version of distribute.
+        
+        * Add fish and csh activate scripts.
+        
+        1.4.9
+        ~~~~~
+        
+        * Include pip 0.7.2
+        
+        1.4.8
+        ~~~~~
+        
+        * Fix for Mac OS X Framework builds that use
+          ``--universal-archs=intel``
+        
+        * Fix ``activate_this.py`` on Windows.
+        
+        * Allow ``$PYTHONHOME`` to be set, so long as you use ``source
+          bin/activate`` it will get unset; if you leave it set and do not
+          activate the environment it will still break the environment.
+        
+        * Include pip 0.7.1
+        
+        1.4.7
+        ~~~~~
+        
+        * Include pip 0.7
+        
+        1.4.6
+        ~~~~~
+        
+        * Allow ``activate.sh`` to skip updating the prompt (by setting
+          ``$VIRTUAL_ENV_DISABLE_PROMPT``).
+        
+        1.4.5
+        ~~~~~
+        
+        * Include pip 0.6.3
+        
+        * Fix ``activate.bat`` and ``deactivate.bat`` under Windows when
+          ``PATH`` contained a parenthesis
+        
+        1.4.4
+        ~~~~~
+        
+        * Include pip 0.6.2 and Distribute 0.6.10
+        
+        * Create the ``virtualenv`` script even when Setuptools isn't
+          installed
+        
+        * 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
+          Distribute by default (so you don't have to remember to use
+          ``--distribute``).
+        
+        1.4.3
+        ~~~~~
+        
+        * Include pip 0.6.1
+        
+        1.4.2
+        ~~~~~
+        
+        * Fix pip installation on Windows
+        
+        * Fix use of stand-alone ``virtualenv.py`` (and boot scripts)
+        
+        * Exclude ~/.local (user site-packages) from environments when using
+          ``--no-site-packages``
+        
+        1.4.1
+        ~~~~~
+        
+        * Include pip 0.6
+        
+        1.4
+        ~~~
+        
+        * Updated setuptools to 0.6c11
+        
+        * Added the --distribute option
+        
+        * Fixed packaging problem of support-files
+        
+        1.3.4
+        ~~~~~
+        
+        * Virtualenv now copies the actual embedded Python binary on
+          Mac OS X to fix a hang on Snow Leopard (10.6).
+        
+        * Fail more gracefully on Windows when ``win32api`` is not installed.
+        
+        * Fix site-packages taking precedent over Jython's ``__classpath__``
+          and also specially handle the new ``__pyclasspath__`` entry in
+          ``sys.path``.
+        
+        * Now copies Jython's ``registry`` file to the virtualenv if it exists.
+        
+        * Better find libraries when compiling extensions on Windows.
+        
+        * Create ``Scripts\pythonw.exe`` on Windows.
+        
+        * Added support for the Debian/Ubuntu
+          ``/usr/lib/pythonX.Y/dist-packages`` directory.
+        
+        * Set ``distutils.sysconfig.get_config_vars()['LIBDIR']`` (based on
+          ``sys.real_prefix``) which is reported to help building on Windows.
+        
+        * Make ``deactivate`` work on ksh
+        
+        * Fixes for ``--python``: make it work with ``--relocatable`` and the
+          symlink created to the exact Python version.
+        
+        1.3.3
+        ~~~~~
+        
+        * Use Windows newlines in ``activate.bat``, which has been reported to help
+          when using non-ASCII directory names.
+        
+        * Fixed compatibility with Jython 2.5b1.
+        
+        * Added a function ``virtualenv.install_python`` for more fine-grained
+          access to what ``virtualenv.create_environment`` does.
+        
+        * Fix `a problem <https://bugs.launchpad.net/virtualenv/+bug/241581>`_
+          with Windows and paths that contain spaces.
+        
+        * If ``/path/to/env/.pydistutils.cfg`` exists (or
+          ``/path/to/env/pydistutils.cfg`` on Windows systems) then ignore
+          ``~/.pydistutils.cfg`` and use that other file instead.
+        
+        * Fix ` a problem
+          <https://bugs.launchpad.net/virtualenv/+bug/340050>`_ picking up
+          some ``.so`` libraries in ``/usr/local``.
+        
+        1.3.2
+        ~~~~~
+        
+        * Remove the ``[install] prefix = ...`` setting from the virtualenv
+          ``distutils.cfg`` -- this has been causing problems for a lot of
+          people, in rather obscure ways.
+        
+        * If you use a `boot script <./index.html#boot-script>`_ it will attempt to import ``virtualenv``
+          and find a pre-downloaded Setuptools egg using that.
+        
+        * Added platform-specific paths, like ``/usr/lib/pythonX.Y/plat-linux2``
+        
+        1.3.1
+        ~~~~~
+        
+        * Real Python 2.6 compatibility.  Backported the Python 2.6 updates to
+          ``site.py``, including `user directories
+          <http://docs.python.org/dev/whatsnew/2.6.html#pep-370-per-user-site-packages-directory>`_
+          (this means older versions of Python will support user directories,
+          whether intended or not).
+        
+        * Always set ``[install] prefix`` in ``distutils.cfg`` -- previously
+          on some platforms where a system-wide ``distutils.cfg`` was present
+          with a ``prefix`` setting, packages would be installed globally
+          (usually in ``/usr/local/lib/pythonX.Y/site-packages``).
+        
+        * Sometimes Cygwin seems to leave ``.exe`` off ``sys.executable``; a
+          workaround is added.
+        
+        * Fix ``--python`` option.
+        
+        * Fixed handling of Jython environments that use a
+          jython-complete.jar.
+        
+        1.3
+        ~~~
+        
+        * Update to Setuptools 0.6c9
+        * Added an option ``virtualenv --relocatable EXISTING_ENV``, which
+          will make an existing environment "relocatable" -- the paths will
+          not be absolute in scripts, ``.egg-info`` and ``.pth`` files.  This
+          may assist in building environments that can be moved and copied.
+          You have to run this *after* any new packages installed.
+        * Added ``bin/activate_this.py``, a file you can use like
+          ``execfile("path_to/activate_this.py",
+          dict(__file__="path_to/activate_this.py"))`` -- this will activate
+          the environment in place, similar to what `the mod_wsgi example
+          does <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
+        * For Mac framework builds of Python, the site-packages directory
+          ``/Library/Python/X.Y/site-packages`` is added to ``sys.path``, from
+          Andrea Rech.
+        * Some platform-specific modules in Macs are added to the path now
+          (``plat-darwin/``, ``plat-mac/``, ``plat-mac/lib-scriptpackages``),
+          from Andrea Rech.
+        * Fixed a small Bashism in the ``bin/activate`` shell script.
+        * Added ``__future__`` to the list of required modules, for Python
+          2.3.  You'll still need to backport your own ``subprocess`` module.
+        * Fixed the ``__classpath__`` entry in Jython's ``sys.path`` taking
+          precedent over virtualenv's libs.
+        
+        1.2
+        ~~~
+        
+        * Added a ``--python`` option to select the Python interpreter.
+        * Add ``warnings`` to the modules copied over, for Python 2.6 support.
+        * Add ``sets`` to the module copied over for Python 2.3 (though Python
+          2.3 still probably doesn't work).
+        
+        1.1.1
+        ~~~~~
+        
+        * Added support for Jython 2.5.
+        
+        1.1
+        ~~~
+        
+        * Added support for Python 2.6.
+        * Fix a problem with missing ``DLLs/zlib.pyd`` on Windows.  Create
+        * ``bin/python`` (or ``bin/python.exe``) even when you run virtualenv
+          with an interpreter named, e.g., ``python2.4``
+        * Fix MacPorts Python
+        * Added --unzip-setuptools option
+        * Update to Setuptools 0.6c8
+        * If the current directory is not writable, run ez_setup.py in ``/tmp``
+        * Copy or symlink over the ``include`` directory so that packages will
+          more consistently compile.
+        
+        1.0
+        ~~~
+        
+        * Fix build on systems that use ``/usr/lib64``, distinct from
+          ``/usr/lib`` (specifically CentOS x64).
+        * Fixed bug in ``--clear``.
+        * Fixed typos in ``deactivate.bat``.
+        * Preserve ``$PYTHONPATH`` when calling subprocesses.
+        
+        0.9.2
+        ~~~~~
+        
+        * Fix include dir copying on Windows (makes compiling possible).
+        * Include the main ``lib-tk`` in the path.
+        * Patch ``distutils.sysconfig``: ``get_python_inc`` and
+          ``get_python_lib`` to point to the global locations.
+        * Install ``distutils.cfg`` before Setuptools, so that system
+          customizations of ``distutils.cfg`` won't effect the installation.
+        * Add ``bin/pythonX.Y`` to the virtualenv (in addition to
+          ``bin/python``).
+        * Fixed an issue with Mac Framework Python builds, and absolute paths
+          (from Ronald Oussoren).
+        
+        0.9.1
+        ~~~~~
+        
+        * Improve ability to create a virtualenv from inside a virtualenv.
+        * Fix a little bug in ``bin/activate``.
+        * Actually get ``distutils.cfg`` to work reliably.
+        
+        0.9
+        ~~~
+        
+        * Added ``lib-dynload`` and ``config`` to things that need to be
+          copied over in an environment.
+        * Copy over or symlink the ``include`` directory, so that you can
+          build packages that need the C headers.
+        * Include a ``distutils`` package, so you can locally update
+          ``distutils.cfg`` (in ``lib/pythonX.Y/distutils/distutils.cfg``).
+        * Better avoid downloading Setuptools, and hitting PyPI on environment
+          creation.
+        * Fix a problem creating a ``lib64/`` directory.
+        * Should work on MacOSX Framework builds (the default Python
+          installations on Mac).  Thanks to Ronald Oussoren.
+        
+        0.8.4
+        ~~~~~
+        
+        * Windows installs would sometimes give errors about ``sys.prefix`` that
+          were inaccurate.
+        * Slightly prettier output.
+        
+        0.8.3
+        ~~~~~
+        
+        * Added support for Windows.
+        
+        0.8.2
+        ~~~~~
+        
+        * Give a better warning if you are on an unsupported platform (Mac
+          Framework Pythons, and Windows).
+        * Give error about running while inside a workingenv.
+        * Give better error message about Python 2.3.
+        
+        0.8.1
+        ~~~~~
+        
+        Fixed packaging of the library.
+        
+        0.8
+        ~~~
+        
+        Initial release.  Everything is changed and new!
+        
+Keywords: setuptools deployment installation distutils
+Platform: UNKNOWN
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 2
+Classifier: Programming Language :: Python :: 2.4
+Classifier: Programming Language :: Python :: 2.5
+Classifier: Programming Language :: Python :: 2.6
+Classifier: Programming Language :: Python :: 2.7
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.1
+Classifier: Programming Language :: Python :: 3.2
@@ -0,0 +1,70 @@
+#!/usr/bin/env python
+"""
+Helper script to rebuild virtualenv.py from virtualenv_support
+"""
+
+import re
+import os
+import sys
+
+here = os.path.dirname(__file__)
+script = os.path.join(here, '..', 'virtualenv.py')
+
+file_regex = re.compile(
+    r'##file (.*?)\n([a-zA-Z][a-zA-Z0-9_]+)\s*=\s*convert\("""(.*?)"""\)',
+    re.S)
+file_template = '##file %(filename)s\n%(varname)s = convert("""\n%(data)s""")'
+
+def rebuild():
+    f = open(script, 'rb')
+    content = f.read()
+    f.close()
+    parts = []
+    last_pos = 0
+    match = None
+    for match in file_regex.finditer(content):
+        parts.append(content[last_pos:match.start()])
+        last_pos = match.end()
+        filename = match.group(1)
+        varname = match.group(2)
+        data = match.group(3)
+        print('Found reference to file %s' % filename)
+        f = open(os.path.join(here, '..', 'virtualenv_support', filename), 'rb')
+        c = f.read()
+        f.close()
+        new_data = c.encode('zlib').encode('base64')
+        if new_data == data:
+            print('  Reference up to date (%s bytes)' % len(c))
+            parts.append(match.group(0))
+            continue
+        print('  Content changed (%s bytes -> %s bytes)' % (
+            zipped_len(data), len(c)))
+        new_match = file_template % dict(
+            filename=filename,
+            varname=varname,
+            data=new_data)
+        parts.append(new_match)
+    parts.append(content[last_pos:])
+    new_content = ''.join(parts)
+    if new_content != content:
+        sys.stdout.write('Content updated; overwriting... ')
+        f = open(script, 'wb')
+        f.write(new_content)
+        f.close()
+        print('done.')
+    else:
+        print('No changes in content')
+    if match is None:
+        print('No variables were matched/found')
+
+def zipped_len(data):
+    if not data:
+        return 'no data'
+    try:
+        return len(data.decode('base64').decode('zlib'))
+    except:
+        return 'unknown'
+
+if __name__ == '__main__':
+    rebuild()
+    
@@ -0,0 +1,52 @@
+#!/usr/bin/env python
+"""
+Refresh any files in ../virtualenv_support/ that come from elsewhere
+"""
+
+import os
+try:
+    from urllib.request import urlopen
+except ImportError:
+    from urllib2 import urlopen
+import sys
+
+here = os.path.dirname(__file__)
+support_files = os.path.join(here, '..', 'virtualenv_support')
+
+files = [
+    ('http://peak.telecommunity.com/dist/ez_setup.py', 'ez_setup.py'),
+    ('http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg', 'setuptools-0.6c11-py2.6.egg'),
+    ('http://pypi.python.org/packages/2.5/s/setuptools/setuptools-0.6c11-py2.5.egg', 'setuptools-0.6c11-py2.5.egg'),
+    ('http://pypi.python.org/packages/2.4/s/setuptools/setuptools-0.6c11-py2.4.egg', 'setuptools-0.6c11-py2.4.egg'),
+    ('http://python-distribute.org/distribute_setup.py', 'distribute_setup.py'),
+    ('http://pypi.python.org/packages/source/d/distribute/distribute-0.6.24.tar.gz', 'distribute-0.6.24.tar.gz'),
+    ('http://pypi.python.org/packages/source/p/pip/pip-1.0.2.tar.gz', 'pip-1.0.2.tar.gz'),
+]
+
+def main():
+    for url, filename in files:
+        sys.stdout.write('fetching %s ... ' % url)
+        sys.stdout.flush()
+        f = urlopen(url)
+        content = f.read()
+        f.close()
+        print('done.')
+        filename = os.path.join(support_files, filename)
+        if os.path.exists(filename):
+            f = open(filename, 'rb')
+            cur_content = f.read()
+            f.close()
+        else:
+            cur_content = ''
+        if cur_content == content:
+            print('  %s up-to-date' % filename)
+        else:
+            print('  overwriting %s' % filename)
+            f = open(filename, 'wb')
+            f.write(content)
+            f.close()
+
+if __name__ == '__main__':
+    main()
+
+
@@ -0,0 +1,130 @@
+# Makefile for Sphinx documentation
+#
+
+# You can set these variables from the command line.
+SPHINXOPTS    =
+SPHINXBUILD   = sphinx-build
+PAPER         =
+BUILDDIR      = _build
+
+# Internal variables.
+PAPEROPT_a4     = -D latex_paper_size=a4
+PAPEROPT_letter = -D latex_paper_size=letter
+ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
+
+.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest
+
+help:
+	@echo "Please use \`make <target>' where <target> is one of"
+	@echo "  html       to make standalone HTML files"
+	@echo "  dirhtml    to make HTML files named index.html in directories"
+	@echo "  singlehtml to make a single large HTML file"
+	@echo "  pickle     to make pickle files"
+	@echo "  json       to make JSON files"
+	@echo "  htmlhelp   to make HTML files and a HTML help project"
+	@echo "  qthelp     to make HTML files and a qthelp project"
+	@echo "  devhelp    to make HTML files and a Devhelp project"
+	@echo "  epub       to make an epub"
+	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
+	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
+	@echo "  text       to make text files"
+	@echo "  man        to make manual pages"
+	@echo "  changes    to make an overview of all changed/added/deprecated items"
+	@echo "  linkcheck  to check all external links for integrity"
+	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
+
+clean:
+	-rm -rf $(BUILDDIR)/*
+
+html:
+	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
+	@echo
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
+
+dirhtml:
+	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
+	@echo
+	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
+
+singlehtml:
+	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
+	@echo
+	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
+
+pickle:
+	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
+	@echo
+	@echo "Build finished; now you can process the pickle files."
+
+json:
+	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
+	@echo
+	@echo "Build finished; now you can process the JSON files."
+
+htmlhelp:
+	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
+	@echo
+	@echo "Build finished; now you can run HTML Help Workshop with the" \
+	      ".hhp project file in $(BUILDDIR)/htmlhelp."
+
+qthelp:
+	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
+	@echo
+	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
+	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
+	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/django-compressor.qhcp"
+	@echo "To view the help file:"
+	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/django-compressor.qhc"
+
+devhelp:
+	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
+	@echo
+	@echo "Build finished."
+	@echo "To view the help file:"
+	@echo "# mkdir -p $$HOME/.local/share/devhelp/django-compressor"
+	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/django-compressor"
+	@echo "# devhelp"
+
+epub:
+	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
+	@echo
+	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
+
+latex:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo
+	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
+	@echo "Run \`make' in that directory to run these through (pdf)latex" \
+	      "(use \`make latexpdf' here to do that automatically)."
+
+latexpdf:
+	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
+	@echo "Running LaTeX files through pdflatex..."
+	make -C $(BUILDDIR)/latex all-pdf
+	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
+
+text:
+	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
+	@echo
+	@echo "Build finished. The text files are in $(BUILDDIR)/text."
+
+man:
+	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
+	@echo
+	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
+
+changes:
+	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
+	@echo
+	@echo "The overview file is in $(BUILDDIR)/changes."
+
+linkcheck:
+	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
+	@echo
+	@echo "Link check complete; look for any errors in the above output " \
+	      "or in $(BUILDDIR)/linkcheck/output.txt."
+
+doctest:
+	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
+	@echo "Testing of doctests in the sources finished, look at the " \
+	      "results in $(BUILDDIR)/doctest/output.txt."
@@ -0,0 +1,229 @@
+/**
+ * Sphinx stylesheet -- default theme
+ * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ */
+ 
+@import url("basic.css");
+ 
+/* -- page layout ----------------------------------------------------------- */
+ 
+body {
+    font-family: Arial, sans-serif;
+    font-size: 100%;
+    background-color: #111;
+    color: #555;
+    margin: 0;
+    padding: 0;
+}
+
+div.documentwrapper {
+    float: left;
+    width: 100%;
+}
+
+div.bodywrapper {
+    margin: 0 0 0 230px;
+}
+
+hr{
+    border: 1px solid #B1B4B6;
+}
+ 
+div.document {
+    background-color: #eee;
+}
+ 
+div.body {
+    background-color: #ffffff;
+    color: #3E4349;
+    padding: 0 30px 30px 30px;
+    font-size: 0.8em;
+}
+ 
+div.footer {
+    color: #555;
+    width: 100%;
+    padding: 13px 0;
+    text-align: center;
+    font-size: 75%;
+}
+ 
+div.footer a {
+    color: #444;
+    text-decoration: underline;
+}
+ 
+div.related {
+    background-color: #6BA81E;
+    line-height: 32px;
+    color: #fff;
+    text-shadow: 0px 1px 0 #444;
+    font-size: 0.80em;
+}
+ 
+div.related a {
+    color: #E2F3CC;
+}
+ 
+div.sphinxsidebar {
+    font-size: 0.75em;
+    line-height: 1.5em;
+}
+
+div.sphinxsidebarwrapper{
+    padding: 20px 0;
+}
+ 
+div.sphinxsidebar h3,
+div.sphinxsidebar h4 {
+    font-family: Arial, sans-serif;
+    color: #222;
+    font-size: 1.2em;
+    font-weight: normal;
+    margin: 0;
+    padding: 5px 10px;
+    background-color: #ddd;
+    text-shadow: 1px 1px 0 white
+}
+
+div.sphinxsidebar h4{
+    font-size: 1.1em;
+}
+ 
+div.sphinxsidebar h3 a {
+    color: #444;
+}
+ 
+ 
+div.sphinxsidebar p {
+    color: #888;
+    padding: 5px 20px;
+}
+ 
+div.sphinxsidebar p.topless {
+}
+ 
+div.sphinxsidebar ul {
+    margin: 10px 20px;
+    padding: 0;
+    color: #000;
+}
+ 
+div.sphinxsidebar a {
+    color: #444;
+}
+ 
+div.sphinxsidebar input {
+    border: 1px solid #ccc;
+    font-family: sans-serif;
+    font-size: 1em;
+}
+
+div.sphinxsidebar input[type=text]{
+    margin-left: 20px;
+}
+ 
+/* -- body styles ----------------------------------------------------------- */
+ 
+a {
+    color: #005B81;
+    text-decoration: none;
+}
+ 
+a:hover {
+    color: #E32E00;
+    text-decoration: underline;
+}
+ 
+div.body h1,
+div.body h2,
+div.body h3,
+div.body h4,
+div.body h5,
+div.body h6 {
+    font-family: Arial, sans-serif;
+    background-color: #BED4EB;
+    font-weight: normal;
+    color: #212224;
+    margin: 30px 0px 10px 0px;
+    padding: 5px 0 5px 10px;
+    text-shadow: 0px 1px 0 white
+}
+ 
+div.body h1 { border-top: 20px solid white; margin-top: 0; font-size: 200%; }
+div.body h2 { font-size: 150%; background-color: #C8D5E3; }
+div.body h3 { font-size: 120%; background-color: #D8DEE3; }
+div.body h4 { font-size: 110%; background-color: #D8DEE3; }
+div.body h5 { font-size: 100%; background-color: #D8DEE3; }
+div.body h6 { font-size: 100%; background-color: #D8DEE3; }
+ 
+a.headerlink {
+    color: #c60f0f;
+    font-size: 0.8em;
+    padding: 0 4px 0 4px;
+    text-decoration: none;
+}
+ 
+a.headerlink:hover {
+    background-color: #c60f0f;
+    color: white;
+}
+ 
+div.body p, div.body dd, div.body li {
+    line-height: 1.5em;
+}
+ 
+div.admonition p.admonition-title + p {
+    display: inline;
+}
+
+div.highlight{
+    background-color: white;
+}
+
+div.note {
+    background-color: #eee;
+    border: 1px solid #ccc;
+}
+ 
+div.seealso {
+    background-color: #ffc;
+    border: 1px solid #ff6;
+}
+ 
+div.topic {
+    background-color: #eee;
+}
+ 
+div.warning {
+    background-color: #ffe4e4;
+    border: 1px solid #f66;
+}
+ 
+p.admonition-title {
+    display: inline;
+}
+ 
+p.admonition-title:after {
+    content: ":";
+}
+ 
+pre {
+    padding: 10px;
+    background-color: White;
+    color: #222;
+    line-height: 1.2em;
+    border: 1px solid #C6C9CB;
+    font-size: 1.2em;
+    margin: 1.5em 0 1.5em 0;
+    -webkit-box-shadow: 1px 1px 1px #d8d8d8;
+    -moz-box-shadow: 1px 1px 1px #d8d8d8;
+}
+ 
+tt {
+    background-color: #ecf0f3;
+    color: #222;
+    padding: 1px 2px;
+    font-size: 1.2em;
+    font-family: monospace;
+}
@@ -0,0 +1,54 @@
+.c { color: #999988; font-style: italic } /* Comment */
+.k { font-weight: bold } /* Keyword */
+.o { font-weight: bold } /* Operator */
+.cm { color: #999988; font-style: italic } /* Comment.Multiline */
+.cp { color: #999999; font-weight: bold } /* Comment.preproc */
+.c1 { color: #999988; font-style: italic } /* Comment.Single */
+.gd { color: #000000; background-color: #ffdddd } /* Generic.Deleted */
+.ge { font-style: italic } /* Generic.Emph */
+.gr { color: #aa0000 } /* Generic.Error */
+.gh { color: #999999 } /* Generic.Heading */
+.gi { color: #000000; background-color: #ddffdd } /* Generic.Inserted */
+.go { color: #111 } /* Generic.Output */
+.gp { color: #555555 } /* Generic.Prompt */
+.gs { font-weight: bold } /* Generic.Strong */
+.gu { color: #aaaaaa } /* Generic.Subheading */
+.gt { color: #aa0000 } /* Generic.Traceback */
+.kc { font-weight: bold } /* Keyword.Constant */
+.kd { font-weight: bold } /* Keyword.Declaration */
+.kp { font-weight: bold } /* Keyword.Pseudo */
+.kr { font-weight: bold } /* Keyword.Reserved */
+.kt { color: #445588; font-weight: bold } /* Keyword.Type */
+.m { color: #009999 } /* Literal.Number */
+.s { color: #bb8844 } /* Literal.String */
+.na { color: #008080 } /* Name.Attribute */
+.nb { color: #999999 } /* Name.Builtin */
+.nc { color: #445588; font-weight: bold } /* Name.Class */
+.no { color: #ff99ff } /* Name.Constant */
+.ni { color: #800080 } /* Name.Entity */
+.ne { color: #990000; font-weight: bold } /* Name.Exception */
+.nf { color: #990000; font-weight: bold } /* Name.Function */
+.nn { color: #555555 } /* Name.Namespace */
+.nt { color: #000080 } /* Name.Tag */
+.nv { color: purple } /* Name.Variable */
+.ow { font-weight: bold } /* Operator.Word */
+.mf { color: #009999 } /* Literal.Number.Float */
+.mh { color: #009999 } /* Literal.Number.Hex */
+.mi { color: #009999 } /* Literal.Number.Integer */
+.mo { color: #009999 } /* Literal.Number.Oct */
+.sb { color: #bb8844 } /* Literal.String.Backtick */
+.sc { color: #bb8844 } /* Literal.String.Char */
+.sd { color: #bb8844 } /* Literal.String.Doc */
+.s2 { color: #bb8844 } /* Literal.String.Double */
+.se { color: #bb8844 } /* Literal.String.Escape */
+.sh { color: #bb8844 } /* Literal.String.Heredoc */
+.si { color: #bb8844 } /* Literal.String.Interpol */
+.sx { color: #bb8844 } /* Literal.String.Other */
+.sr { color: #808000 } /* Literal.String.Regex */
+.s1 { color: #bb8844 } /* Literal.String.Single */
+.ss { color: #bb8844 } /* Literal.String.Symbol */
+.bp { color: #999999 } /* Name.Builtin.Pseudo */
+.vc { color: #ff99ff } /* Name.Variable.Class */
+.vg { color: #ff99ff } /* Name.Variable.Global */
+.vi { color: #ff99ff } /* Name.Variable.Instance */
+.il { color: #009999 } /* Literal.Number.Integer.Long */
@@ -0,0 +1,4 @@
+[theme]
+inherit = basic
+stylesheet = nature.css
+pygments_style = tango
@@ -0,0 +1,136 @@
+# -*- coding: utf-8 -*-
+#
+# Paste documentation build configuration file, created by
+# sphinx-quickstart on Tue Apr 22 22:08:49 2008.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# The contents of this file are pickled, so don't put values in the namespace
+# that aren't pickleable (module imports are okay, they're removed automatically).
+#
+# All configuration values have a default value; values that are commented out
+# serve to show the default value.
+
+import sys
+
+# If your extensions are in another directory, add it here.
+#sys.path.append('some/directory')
+
+# General configuration
+# ---------------------
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = ['sphinx.ext.autodoc']
+
+# Add any paths that contain templates here, relative to this directory.
+## FIXME: disabled for now because I haven't figured out how to use this:
+#templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.txt'
+
+# The master toctree document.
+master_doc = 'index'
+
+# General substitutions.
+project = 'virtualenv'
+copyright = '2007-2011, Ian Bicking, The Open Planning Project, The virtualenv developers'
+
+# The default replacements for |version| and |release|, also used in various
+# other places throughout the built documents.
+#
+# The short X.Y version.
+
+release = "1.7"
+version = ".".join(release.split(".")[:2])
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+today_fmt = '%B %d, %Y'
+
+# List of documents that shouldn't be included in the build.
+unused_docs = []
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+
+# Options for HTML output
+# -----------------------
+
+# The style sheet to use for HTML and HTML Help pages. A file of that name
+# must exist either in Sphinx' static/ path, or in one of the custom paths
+# given in html_static_path.
+#html_style = 'default.css'
+
+html_theme = 'nature'
+html_theme_path = ['_theme']
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Content template for the index page.
+#html_index = ''
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_use_modindex = True
+
+# If true, the reST sources are included in the HTML build as _sources/<name>.
+#html_copy_source = True
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'Pastedoc'
+
+
+# Options for LaTeX output
+# ------------------------
+
+# The paper size ('letter' or 'a4').
+#latex_paper_size = 'letter'
+
+# The font size ('10pt', '11pt' or '12pt').
+#latex_font_size = '10pt'
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, document class [howto/manual]).
+#latex_documents = []
+
+# Additional stuff for the LaTeX preamble.
+#latex_preamble = ''
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_use_modindex = True
@@ -0,0 +1,487 @@
+virtualenv
+==========
+
+* `Discussion list <http://groups.google.com/group/python-virtualenv/>`_
+* `Bugs <https://github.com/pypa/virtualenv/issues/>`_
+
+.. contents::
+
+.. toctree::
+   :maxdepth: 1
+
+   news
+
+.. comment: split here
+
+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>`_.
+
+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 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
+------------
+
+``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).
+
+The basic usage is::
+
+    $ python virtualenv.py ENV
+
+If you install it you can also just do ``virtualenv ENV``.
+
+This creates ``ENV/lib/pythonX.X/site-packages``, where any libraries you
+install will go.  It also creates ``ENV/bin/python``, which is a Python
+interpreter that uses this environment.  Anytime you use that interpreter
+(including when a script has ``#!/path/to/ENV/bin/python`` in it) the libraries
+in that environment will be used.
+
+It also installs either `Setuptools
+<http://peak.telecommunity.com/DevCenter/setuptools>`_ or `distribute
+<http://pypi.python.org/pypi/distribute>`_ into the environment. To use
+Distribute instead of setuptools, just call virtualenv like this::
+
+    $ python virtualenv.py --distribute ENV
+
+You can also set the environment variable VIRTUALENV_USE_DISTRIBUTE.
+
+A new virtualenv also includes the `pip <http://pypy.python.org/pypi/pip>`_
+installer, so you can use ``ENV/bin/pip`` to install additional packages into
+the environment.
+
+Environment variables and configuration files
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+virtualenv can not only be configured by passing command line options such as
+``--distribute`` but also by two other means:
+
+- Environment variables
+
+  Each command line option is automatically used to look for environment
+  variables with the name format ``VIRTUALENV_<UPPER_NAME>``. That means
+  the name of the command line options are capitalized and have dashes
+  (``'-'``) replaced with underscores (``'_'``).
+
+  For example, to automatically install Distribute instead of setuptools
+  you can also set an environment variable::
+
+      $ export VIRTUALENV_USE_DISTRIBUTE=true
+      $ python virtualenv.py ENV
+
+  It's the same as passing the option to virtualenv directly::
+
+      $ python virtualenv.py --distribute ENV
+
+  This also works for appending command line options, like ``--find-links``.
+  Just leave an empty space between the passsed values, e.g.::
+
+      $ export VIRTUALENV_EXTRA_SEARCH_DIR="/path/to/dists /path/to/other/dists"
+      $ virtualenv ENV
+
+  is the same as calling::
+
+      $ python virtualenv.py --extra-search-dir=/path/to/dists --extra-search-dir=/path/to/other/dists ENV
+
+- Config files
+
+  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``.
+
+  The names of the settings are derived from the long command line option,
+  e.g. the option ``--distribute`` would look like this::
+
+      [virtualenv]
+      distribute = true
+
+  Appending options like ``--extra-search-dir`` can be written on multiple
+  lines::
+
+      [virtualenv]
+      extra-search-dir =
+          /path/to/dists
+          /path/to/other/dists
+
+Please have a look at the output of ``virtualenv --help`` for a full list
+of supported options.
+
+Windows Notes
+~~~~~~~~~~~~~
+
+Some paths within the virtualenv are slightly different on Windows: scripts and
+executables on Windows go in ``ENV\Scripts\`` instead of ``ENV/bin/`` and
+libraries go in ``ENV\Lib\`` rather than ``ENV/lib/``.
+
+To create a virtualenv under a path with spaces in it on Windows, you'll need
+the `win32api <http://sourceforge.net/projects/pywin32/>`_ library installed.
+
+PyPy Support
+~~~~~~~~~~~~
+
+Beginning with virtualenv version 1.5 `PyPy <http://pypy.org>`_ is
+supported. To use PyPy 1.4 or 1.4.1, you need a version of virtualenv >= 1.5.
+To use PyPy 1.5, you need a version of virtualenv >= 1.6.1.
+
+Creating Your Own Bootstrap Scripts
+-----------------------------------
+
+While this creates an environment, it doesn't put anything into the
+environment.  Developers may find it useful to distribute a script
+that sets up a particular environment, for example a script that
+installs a particular web application.
+
+To create a script like this, call
+``virtualenv.create_bootstrap_script(extra_text)``, and write the
+result to your new bootstrapping script.  Here's the documentation
+from the docstring:
+
+Creates a bootstrap script, which is like this script but with
+extend_parser, adjust_options, and after_install hooks.
+
+This returns a string that (written to disk of course) can be used
+as a bootstrap script with your own customizations.  The script
+will be the standard virtualenv.py script, with your extra text
+added (your extra text should be Python code).
+
+If you include these functions, they will be called:
+
+``extend_parser(optparse_parser)``:
+    You can add or remove options from the parser here.
+
+``adjust_options(options, args)``:
+    You can change options here, or change the args (if you accept
+    different kinds of arguments, be sure you modify ``args`` so it is
+    only ``[DEST_DIR]``).
+
+``after_install(options, home_dir)``:
+
+    After everything is installed, this function is called.  This
+    is probably the function you are most likely to use.  An
+    example would be::
+
+        def after_install(options, home_dir):
+            if sys.platform == 'win32':
+                bin = 'Scripts'
+            else:
+                bin = 'bin'
+            subprocess.call([join(home_dir, bin, 'easy_install'),
+                             'MyPackage'])
+            subprocess.call([join(home_dir, bin, 'my-package-script'),
+                             'setup', home_dir])
+
+    This example immediately installs a package, and runs a setup
+    script from that package.
+
+Bootstrap Example
+~~~~~~~~~~~~~~~~~
+
+Here's a more concrete example of how you could use this::
+
+    import virtualenv, textwrap
+    output = virtualenv.create_bootstrap_script(textwrap.dedent("""
+    import os, subprocess
+    def after_install(options, home_dir):
+        etc = join(home_dir, 'etc')
+        if not os.path.exists(etc):
+            os.makedirs(etc)
+        subprocess.call([join(home_dir, 'bin', 'easy_install'),
+                         'BlogApplication'])
+        subprocess.call([join(home_dir, 'bin', 'paster'),
+                         'make-config', 'BlogApplication',
+                         join(etc, 'blog.ini')])
+        subprocess.call([join(home_dir, 'bin', 'paster'),
+                         'setup-app', join(etc, 'blog.ini')])
+    """))
+    f = open('blog-bootstrap.py', 'w').write(output)
+
+Another example is available `here
+<https://github.com/socialplanning/fassembler/blob/master/fassembler/create-venv-script.py>`_.
+
+activate script
+~~~~~~~~~~~~~~~
+
+In a newly created virtualenv there will be a ``bin/activate`` shell
+script, or a ``Scripts/activate.bat`` batch file on Windows.
+
+On Posix systems you can do::
+
+  $ 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
+environment in-place.) This is all it does; it's purely a convenience.  If
+you directly run a script or the python interpreter from the virtualenv's
+``bin/`` directory (e.g.  ``path/to/env/bin/pip`` or
+``/path/to/env/bin/python script.py``) there's no need for activation.
+
+After activating an environment you can use the function ``deactivate`` to
+undo the changes to your ``$PATH``.
+
+The ``activate`` script will also modify your shell prompt to indicate
+which environment is currently active.  You can disable this behavior,
+which can be useful if you have your own custom prompt that already
+displays the active environment name.  To do so, set the
+``VIRTUAL_ENV_DISABLE_PROMPT`` environment variable to any non-empty
+value before running the ``activate`` script.
+
+On Windows you just do::
+
+  > \path\to\env\Scripts\activate.bat
+
+And use ``deactivate.bat`` to undo the changes.
+
+The ``--system-site-packages`` Option
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+If you build with ``virtualenv --system-site-packages ENV``, your virtual
+environment will inherit packages from ``/usr/lib/python2.7/site-packages``
+(or wherever your global site-packages directory is).
+
+This can be used if you have control over the global site-packages directory,
+and you want to depend on the packages there.  If you want isolation from the
+global system, do not use this flag.
+
+Using Virtualenv without ``bin/python``
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Sometimes you can't or don't want to use the Python interpreter
+created by the virtualenv.  For instance, in a `mod_python
+<http://www.modpython.org/>`_ or `mod_wsgi <http://www.modwsgi.org/>`_
+environment, there is only one interpreter.
+
+Luckily, it's easy.  You must use the custom Python interpreter to
+*install* libraries.  But to *use* libraries, you just have to be sure
+the path is correct.  A script is available to correct the path.  You
+can setup the environment like::
+
+    activate_this = '/path/to/env/bin/activate_this.py'
+    execfile(activate_this, dict(__file__=activate_this))
+
+This will change ``sys.path`` and even change ``sys.prefix``, but also allow
+you to use an existing interpreter.  Items in your environment will show up
+first on ``sys.path``, before global items.  However, global items will
+always be accessible (as if the ``--system-site-packages`` flag had been used
+in creating the environment, whether it was or not).  Also, this cannot undo
+the activation of other environments, or modules that have been imported.
+You shouldn't try to, for instance, activate an environment before a web
+request; you should activate *one* environment as early as possible, and not
+do it again in that process.
+
+Making Environments Relocatable
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Note: this option is somewhat experimental, and there are probably
+caveats that have not yet been identified.  Also this does not
+currently work on Windows.
+
+Normally environments are tied to a specific path.  That means that
+you cannot move an environment around or copy it to another computer.
+You can fix up an environment to make it relocatable with the
+command::
+
+    $ virtualenv --relocatable ENV
+
+This will make some of the files created by setuptools or distribute
+use relative paths, and will change all the scripts to use ``activate_this.py``
+instead of using the location of the Python interpreter to select the
+environment.
+
+**Note:** you must run this after you've installed *any* packages into
+the environment.  If you make an environment relocatable, then
+install a new package, you must run ``virtualenv --relocatable``
+again.
+
+Also, this **does not make your packages cross-platform**.  You can
+move the directory around, but it can only be used on other similar
+computers.  Some known environmental differences that can cause
+incompatibilities: a different version of Python, when one platform
+uses UCS2 for its internal unicode representation and another uses
+UCS4 (a compile-time option), obvious platform changes like Windows
+vs. Linux, or Intel vs. ARM, and if you have libraries that bind to C
+libraries on the system, if those C libraries are located somewhere
+different (either different versions, or a different filesystem
+layout).
+
+If you use this flag to create an environment, currently, the
+``--system-site-packages`` option will be implied.
+
+The ``--extra-search-dir`` Option
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+When it creates a new environment, virtualenv installs either
+setuptools or distribute, and pip.  In normal operation, the latest
+releases of these packages are fetched from the `Python Package Index
+<http://pypi.python.org>`_ (PyPI). In some circumstances, this
+behavior may not be wanted, for example if you are using virtualenv
+during a deployment and do not want to depend on Internet access and
+PyPI availability.
+
+As an alternative, you can provide your own versions of setuptools,
+distribute and/or pip on the filesystem, and tell virtualenv to use
+those distributions instead of downloading them from the Internet.  To
+use this feature, pass one or more ``--extra-search-dir`` options to
+virtualenv like this::
+
+    $ virtualenv --extra-search-dir=/path/to/distributions ENV
+
+The ``/path/to/distributions`` path should point to a directory that
+contains setuptools, distribute and/or pip distributions.  Setuptools
+distributions must be ``.egg`` files; distribute and pip distributions
+should be `.tar.gz` source distributions.
+
+Virtualenv will still download these packages if no satisfactory local
+distributions are found.
+
+If you are really concerned about virtualenv fetching these packages
+from the Internet and want to ensure that it never will, you can also
+provide an option ``--never-download`` like so::
+
+    $ virtualenv --extra-search-dir=/path/to/distributions --never-download ENV
+
+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.
+
+Compare & Contrast with Alternatives
+------------------------------------
+
+There are several alternatives that create isolated environments:
+
+* ``workingenv`` (which I do not suggest you use anymore) is the
+  predecessor to this library.  It used the main Python interpreter,
+  but relied on setting ``$PYTHONPATH`` to activate the environment.
+  This causes problems when running Python scripts that aren't part of
+  the environment (e.g., a globally installed ``hg`` or ``bzr``).  It
+  also conflicted a lot with Setuptools.
+
+* `virtual-python
+  <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_
+  is also a predecessor to this library.  It uses only symlinks, so it
+  couldn't work on Windows.  It also symlinks over the *entire*
+  standard library and global ``site-packages``.  As a result, it
+  won't see new additions to the global ``site-packages``.
+
+  This script only symlinks a small portion of the standard library
+  into the environment, and so on Windows it is feasible to simply
+  copy these files over.  Also, it creates a new/empty
+  ``site-packages`` and also adds the global ``site-packages`` to the
+  path, so updates are tracked separately.  This script also installs
+  Setuptools automatically, saving a step and avoiding the need for
+  network access.
+
+* `zc.buildout <http://pypi.python.org/pypi/zc.buildout>`_ doesn't
+  create an isolated Python environment in the same style, but
+  achieves similar results through a declarative config file that sets
+  up scripts with very particular packages.  As a declarative system,
+  it is somewhat easier to repeat and manage, but more difficult to
+  experiment with.  ``zc.buildout`` includes the ability to setup
+  non-Python systems (e.g., a database server or an Apache instance).
+
+I *strongly* recommend anyone doing application development or
+deployment use one of these tools.
+
+Contributing
+------------
+
+Refer to the `contributing to pip`_ documentation - it applies equally to
+virtualenv.
+
+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
+
+Running the tests
+~~~~~~~~~~~~~~~~~
+
+Virtualenv's test suite is small and not yet at all comprehensive, but we aim
+to grow it.
+
+The easy way to run tests (handles test dependencies automatically)::
+
+    $ python setup.py test
+
+If you want to run only a selection of the tests, you'll need to run them
+directly with nose instead. Create a virtualenv, and install required
+packages::
+
+    $ pip install nose mock
+
+Run nosetests::
+
+    $ nosetests
+
+Or select just a single test file to run::
+
+    $ nosetests tests.test_virtualenv
+
+
+Other Documentation and Links
+-----------------------------
+
+* James Gardner has written a tutorial on using `virtualenv with
+  Pylons
+  <http://wiki.pylonshq.com/display/pylonscookbook/Using+a+Virtualenv+Sandbox>`_.
+
+* `Blog announcement
+  <http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/>`_.
+
+* Doug Hellmann wrote a description of his `command-line work flow
+  using virtualenv (virtualenvwrapper)
+  <http://www.doughellmann.com/articles/CompletelyDifferent-2008-05-virtualenvwrapper/index.html>`_
+  including some handy scripts to make working with multiple
+  environments easier.  He also wrote `an example of using virtualenv
+  to try IPython
+  <http://www.doughellmann.com/articles/CompletelyDifferent-2008-02-ipython-and-virtualenv/index.html>`_.
+
+* Chris Perkins created a `showmedo video including virtualenv
+  <http://showmedo.com/videos/video?name=2910000&fromSeriesID=291>`_.
+
+* `Using virtualenv with mod_wsgi
+  <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
+
+* `virtualenv commands
+  <http://thisismedium.com/tech/extending-virtualenv/>`_ for some more
+  workflow-related tools around virtualenv.
@@ -0,0 +1,170 @@
+@ECHO OFF
+
+REM Command file for Sphinx documentation
+
+if "%SPHINXBUILD%" == "" (
+	set SPHINXBUILD=sphinx-build
+)
+set BUILDDIR=_build
+set ALLSPHINXOPTS=-d %BUILDDIR%/doctrees %SPHINXOPTS% .
+if NOT "%PAPER%" == "" (
+	set ALLSPHINXOPTS=-D latex_paper_size=%PAPER% %ALLSPHINXOPTS%
+)
+
+if "%1" == "" goto help
+
+if "%1" == "help" (
+	:help
+	echo.Please use `make ^<target^>` where ^<target^> is one of
+	echo.  html       to make standalone HTML files
+	echo.  dirhtml    to make HTML files named index.html in directories
+	echo.  singlehtml to make a single large HTML file
+	echo.  pickle     to make pickle files
+	echo.  json       to make JSON files
+	echo.  htmlhelp   to make HTML files and a HTML help project
+	echo.  qthelp     to make HTML files and a qthelp project
+	echo.  devhelp    to make HTML files and a Devhelp project
+	echo.  epub       to make an epub
+	echo.  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter
+	echo.  text       to make text files
+	echo.  man        to make manual pages
+	echo.  changes    to make an overview over all changed/added/deprecated items
+	echo.  linkcheck  to check all external links for integrity
+	echo.  doctest    to run all doctests embedded in the documentation if enabled
+	goto end
+)
+
+if "%1" == "clean" (
+	for /d %%i in (%BUILDDIR%\*) do rmdir /q /s %%i
+	del /q /s %BUILDDIR%\*
+	goto end
+)
+
+if "%1" == "html" (
+	%SPHINXBUILD% -b html %ALLSPHINXOPTS% %BUILDDIR%/html
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished. The HTML pages are in %BUILDDIR%/html.
+	goto end
+)
+
+if "%1" == "dirhtml" (
+	%SPHINXBUILD% -b dirhtml %ALLSPHINXOPTS% %BUILDDIR%/dirhtml
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished. The HTML pages are in %BUILDDIR%/dirhtml.
+	goto end
+)
+
+if "%1" == "singlehtml" (
+	%SPHINXBUILD% -b singlehtml %ALLSPHINXOPTS% %BUILDDIR%/singlehtml
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished. The HTML pages are in %BUILDDIR%/singlehtml.
+	goto end
+)
+
+if "%1" == "pickle" (
+	%SPHINXBUILD% -b pickle %ALLSPHINXOPTS% %BUILDDIR%/pickle
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished; now you can process the pickle files.
+	goto end
+)
+
+if "%1" == "json" (
+	%SPHINXBUILD% -b json %ALLSPHINXOPTS% %BUILDDIR%/json
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished; now you can process the JSON files.
+	goto end
+)
+
+if "%1" == "htmlhelp" (
+	%SPHINXBUILD% -b htmlhelp %ALLSPHINXOPTS% %BUILDDIR%/htmlhelp
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished; now you can run HTML Help Workshop with the ^
+.hhp project file in %BUILDDIR%/htmlhelp.
+	goto end
+)
+
+if "%1" == "qthelp" (
+	%SPHINXBUILD% -b qthelp %ALLSPHINXOPTS% %BUILDDIR%/qthelp
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished; now you can run "qcollectiongenerator" with the ^
+.qhcp project file in %BUILDDIR%/qthelp, like this:
+	echo.^> qcollectiongenerator %BUILDDIR%\qthelp\django-compressor.qhcp
+	echo.To view the help file:
+	echo.^> assistant -collectionFile %BUILDDIR%\qthelp\django-compressor.ghc
+	goto end
+)
+
+if "%1" == "devhelp" (
+	%SPHINXBUILD% -b devhelp %ALLSPHINXOPTS% %BUILDDIR%/devhelp
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished.
+	goto end
+)
+
+if "%1" == "epub" (
+	%SPHINXBUILD% -b epub %ALLSPHINXOPTS% %BUILDDIR%/epub
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished. The epub file is in %BUILDDIR%/epub.
+	goto end
+)
+
+if "%1" == "latex" (
+	%SPHINXBUILD% -b latex %ALLSPHINXOPTS% %BUILDDIR%/latex
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished; the LaTeX files are in %BUILDDIR%/latex.
+	goto end
+)
+
+if "%1" == "text" (
+	%SPHINXBUILD% -b text %ALLSPHINXOPTS% %BUILDDIR%/text
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished. The text files are in %BUILDDIR%/text.
+	goto end
+)
+
+if "%1" == "man" (
+	%SPHINXBUILD% -b man %ALLSPHINXOPTS% %BUILDDIR%/man
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Build finished. The manual pages are in %BUILDDIR%/man.
+	goto end
+)
+
+if "%1" == "changes" (
+	%SPHINXBUILD% -b changes %ALLSPHINXOPTS% %BUILDDIR%/changes
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.The overview file is in %BUILDDIR%/changes.
+	goto end
+)
+
+if "%1" == "linkcheck" (
+	%SPHINXBUILD% -b linkcheck %ALLSPHINXOPTS% %BUILDDIR%/linkcheck
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Link check complete; look for any errors in the above output ^
+or in %BUILDDIR%/linkcheck/output.txt.
+	goto end
+)
+
+if "%1" == "doctest" (
+	%SPHINXBUILD% -b doctest %ALLSPHINXOPTS% %BUILDDIR%/doctest
+	if errorlevel 1 exit /b 1
+	echo.
+	echo.Testing of doctests in the sources finished, look at the ^
+results in %BUILDDIR%/doctest/output.txt.
+	goto end
+)
+
+:end
@@ -0,0 +1,409 @@
+Changes & News
+--------------
+
+1.7 (2011-11-30)
+~~~~~~~~~~~~~~~~
+
+* Updated embedded Distribute release to 0.6.24. Thanks Alex Grönholm.
+
+* Made ``--no-site-packages`` behavior the default behavior.  The
+  ``--no-site-packages`` flag is still permitted, but displays a warning when
+  used. Thanks Chris McDonough.
+
+* New flag: ``--system-site-packages``; this flag should be passed to get the
+  previous default global-site-package-including behavior back.
+
+* Added ability to set command options as environment variables and options
+  in a ``virtualenv.ini`` file.
+
+* Fixed various encoding related issues with paths. Thanks Gunnlaugur Thor Briem.
+
+* Made ``virtualenv.py`` script executable.
+
+1.6.4 (2011-07-21)
+~~~~~~~~~~~~~~~~~~
+
+* Restored ability to run on Python 2.4, too.
+
+1.6.3 (2011-07-16)
+~~~~~~~~~~~~~~~~~~
+
+* Restored ability to run on Python < 2.7.
+
+1.6.2 (2011-07-16)
+~~~~~~~~~~~~~~~~~~
+
+* Updated embedded distribute release to 0.6.19.
+
+* Updated embedded pip release to 1.0.2.
+
+* Fixed #141 - Be smarter about finding pkg_resources when using the
+  non-default Python intepreter (by using the ``-p`` option).
+
+* Fixed #112 - Fixed path in docs.
+
+* Fixed #109 - Corrected doctests of a Logger method.
+
+* Fixed #118 - Fixed creating virtualenvs on platforms that use the
+  "posix_local" install scheme, such as Ubuntu with Python 2.7.
+
+* Add missing library to Python 3 virtualenvs (``_dummy_thread``).
+
+
+1.6.1 (2011-04-30)
+~~~~~~~~~~~~~~~~~~
+
+* Start to use git-flow.
+
+* Added support for PyPy 1.5
+
+* Fixed #121 -- added sanity-checking of the -p argument. Thanks Paul Nasrat.
+
+* Added progress meter for pip installation as well as setuptools. Thanks Ethan
+  Jucovy.
+
+* Added --never-download and --search-dir options. Thanks Ethan Jucovy.
+
+1.6
+~~~
+
+* Added Python 3 support! Huge thanks to Vinay Sajip and Vitaly Babiy.
+
+* Fixed creation of virtualenvs on Mac OS X when standard library modules
+  (readline) are installed outside the standard library.
+
+* Updated bundled pip to 1.0.
+
+1.5.2
+~~~~~
+
+* Moved main repository to Github: https://github.com/pypa/virtualenv
+
+* Transferred primary maintenance from Ian to Jannis Leidel, Carl Meyer and Brian Rosner
+
+* Fixed a few more pypy related bugs.
+
+* Updated bundled pip to 0.8.2.
+
+* Handed project over to new team of maintainers.
+
+* Moved virtualenv to Github at https://github.com/pypa/virtualenv
+
+1.5.1
+~~~~~
+
+* Added ``_weakrefset`` requirement for Python 2.7.1.
+
+* Fixed Windows regression in 1.5
+
+1.5
+~~~
+
+* Include pip 0.8.1.
+
+* Add support for PyPy.
+
+* Uses a proper temporary dir when installing environment requirements.
+
+* Add ``--prompt`` option to be able to override the default prompt prefix.
+
+* Fix an issue with ``--relocatable`` on Windows.
+
+* Fix issue with installing the wrong version of distribute.
+
+* Add fish and csh activate scripts.
+
+1.4.9
+~~~~~
+
+* Include pip 0.7.2
+
+1.4.8
+~~~~~
+
+* Fix for Mac OS X Framework builds that use
+  ``--universal-archs=intel``
+
+* Fix ``activate_this.py`` on Windows.
+
+* Allow ``$PYTHONHOME`` to be set, so long as you use ``source
+  bin/activate`` it will get unset; if you leave it set and do not
+  activate the environment it will still break the environment.
+
+* Include pip 0.7.1
+
+1.4.7
+~~~~~
+
+* Include pip 0.7
+
+1.4.6
+~~~~~
+
+* Allow ``activate.sh`` to skip updating the prompt (by setting
+  ``$VIRTUAL_ENV_DISABLE_PROMPT``).
+
+1.4.5
+~~~~~
+
+* Include pip 0.6.3
+
+* Fix ``activate.bat`` and ``deactivate.bat`` under Windows when
+  ``PATH`` contained a parenthesis
+
+1.4.4
+~~~~~
+
+* Include pip 0.6.2 and Distribute 0.6.10
+
+* Create the ``virtualenv`` script even when Setuptools isn't
+  installed
+
+* 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
+  Distribute by default (so you don't have to remember to use
+  ``--distribute``).
+
+1.4.3
+~~~~~
+
+* Include pip 0.6.1
+
+1.4.2
+~~~~~
+
+* Fix pip installation on Windows
+
+* Fix use of stand-alone ``virtualenv.py`` (and boot scripts)
+
+* Exclude ~/.local (user site-packages) from environments when using
+  ``--no-site-packages``
+
+1.4.1
+~~~~~
+
+* Include pip 0.6
+
+1.4
+~~~
+
+* Updated setuptools to 0.6c11
+
+* Added the --distribute option
+
+* Fixed packaging problem of support-files
+
+1.3.4
+~~~~~
+
+* Virtualenv now copies the actual embedded Python binary on
+  Mac OS X to fix a hang on Snow Leopard (10.6).
+
+* Fail more gracefully on Windows when ``win32api`` is not installed.
+
+* Fix site-packages taking precedent over Jython's ``__classpath__``
+  and also specially handle the new ``__pyclasspath__`` entry in
+  ``sys.path``.
+
+* Now copies Jython's ``registry`` file to the virtualenv if it exists.
+
+* Better find libraries when compiling extensions on Windows.
+
+* Create ``Scripts\pythonw.exe`` on Windows.
+
+* Added support for the Debian/Ubuntu
+  ``/usr/lib/pythonX.Y/dist-packages`` directory.
+
+* Set ``distutils.sysconfig.get_config_vars()['LIBDIR']`` (based on
+  ``sys.real_prefix``) which is reported to help building on Windows.
+
+* Make ``deactivate`` work on ksh
+
+* Fixes for ``--python``: make it work with ``--relocatable`` and the
+  symlink created to the exact Python version.
+
+1.3.3
+~~~~~
+
+* Use Windows newlines in ``activate.bat``, which has been reported to help
+  when using non-ASCII directory names.
+
+* Fixed compatibility with Jython 2.5b1.
+
+* Added a function ``virtualenv.install_python`` for more fine-grained
+  access to what ``virtualenv.create_environment`` does.
+
+* Fix `a problem <https://bugs.launchpad.net/virtualenv/+bug/241581>`_
+  with Windows and paths that contain spaces.
+
+* If ``/path/to/env/.pydistutils.cfg`` exists (or
+  ``/path/to/env/pydistutils.cfg`` on Windows systems) then ignore
+  ``~/.pydistutils.cfg`` and use that other file instead.
+
+* Fix ` a problem
+  <https://bugs.launchpad.net/virtualenv/+bug/340050>`_ picking up
+  some ``.so`` libraries in ``/usr/local``.
+
+1.3.2
+~~~~~
+
+* Remove the ``[install] prefix = ...`` setting from the virtualenv
+  ``distutils.cfg`` -- this has been causing problems for a lot of
+  people, in rather obscure ways.
+
+* If you use a `boot script <./index.html#boot-script>`_ it will attempt to import ``virtualenv``
+  and find a pre-downloaded Setuptools egg using that.
+
+* Added platform-specific paths, like ``/usr/lib/pythonX.Y/plat-linux2``
+
+1.3.1
+~~~~~
+
+* Real Python 2.6 compatibility.  Backported the Python 2.6 updates to
+  ``site.py``, including `user directories
+  <http://docs.python.org/dev/whatsnew/2.6.html#pep-370-per-user-site-packages-directory>`_
+  (this means older versions of Python will support user directories,
+  whether intended or not).
+
+* Always set ``[install] prefix`` in ``distutils.cfg`` -- previously
+  on some platforms where a system-wide ``distutils.cfg`` was present
+  with a ``prefix`` setting, packages would be installed globally
+  (usually in ``/usr/local/lib/pythonX.Y/site-packages``).
+
+* Sometimes Cygwin seems to leave ``.exe`` off ``sys.executable``; a
+  workaround is added.
+
+* Fix ``--python`` option.
+
+* Fixed handling of Jython environments that use a
+  jython-complete.jar.
+
+1.3
+~~~
+
+* Update to Setuptools 0.6c9
+* Added an option ``virtualenv --relocatable EXISTING_ENV``, which
+  will make an existing environment "relocatable" -- the paths will
+  not be absolute in scripts, ``.egg-info`` and ``.pth`` files.  This
+  may assist in building environments that can be moved and copied.
+  You have to run this *after* any new packages installed.
+* Added ``bin/activate_this.py``, a file you can use like
+  ``execfile("path_to/activate_this.py",
+  dict(__file__="path_to/activate_this.py"))`` -- this will activate
+  the environment in place, similar to what `the mod_wsgi example
+  does <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
+* For Mac framework builds of Python, the site-packages directory
+  ``/Library/Python/X.Y/site-packages`` is added to ``sys.path``, from
+  Andrea Rech.
+* Some platform-specific modules in Macs are added to the path now
+  (``plat-darwin/``, ``plat-mac/``, ``plat-mac/lib-scriptpackages``),
+  from Andrea Rech.
+* Fixed a small Bashism in the ``bin/activate`` shell script.
+* Added ``__future__`` to the list of required modules, for Python
+  2.3.  You'll still need to backport your own ``subprocess`` module.
+* Fixed the ``__classpath__`` entry in Jython's ``sys.path`` taking
+  precedent over virtualenv's libs.
+
+1.2
+~~~
+
+* Added a ``--python`` option to select the Python interpreter.
+* Add ``warnings`` to the modules copied over, for Python 2.6 support.
+* Add ``sets`` to the module copied over for Python 2.3 (though Python
+  2.3 still probably doesn't work).
+
+1.1.1
+~~~~~
+
+* Added support for Jython 2.5.
+
+1.1
+~~~
+
+* Added support for Python 2.6.
+* Fix a problem with missing ``DLLs/zlib.pyd`` on Windows.  Create
+* ``bin/python`` (or ``bin/python.exe``) even when you run virtualenv
+  with an interpreter named, e.g., ``python2.4``
+* Fix MacPorts Python
+* Added --unzip-setuptools option
+* Update to Setuptools 0.6c8
+* If the current directory is not writable, run ez_setup.py in ``/tmp``
+* Copy or symlink over the ``include`` directory so that packages will
+  more consistently compile.
+
+1.0
+~~~
+
+* Fix build on systems that use ``/usr/lib64``, distinct from
+  ``/usr/lib`` (specifically CentOS x64).
+* Fixed bug in ``--clear``.
+* Fixed typos in ``deactivate.bat``.
+* Preserve ``$PYTHONPATH`` when calling subprocesses.
+
+0.9.2
+~~~~~
+
+* Fix include dir copying on Windows (makes compiling possible).
+* Include the main ``lib-tk`` in the path.
+* Patch ``distutils.sysconfig``: ``get_python_inc`` and
+  ``get_python_lib`` to point to the global locations.
+* Install ``distutils.cfg`` before Setuptools, so that system
+  customizations of ``distutils.cfg`` won't effect the installation.
+* Add ``bin/pythonX.Y`` to the virtualenv (in addition to
+  ``bin/python``).
+* Fixed an issue with Mac Framework Python builds, and absolute paths
+  (from Ronald Oussoren).
+
+0.9.1
+~~~~~
+
+* Improve ability to create a virtualenv from inside a virtualenv.
+* Fix a little bug in ``bin/activate``.
+* Actually get ``distutils.cfg`` to work reliably.
+
+0.9
+~~~
+
+* Added ``lib-dynload`` and ``config`` to things that need to be
+  copied over in an environment.
+* Copy over or symlink the ``include`` directory, so that you can
+  build packages that need the C headers.
+* Include a ``distutils`` package, so you can locally update
+  ``distutils.cfg`` (in ``lib/pythonX.Y/distutils/distutils.cfg``).
+* Better avoid downloading Setuptools, and hitting PyPI on environment
+  creation.
+* Fix a problem creating a ``lib64/`` directory.
+* Should work on MacOSX Framework builds (the default Python
+  installations on Mac).  Thanks to Ronald Oussoren.
+
+0.8.4
+~~~~~
+
+* Windows installs would sometimes give errors about ``sys.prefix`` that
+  were inaccurate.
+* Slightly prettier output.
+
+0.8.3
+~~~~~
+
+* Added support for Windows.
+
+0.8.2
+~~~~~
+
+* Give a better warning if you are on an unsupported platform (Mac
+  Framework Pythons, and Windows).
+* Give error about running while inside a workingenv.
+* Give better error message about Python 2.3.
+
+0.8.1
+~~~~~
+
+Fixed packaging of the library.
+
+0.8
+~~~
+
+Initial release.  Everything is changed and new!
@@ -0,0 +1,3 @@
+#!/usr/bin/env python
+import virtualenv
+virtualenv.main()
@@ -0,0 +1,5 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+tag_svn_revision = 0
+
@@ -0,0 +1,58 @@
+import sys, os
+try:
+    from setuptools import setup
+    kw = {'entry_points':
+          """[console_scripts]\nvirtualenv = virtualenv:main\n""",
+          'zip_safe': False}
+except ImportError:
+    from distutils.core import setup
+    if sys.platform == 'win32':
+        print('Note: without Setuptools installed you will have to use "python -m virtualenv ENV"')
+        kw = {}
+    else:
+        kw = {'scripts': ['scripts/virtualenv']}
+
+here = os.path.dirname(os.path.abspath(__file__))
+
+## Get long_description from index.txt:
+f = open(os.path.join(here, 'docs', 'index.txt'))
+long_description = f.read().strip()
+long_description = long_description.split('split here', 1)[1]
+f.close()
+f = open(os.path.join(here, 'docs', 'news.txt'))
+long_description += "\n\n" + f.read()
+f.close()
+
+setup(name='virtualenv',
+      # If you change the version here, change it in virtualenv.py and
+      # docs/conf.py as well
+      version="1.7",
+      description="Virtual Python Environment builder",
+      long_description=long_description,
+      classifiers=[
+        'Development Status :: 4 - Beta',
+        'Intended Audience :: Developers',
+        'License :: OSI Approved :: MIT License',
+        'Programming Language :: Python :: 2',
+        'Programming Language :: Python :: 2.4',
+        'Programming Language :: Python :: 2.5',
+        'Programming Language :: Python :: 2.6',
+        'Programming Language :: Python :: 2.7',
+        'Programming Language :: Python :: 3',
+        'Programming Language :: Python :: 3.1',
+        'Programming Language :: Python :: 3.2',
+        ],
+      keywords='setuptools deployment installation distutils',
+      author='Ian Bicking',
+      author_email='ianb@colorstudy.com',
+      maintainer='Jannis Leidel, Carl Meyer and Brian Rosner',
+      maintainer_email='python-virtualenv@groups.google.com',
+      url='http://www.virtualenv.org',
+      license='MIT',
+      py_modules=['virtualenv'],
+      packages=['virtualenv_support'],
+      package_data={'virtualenv_support': ['*-py%s.egg' % sys.version[:3], '*.tar.gz']},
+      test_suite='nose.collector',
+      tests_require=['nose', 'Mock'],
+      **kw
+      )
@@ -0,0 +1,50 @@
+import virtualenv
+from mock import patch, Mock
+
+
+def test_version():
+    """Should have a version string"""
+    assert virtualenv.virtualenv_version == "1.7", "Should have version"
+
+
+@patch('os.path.exists')
+def test_resolve_interpreter_with_absolute_path(mock_exists):
+    """Should return absolute path if given and exists"""
+    mock_exists.return_value = True
+    virtualenv.is_executable = Mock(return_value=True)
+
+    exe = virtualenv.resolve_interpreter("/usr/bin/python42")
+
+    assert exe == "/usr/bin/python42", "Absolute path should return as is"
+    mock_exists.assert_called_with("/usr/bin/python42")
+    virtualenv.is_executable.assert_called_with("/usr/bin/python42")
+
+
+@patch('os.path.exists')
+def test_resolve_intepreter_with_nonexistant_interpreter(mock_exists):
+    """Should exit when with absolute path if not exists"""
+    mock_exists.return_value = False
+
+    try:
+        virtualenv.resolve_interpreter("/usr/bin/python42")
+        assert False, "Should raise exception"
+    except SystemExit:
+        pass
+
+    mock_exists.assert_called_with("/usr/bin/python42")
+
+
+@patch('os.path.exists')
+def test_resolve_intepreter_with_invalid_interpreter(mock_exists):
+    """Should exit when with absolute path if not exists"""
+    mock_exists.return_value = True
+    virtualenv.is_executable = Mock(return_value=False)
+
+    try:
+        virtualenv.resolve_interpreter("/usr/bin/python42")
+        assert False, "Should raise exception"
+    except SystemExit:
+        pass
+
+    mock_exists.assert_called_with("/usr/bin/python42")
+    virtualenv.is_executable.assert_called_with("/usr/bin/python42")
@@ -0,0 +1,906 @@
+Metadata-Version: 1.0
+Name: virtualenv
+Version: 1.7
+Summary: Virtual Python Environment builder
+Home-page: http://www.virtualenv.org
+Author: Jannis Leidel, Carl Meyer and Brian Rosner
+Author-email: python-virtualenv@groups.google.com
+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>`_.
+        
+        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 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
+        ------------
+        
+        ``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).
+        
+        The basic usage is::
+        
+            $ python virtualenv.py ENV
+        
+        If you install it you can also just do ``virtualenv ENV``.
+        
+        This creates ``ENV/lib/pythonX.X/site-packages``, where any libraries you
+        install will go.  It also creates ``ENV/bin/python``, which is a Python
+        interpreter that uses this environment.  Anytime you use that interpreter
+        (including when a script has ``#!/path/to/ENV/bin/python`` in it) the libraries
+        in that environment will be used.
+        
+        It also installs either `Setuptools
+        <http://peak.telecommunity.com/DevCenter/setuptools>`_ or `distribute
+        <http://pypi.python.org/pypi/distribute>`_ into the environment. To use
+        Distribute instead of setuptools, just call virtualenv like this::
+        
+            $ python virtualenv.py --distribute ENV
+        
+        You can also set the environment variable VIRTUALENV_USE_DISTRIBUTE.
+        
+        A new virtualenv also includes the `pip <http://pypy.python.org/pypi/pip>`_
+        installer, so you can use ``ENV/bin/pip`` to install additional packages into
+        the environment.
+        
+        Environment variables and configuration files
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        virtualenv can not only be configured by passing command line options such as
+        ``--distribute`` but also by two other means:
+        
+        - Environment variables
+        
+          Each command line option is automatically used to look for environment
+          variables with the name format ``VIRTUALENV_<UPPER_NAME>``. That means
+          the name of the command line options are capitalized and have dashes
+          (``'-'``) replaced with underscores (``'_'``).
+        
+          For example, to automatically install Distribute instead of setuptools
+          you can also set an environment variable::
+        
+              $ export VIRTUALENV_USE_DISTRIBUTE=true
+              $ python virtualenv.py ENV
+        
+          It's the same as passing the option to virtualenv directly::
+        
+              $ python virtualenv.py --distribute ENV
+        
+          This also works for appending command line options, like ``--find-links``.
+          Just leave an empty space between the passsed values, e.g.::
+        
+              $ export VIRTUALENV_EXTRA_SEARCH_DIR="/path/to/dists /path/to/other/dists"
+              $ virtualenv ENV
+        
+          is the same as calling::
+        
+              $ python virtualenv.py --extra-search-dir=/path/to/dists --extra-search-dir=/path/to/other/dists ENV
+        
+        - Config files
+        
+          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``.
+        
+          The names of the settings are derived from the long command line option,
+          e.g. the option ``--distribute`` would look like this::
+        
+              [virtualenv]
+              distribute = true
+        
+          Appending options like ``--extra-search-dir`` can be written on multiple
+          lines::
+        
+              [virtualenv]
+              extra-search-dir =
+                  /path/to/dists
+                  /path/to/other/dists
+        
+        Please have a look at the output of ``virtualenv --help`` for a full list
+        of supported options.
+        
+        Windows Notes
+        ~~~~~~~~~~~~~
+        
+        Some paths within the virtualenv are slightly different on Windows: scripts and
+        executables on Windows go in ``ENV\Scripts\`` instead of ``ENV/bin/`` and
+        libraries go in ``ENV\Lib\`` rather than ``ENV/lib/``.
+        
+        To create a virtualenv under a path with spaces in it on Windows, you'll need
+        the `win32api <http://sourceforge.net/projects/pywin32/>`_ library installed.
+        
+        PyPy Support
+        ~~~~~~~~~~~~
+        
+        Beginning with virtualenv version 1.5 `PyPy <http://pypy.org>`_ is
+        supported. To use PyPy 1.4 or 1.4.1, you need a version of virtualenv >= 1.5.
+        To use PyPy 1.5, you need a version of virtualenv >= 1.6.1.
+        
+        Creating Your Own Bootstrap Scripts
+        -----------------------------------
+        
+        While this creates an environment, it doesn't put anything into the
+        environment.  Developers may find it useful to distribute a script
+        that sets up a particular environment, for example a script that
+        installs a particular web application.
+        
+        To create a script like this, call
+        ``virtualenv.create_bootstrap_script(extra_text)``, and write the
+        result to your new bootstrapping script.  Here's the documentation
+        from the docstring:
+        
+        Creates a bootstrap script, which is like this script but with
+        extend_parser, adjust_options, and after_install hooks.
+        
+        This returns a string that (written to disk of course) can be used
+        as a bootstrap script with your own customizations.  The script
+        will be the standard virtualenv.py script, with your extra text
+        added (your extra text should be Python code).
+        
+        If you include these functions, they will be called:
+        
+        ``extend_parser(optparse_parser)``:
+            You can add or remove options from the parser here.
+        
+        ``adjust_options(options, args)``:
+            You can change options here, or change the args (if you accept
+            different kinds of arguments, be sure you modify ``args`` so it is
+            only ``[DEST_DIR]``).
+        
+        ``after_install(options, home_dir)``:
+        
+            After everything is installed, this function is called.  This
+            is probably the function you are most likely to use.  An
+            example would be::
+        
+                def after_install(options, home_dir):
+                    if sys.platform == 'win32':
+                        bin = 'Scripts'
+                    else:
+                        bin = 'bin'
+                    subprocess.call([join(home_dir, bin, 'easy_install'),
+                                     'MyPackage'])
+                    subprocess.call([join(home_dir, bin, 'my-package-script'),
+                                     'setup', home_dir])
+        
+            This example immediately installs a package, and runs a setup
+            script from that package.
+        
+        Bootstrap Example
+        ~~~~~~~~~~~~~~~~~
+        
+        Here's a more concrete example of how you could use this::
+        
+            import virtualenv, textwrap
+            output = virtualenv.create_bootstrap_script(textwrap.dedent("""
+            import os, subprocess
+            def after_install(options, home_dir):
+                etc = join(home_dir, 'etc')
+                if not os.path.exists(etc):
+                    os.makedirs(etc)
+                subprocess.call([join(home_dir, 'bin', 'easy_install'),
+                                 'BlogApplication'])
+                subprocess.call([join(home_dir, 'bin', 'paster'),
+                                 'make-config', 'BlogApplication',
+                                 join(etc, 'blog.ini')])
+                subprocess.call([join(home_dir, 'bin', 'paster'),
+                                 'setup-app', join(etc, 'blog.ini')])
+            """))
+            f = open('blog-bootstrap.py', 'w').write(output)
+        
+        Another example is available `here
+        <https://github.com/socialplanning/fassembler/blob/master/fassembler/create-venv-script.py>`_.
+        
+        activate script
+        ~~~~~~~~~~~~~~~
+        
+        In a newly created virtualenv there will be a ``bin/activate`` shell
+        script, or a ``Scripts/activate.bat`` batch file on Windows.
+        
+        On Posix systems you can do::
+        
+          $ 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
+        environment in-place.) This is all it does; it's purely a convenience.  If
+        you directly run a script or the python interpreter from the virtualenv's
+        ``bin/`` directory (e.g.  ``path/to/env/bin/pip`` or
+        ``/path/to/env/bin/python script.py``) there's no need for activation.
+        
+        After activating an environment you can use the function ``deactivate`` to
+        undo the changes to your ``$PATH``.
+        
+        The ``activate`` script will also modify your shell prompt to indicate
+        which environment is currently active.  You can disable this behavior,
+        which can be useful if you have your own custom prompt that already
+        displays the active environment name.  To do so, set the
+        ``VIRTUAL_ENV_DISABLE_PROMPT`` environment variable to any non-empty
+        value before running the ``activate`` script.
+        
+        On Windows you just do::
+        
+          > \path\to\env\Scripts\activate.bat
+        
+        And use ``deactivate.bat`` to undo the changes.
+        
+        The ``--system-site-packages`` Option
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        If you build with ``virtualenv --system-site-packages ENV``, your virtual
+        environment will inherit packages from ``/usr/lib/python2.7/site-packages``
+        (or wherever your global site-packages directory is).
+        
+        This can be used if you have control over the global site-packages directory,
+        and you want to depend on the packages there.  If you want isolation from the
+        global system, do not use this flag.
+        
+        Using Virtualenv without ``bin/python``
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        Sometimes you can't or don't want to use the Python interpreter
+        created by the virtualenv.  For instance, in a `mod_python
+        <http://www.modpython.org/>`_ or `mod_wsgi <http://www.modwsgi.org/>`_
+        environment, there is only one interpreter.
+        
+        Luckily, it's easy.  You must use the custom Python interpreter to
+        *install* libraries.  But to *use* libraries, you just have to be sure
+        the path is correct.  A script is available to correct the path.  You
+        can setup the environment like::
+        
+            activate_this = '/path/to/env/bin/activate_this.py'
+            execfile(activate_this, dict(__file__=activate_this))
+        
+        This will change ``sys.path`` and even change ``sys.prefix``, but also allow
+        you to use an existing interpreter.  Items in your environment will show up
+        first on ``sys.path``, before global items.  However, global items will
+        always be accessible (as if the ``--system-site-packages`` flag had been used
+        in creating the environment, whether it was or not).  Also, this cannot undo
+        the activation of other environments, or modules that have been imported.
+        You shouldn't try to, for instance, activate an environment before a web
+        request; you should activate *one* environment as early as possible, and not
+        do it again in that process.
+        
+        Making Environments Relocatable
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        Note: this option is somewhat experimental, and there are probably
+        caveats that have not yet been identified.  Also this does not
+        currently work on Windows.
+        
+        Normally environments are tied to a specific path.  That means that
+        you cannot move an environment around or copy it to another computer.
+        You can fix up an environment to make it relocatable with the
+        command::
+        
+            $ virtualenv --relocatable ENV
+        
+        This will make some of the files created by setuptools or distribute
+        use relative paths, and will change all the scripts to use ``activate_this.py``
+        instead of using the location of the Python interpreter to select the
+        environment.
+        
+        **Note:** you must run this after you've installed *any* packages into
+        the environment.  If you make an environment relocatable, then
+        install a new package, you must run ``virtualenv --relocatable``
+        again.
+        
+        Also, this **does not make your packages cross-platform**.  You can
+        move the directory around, but it can only be used on other similar
+        computers.  Some known environmental differences that can cause
+        incompatibilities: a different version of Python, when one platform
+        uses UCS2 for its internal unicode representation and another uses
+        UCS4 (a compile-time option), obvious platform changes like Windows
+        vs. Linux, or Intel vs. ARM, and if you have libraries that bind to C
+        libraries on the system, if those C libraries are located somewhere
+        different (either different versions, or a different filesystem
+        layout).
+        
+        If you use this flag to create an environment, currently, the
+        ``--system-site-packages`` option will be implied.
+        
+        The ``--extra-search-dir`` Option
+        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+        
+        When it creates a new environment, virtualenv installs either
+        setuptools or distribute, and pip.  In normal operation, the latest
+        releases of these packages are fetched from the `Python Package Index
+        <http://pypi.python.org>`_ (PyPI). In some circumstances, this
+        behavior may not be wanted, for example if you are using virtualenv
+        during a deployment and do not want to depend on Internet access and
+        PyPI availability.
+        
+        As an alternative, you can provide your own versions of setuptools,
+        distribute and/or pip on the filesystem, and tell virtualenv to use
+        those distributions instead of downloading them from the Internet.  To
+        use this feature, pass one or more ``--extra-search-dir`` options to
+        virtualenv like this::
+        
+            $ virtualenv --extra-search-dir=/path/to/distributions ENV
+        
+        The ``/path/to/distributions`` path should point to a directory that
+        contains setuptools, distribute and/or pip distributions.  Setuptools
+        distributions must be ``.egg`` files; distribute and pip distributions
+        should be `.tar.gz` source distributions.
+        
+        Virtualenv will still download these packages if no satisfactory local
+        distributions are found.
+        
+        If you are really concerned about virtualenv fetching these packages
+        from the Internet and want to ensure that it never will, you can also
+        provide an option ``--never-download`` like so::
+        
+            $ virtualenv --extra-search-dir=/path/to/distributions --never-download ENV
+        
+        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.
+        
+        Compare & Contrast with Alternatives
+        ------------------------------------
+        
+        There are several alternatives that create isolated environments:
+        
+        * ``workingenv`` (which I do not suggest you use anymore) is the
+          predecessor to this library.  It used the main Python interpreter,
+          but relied on setting ``$PYTHONPATH`` to activate the environment.
+          This causes problems when running Python scripts that aren't part of
+          the environment (e.g., a globally installed ``hg`` or ``bzr``).  It
+          also conflicted a lot with Setuptools.
+        
+        * `virtual-python
+          <http://peak.telecommunity.com/DevCenter/EasyInstall#creating-a-virtual-python>`_
+          is also a predecessor to this library.  It uses only symlinks, so it
+          couldn't work on Windows.  It also symlinks over the *entire*
+          standard library and global ``site-packages``.  As a result, it
+          won't see new additions to the global ``site-packages``.
+        
+          This script only symlinks a small portion of the standard library
+          into the environment, and so on Windows it is feasible to simply
+          copy these files over.  Also, it creates a new/empty
+          ``site-packages`` and also adds the global ``site-packages`` to the
+          path, so updates are tracked separately.  This script also installs
+          Setuptools automatically, saving a step and avoiding the need for
+          network access.
+        
+        * `zc.buildout <http://pypi.python.org/pypi/zc.buildout>`_ doesn't
+          create an isolated Python environment in the same style, but
+          achieves similar results through a declarative config file that sets
+          up scripts with very particular packages.  As a declarative system,
+          it is somewhat easier to repeat and manage, but more difficult to
+          experiment with.  ``zc.buildout`` includes the ability to setup
+          non-Python systems (e.g., a database server or an Apache instance).
+        
+        I *strongly* recommend anyone doing application development or
+        deployment use one of these tools.
+        
+        Contributing
+        ------------
+        
+        Refer to the `contributing to pip`_ documentation - it applies equally to
+        virtualenv.
+        
+        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
+        
+        Running the tests
+        ~~~~~~~~~~~~~~~~~
+        
+        Virtualenv's test suite is small and not yet at all comprehensive, but we aim
+        to grow it.
+        
+        The easy way to run tests (handles test dependencies automatically)::
+        
+            $ python setup.py test
+        
+        If you want to run only a selection of the tests, you'll need to run them
+        directly with nose instead. Create a virtualenv, and install required
+        packages::
+        
+            $ pip install nose mock
+        
+        Run nosetests::
+        
+            $ nosetests
+        
+        Or select just a single test file to run::
+        
+            $ nosetests tests.test_virtualenv
+        
+        
+        Other Documentation and Links
+        -----------------------------
+        
+        * James Gardner has written a tutorial on using `virtualenv with
+          Pylons
+          <http://wiki.pylonshq.com/display/pylonscookbook/Using+a+Virtualenv+Sandbox>`_.
+        
+        * `Blog announcement
+          <http://blog.ianbicking.org/2007/10/10/workingenv-is-dead-long-live-virtualenv/>`_.
+        
+        * Doug Hellmann wrote a description of his `command-line work flow
+          using virtualenv (virtualenvwrapper)
+          <http://www.doughellmann.com/articles/CompletelyDifferent-2008-05-virtualenvwrapper/index.html>`_
+          including some handy scripts to make working with multiple
+          environments easier.  He also wrote `an example of using virtualenv
+          to try IPython
+          <http://www.doughellmann.com/articles/CompletelyDifferent-2008-02-ipython-and-virtualenv/index.html>`_.
+        
+        * Chris Perkins created a `showmedo video including virtualenv
+          <http://showmedo.com/videos/video?name=2910000&fromSeriesID=291>`_.
+        
+        * `Using virtualenv with mod_wsgi
+          <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
+        
+        * `virtualenv commands
+          <http://thisismedium.com/tech/extending-virtualenv/>`_ for some more
+          workflow-related tools around virtualenv.
+        
+        Changes & News
+        --------------
+        
+        1.7 (2011-11-30)
+        ~~~~~~~~~~~~~~~~
+        
+        * Updated embedded Distribute release to 0.6.24. Thanks Alex Grönholm.
+        
+        * Made ``--no-site-packages`` behavior the default behavior.  The
+          ``--no-site-packages`` flag is still permitted, but displays a warning when
+          used. Thanks Chris McDonough.
+        
+        * New flag: ``--system-site-packages``; this flag should be passed to get the
+          previous default global-site-package-including behavior back.
+        
+        * Added ability to set command options as environment variables and options
+          in a ``virtualenv.ini`` file.
+        
+        * Fixed various encoding related issues with paths. Thanks Gunnlaugur Thor Briem.
+        
+        * Made ``virtualenv.py`` script executable.
+        
+        1.6.4 (2011-07-21)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Restored ability to run on Python 2.4, too.
+        
+        1.6.3 (2011-07-16)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Restored ability to run on Python < 2.7.
+        
+        1.6.2 (2011-07-16)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Updated embedded distribute release to 0.6.19.
+        
+        * Updated embedded pip release to 1.0.2.
+        
+        * Fixed #141 - Be smarter about finding pkg_resources when using the
+          non-default Python intepreter (by using the ``-p`` option).
+        
+        * Fixed #112 - Fixed path in docs.
+        
+        * Fixed #109 - Corrected doctests of a Logger method.
+        
+        * Fixed #118 - Fixed creating virtualenvs on platforms that use the
+          "posix_local" install scheme, such as Ubuntu with Python 2.7.
+        
+        * Add missing library to Python 3 virtualenvs (``_dummy_thread``).
+        
+        
+        1.6.1 (2011-04-30)
+        ~~~~~~~~~~~~~~~~~~
+        
+        * Start to use git-flow.
+        
+        * Added support for PyPy 1.5
+        
+        * Fixed #121 -- added sanity-checking of the -p argument. Thanks Paul Nasrat.
+        
+        * Added progress meter for pip installation as well as setuptools. Thanks Ethan
+          Jucovy.
+        
+        * Added --never-download and --search-dir options. Thanks Ethan Jucovy.
+        
+        1.6
+        ~~~
+        
+        * Added Python 3 support! Huge thanks to Vinay Sajip and Vitaly Babiy.
+        
+        * Fixed creation of virtualenvs on Mac OS X when standard library modules
+          (readline) are installed outside the standard library.
+        
+        * Updated bundled pip to 1.0.
+        
+        1.5.2
+        ~~~~~
+        
+        * Moved main repository to Github: https://github.com/pypa/virtualenv
+        
+        * Transferred primary maintenance from Ian to Jannis Leidel, Carl Meyer and Brian Rosner
+        
+        * Fixed a few more pypy related bugs.
+        
+        * Updated bundled pip to 0.8.2.
+        
+        * Handed project over to new team of maintainers.
+        
+        * Moved virtualenv to Github at https://github.com/pypa/virtualenv
+        
+        1.5.1
+        ~~~~~
+        
+        * Added ``_weakrefset`` requirement for Python 2.7.1.
+        
+        * Fixed Windows regression in 1.5
+        
+        1.5
+        ~~~
+        
+        * Include pip 0.8.1.
+        
+        * Add support for PyPy.
+        
+        * Uses a proper temporary dir when installing environment requirements.
+        
+        * Add ``--prompt`` option to be able to override the default prompt prefix.
+        
+        * Fix an issue with ``--relocatable`` on Windows.
+        
+        * Fix issue with installing the wrong version of distribute.
+        
+        * Add fish and csh activate scripts.
+        
+        1.4.9
+        ~~~~~
+        
+        * Include pip 0.7.2
+        
+        1.4.8
+        ~~~~~
+        
+        * Fix for Mac OS X Framework builds that use
+          ``--universal-archs=intel``
+        
+        * Fix ``activate_this.py`` on Windows.
+        
+        * Allow ``$PYTHONHOME`` to be set, so long as you use ``source
+          bin/activate`` it will get unset; if you leave it set and do not
+          activate the environment it will still break the environment.
+        
+        * Include pip 0.7.1
+        
+        1.4.7
+        ~~~~~
+        
+        * Include pip 0.7
+        
+        1.4.6
+        ~~~~~
+        
+        * Allow ``activate.sh`` to skip updating the prompt (by setting
+          ``$VIRTUAL_ENV_DISABLE_PROMPT``).
+        
+        1.4.5
+        ~~~~~
+        
+        * Include pip 0.6.3
+        
+        * Fix ``activate.bat`` and ``deactivate.bat`` under Windows when
+          ``PATH`` contained a parenthesis
+        
+        1.4.4
+        ~~~~~
+        
+        * Include pip 0.6.2 and Distribute 0.6.10
+        
+        * Create the ``virtualenv`` script even when Setuptools isn't
+          installed
+        
+        * 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
+          Distribute by default (so you don't have to remember to use
+          ``--distribute``).
+        
+        1.4.3
+        ~~~~~
+        
+        * Include pip 0.6.1
+        
+        1.4.2
+        ~~~~~
+        
+        * Fix pip installation on Windows
+        
+        * Fix use of stand-alone ``virtualenv.py`` (and boot scripts)
+        
+        * Exclude ~/.local (user site-packages) from environments when using
+          ``--no-site-packages``
+        
+        1.4.1
+        ~~~~~
+        
+        * Include pip 0.6
+        
+        1.4
+        ~~~
+        
+        * Updated setuptools to 0.6c11
+        
+        * Added the --distribute option
+        
+        * Fixed packaging problem of support-files
+        
+        1.3.4
+        ~~~~~
+        
+        * Virtualenv now copies the actual embedded Python binary on
+          Mac OS X to fix a hang on Snow Leopard (10.6).
+        
+        * Fail more gracefully on Windows when ``win32api`` is not installed.
+        
+        * Fix site-packages taking precedent over Jython's ``__classpath__``
+          and also specially handle the new ``__pyclasspath__`` entry in
+          ``sys.path``.
+        
+        * Now copies Jython's ``registry`` file to the virtualenv if it exists.
+        
+        * Better find libraries when compiling extensions on Windows.
+        
+        * Create ``Scripts\pythonw.exe`` on Windows.
+        
+        * Added support for the Debian/Ubuntu
+          ``/usr/lib/pythonX.Y/dist-packages`` directory.
+        
+        * Set ``distutils.sysconfig.get_config_vars()['LIBDIR']`` (based on
+          ``sys.real_prefix``) which is reported to help building on Windows.
+        
+        * Make ``deactivate`` work on ksh
+        
+        * Fixes for ``--python``: make it work with ``--relocatable`` and the
+          symlink created to the exact Python version.
+        
+        1.3.3
+        ~~~~~
+        
+        * Use Windows newlines in ``activate.bat``, which has been reported to help
+          when using non-ASCII directory names.
+        
+        * Fixed compatibility with Jython 2.5b1.
+        
+        * Added a function ``virtualenv.install_python`` for more fine-grained
+          access to what ``virtualenv.create_environment`` does.
+        
+        * Fix `a problem <https://bugs.launchpad.net/virtualenv/+bug/241581>`_
+          with Windows and paths that contain spaces.
+        
+        * If ``/path/to/env/.pydistutils.cfg`` exists (or
+          ``/path/to/env/pydistutils.cfg`` on Windows systems) then ignore
+          ``~/.pydistutils.cfg`` and use that other file instead.
+        
+        * Fix ` a problem
+          <https://bugs.launchpad.net/virtualenv/+bug/340050>`_ picking up
+          some ``.so`` libraries in ``/usr/local``.
+        
+        1.3.2
+        ~~~~~
+        
+        * Remove the ``[install] prefix = ...`` setting from the virtualenv
+          ``distutils.cfg`` -- this has been causing problems for a lot of
+          people, in rather obscure ways.
+        
+        * If you use a `boot script <./index.html#boot-script>`_ it will attempt to import ``virtualenv``
+          and find a pre-downloaded Setuptools egg using that.
+        
+        * Added platform-specific paths, like ``/usr/lib/pythonX.Y/plat-linux2``
+        
+        1.3.1
+        ~~~~~
+        
+        * Real Python 2.6 compatibility.  Backported the Python 2.6 updates to
+          ``site.py``, including `user directories
+          <http://docs.python.org/dev/whatsnew/2.6.html#pep-370-per-user-site-packages-directory>`_
+          (this means older versions of Python will support user directories,
+          whether intended or not).
+        
+        * Always set ``[install] prefix`` in ``distutils.cfg`` -- previously
+          on some platforms where a system-wide ``distutils.cfg`` was present
+          with a ``prefix`` setting, packages would be installed globally
+          (usually in ``/usr/local/lib/pythonX.Y/site-packages``).
+        
+        * Sometimes Cygwin seems to leave ``.exe`` off ``sys.executable``; a
+          workaround is added.
+        
+        * Fix ``--python`` option.
+        
+        * Fixed handling of Jython environments that use a
+          jython-complete.jar.
+        
+        1.3
+        ~~~
+        
+        * Update to Setuptools 0.6c9
+        * Added an option ``virtualenv --relocatable EXISTING_ENV``, which
+          will make an existing environment "relocatable" -- the paths will
+          not be absolute in scripts, ``.egg-info`` and ``.pth`` files.  This
+          may assist in building environments that can be moved and copied.
+          You have to run this *after* any new packages installed.
+        * Added ``bin/activate_this.py``, a file you can use like
+          ``execfile("path_to/activate_this.py",
+          dict(__file__="path_to/activate_this.py"))`` -- this will activate
+          the environment in place, similar to what `the mod_wsgi example
+          does <http://code.google.com/p/modwsgi/wiki/VirtualEnvironments>`_.
+        * For Mac framework builds of Python, the site-packages directory
+          ``/Library/Python/X.Y/site-packages`` is added to ``sys.path``, from
+          Andrea Rech.
+        * Some platform-specific modules in Macs are added to the path now
+          (``plat-darwin/``, ``plat-mac/``, ``plat-mac/lib-scriptpackages``),
+          from Andrea Rech.
+        * Fixed a small Bashism in the ``bin/activate`` shell script.
+        * Added ``__future__`` to the list of required modules, for Python
+          2.3.  You'll still need to backport your own ``subprocess`` module.
+        * Fixed the ``__classpath__`` entry in Jython's ``sys.path`` taking
+          precedent over virtualenv's libs.
+        
+        1.2
+        ~~~
+        
+        * Added a ``--python`` option to select the Python interpreter.
+        * Add ``warnings`` to the modules copied over, for Python 2.6 support.
+        * Add ``sets`` to the module copied over for Python 2.3 (though Python
+          2.3 still probably doesn't work).
+        
+        1.1.1
+        ~~~~~
+        
+        * Added support for Jython 2.5.
+        
+        1.1
+        ~~~
+        
+        * Added support for Python 2.6.
+        * Fix a problem with missing ``DLLs/zlib.pyd`` on Windows.  Create
+        * ``bin/python`` (or ``bin/python.exe``) even when you run virtualenv
+          with an interpreter named, e.g., ``python2.4``
+        * Fix MacPorts Python
+        * Added --unzip-setuptools option
+        * Update to Setuptools 0.6c8
+        * If the current directory is not writable, run ez_setup.py in ``/tmp``
+        * Copy or symlink over the ``include`` directory so that packages will
+          more consistently compile.
+        
+        1.0
+        ~~~
+        
+        * Fix build on systems that use ``/usr/lib64``, distinct from
+          ``/usr/lib`` (specifically CentOS x64).
+        * Fixed bug in ``--clear``.
+        * Fixed typos in ``deactivate.bat``.
+        * Preserve ``$PYTHONPATH`` when calling subprocesses.
+        
+        0.9.2
+        ~~~~~
+        
+        * Fix include dir copying on Windows (makes compiling possible).
+        * Include the main ``lib-tk`` in the path.
+        * Patch ``distutils.sysconfig``: ``get_python_inc`` and
+          ``get_python_lib`` to point to the global locations.
+        * Install ``distutils.cfg`` before Setuptools, so that system
+          customizations of ``distutils.cfg`` won't effect the installation.
+        * Add ``bin/pythonX.Y`` to the virtualenv (in addition to
+          ``bin/python``).
+        * Fixed an issue with Mac Framework Python builds, and absolute paths
+          (from Ronald Oussoren).
+        
+        0.9.1
+        ~~~~~
+        
+        * Improve ability to create a virtualenv from inside a virtualenv.
+        * Fix a little bug in ``bin/activate``.
+        * Actually get ``distutils.cfg`` to work reliably.
+        
+        0.9
+        ~~~
+        
+        * Added ``lib-dynload`` and ``config`` to things that need to be
+          copied over in an environment.
+        * Copy over or symlink the ``include`` directory, so that you can
+          build packages that need the C headers.
+        * Include a ``distutils`` package, so you can locally update
+          ``distutils.cfg`` (in ``lib/pythonX.Y/distutils/distutils.cfg``).
+        * Better avoid downloading Setuptools, and hitting PyPI on environment
+          creation.
+        * Fix a problem creating a ``lib64/`` directory.
+        * Should work on MacOSX Framework builds (the default Python
+          installations on Mac).  Thanks to Ronald Oussoren.
+        
+        0.8.4
+        ~~~~~
+        
+        * Windows installs would sometimes give errors about ``sys.prefix`` that
+          were inaccurate.
+        * Slightly prettier output.
+        
+        0.8.3
+        ~~~~~
+        
+        * Added support for Windows.
+        
+        0.8.2
+        ~~~~~
+        
+        * Give a better warning if you are on an unsupported platform (Mac
+          Framework Pythons, and Windows).
+        * Give error about running while inside a workingenv.
+        * Give better error message about Python 2.3.
+        
+        0.8.1
+        ~~~~~
+        
+        Fixed packaging of the library.
+        
+        0.8
+        ~~~
+        
+        Initial release.  Everything is changed and new!
+        
+Keywords: setuptools deployment installation distutils
+Platform: UNKNOWN
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 2
+Classifier: Programming Language :: Python :: 2.4
+Classifier: Programming Language :: Python :: 2.5
+Classifier: Programming Language :: Python :: 2.6
+Classifier: Programming Language :: Python :: 2.7
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.1
+Classifier: Programming Language :: Python :: 3.2
@@ -0,0 +1,38 @@
+AUTHORS.txt
+HACKING
+LICENSE.txt
+MANIFEST.in
+setup.py
+virtualenv.py
+bin/rebuild-script.py
+bin/refresh-support-files.py
+docs/Makefile
+docs/conf.py
+docs/index.txt
+docs/make.bat
+docs/news.txt
+docs/_theme/nature/theme.conf
+docs/_theme/nature/static/nature.css_t
+docs/_theme/nature/static/pygments.css
+scripts/virtualenv
+tests/__init__.py
+tests/test_virtualenv.py
+virtualenv.egg-info/PKG-INFO
+virtualenv.egg-info/SOURCES.txt
+virtualenv.egg-info/dependency_links.txt
+virtualenv.egg-info/entry_points.txt
+virtualenv.egg-info/not-zip-safe
+virtualenv.egg-info/top_level.txt
+virtualenv_support/__init__.py
+virtualenv_support/activate.bat
+virtualenv_support/activate.csh
+virtualenv_support/activate.fish
+virtualenv_support/activate.sh
+virtualenv_support/deactivate.bat
+virtualenv_support/distribute-0.6.24.tar.gz
+virtualenv_support/distutils.cfg
+virtualenv_support/pip-1.0.2.tar.gz
+virtualenv_support/setuptools-0.6c11-py2.4.egg
+virtualenv_support/setuptools-0.6c11-py2.5.egg
+virtualenv_support/setuptools-0.6c11-py2.6.egg
+virtualenv_support/setuptools-0.6c11-py2.7.egg
@@ -0,0 +1 @@
+
@@ -0,0 +1,2 @@
+[console_scripts]
+virtualenv = virtualenv:main
@@ -0,0 +1 @@
+
@@ -0,0 +1,2 @@
+virtualenv_support
+virtualenv
@@ -0,0 +1,31 @@
+@echo off
+set VIRTUAL_ENV=__VIRTUAL_ENV__
+
+if not defined PROMPT (
+    set PROMPT=$P$G
+)
+
+if defined _OLD_VIRTUAL_PROMPT (
+    set PROMPT=%_OLD_VIRTUAL_PROMPT%
+)
+
+if defined _OLD_VIRTUAL_PYTHONHOME (
+     set PYTHONHOME=%_OLD_VIRTUAL_PYTHONHOME%
+)
+
+set _OLD_VIRTUAL_PROMPT=%PROMPT%
+set PROMPT=__VIRTUAL_WINPROMPT__ %PROMPT%
+
+if defined PYTHONHOME (
+     set _OLD_VIRTUAL_PYTHONHOME=%PYTHONHOME%
+     set PYTHONHOME=
+)
+
+if defined _OLD_VIRTUAL_PATH set PATH=%_OLD_VIRTUAL_PATH%; goto SKIPPATH
+
+set _OLD_VIRTUAL_PATH=%PATH%
+
+:SKIPPATH
+set PATH=%VIRTUAL_ENV%\__BIN_NAME__;%PATH%
+
+:END
@@ -0,0 +1,32 @@
+# This file must be used with "source bin/activate.csh" *from csh*.
+# You cannot run it directly.
+# Created by Davide Di Blasi <davidedb@gmail.com>.
+
+alias deactivate 'test $?_OLD_VIRTUAL_PATH != 0 && setenv PATH "$_OLD_VIRTUAL_PATH" && unset _OLD_VIRTUAL_PATH; rehash; test $?_OLD_VIRTUAL_PROMPT != 0 && set prompt="$_OLD_VIRTUAL_PROMPT" && unset _OLD_VIRTUAL_PROMPT; unsetenv VIRTUAL_ENV; test "\!:*" != "nondestructive" && unalias deactivate'
+
+# Unset irrelavent variables.
+deactivate nondestructive
+
+setenv VIRTUAL_ENV "__VIRTUAL_ENV__"
+
+set _OLD_VIRTUAL_PATH="$PATH"
+setenv PATH "$VIRTUAL_ENV/__BIN_NAME__:$PATH"
+
+set _OLD_VIRTUAL_PROMPT="$prompt"
+
+if ("__VIRTUAL_PROMPT__" != "") then
+    set env_name = "__VIRTUAL_PROMPT__"
+else
+    if (`basename "$VIRTUAL_ENV"` == "__") then
+        # special case for Aspen magic directories
+        # see http://www.zetadev.com/software/aspen/
+        set env_name = `basename \`dirname "$VIRTUAL_ENV"\``
+    else
+        set env_name = `basename "$VIRTUAL_ENV"`
+    endif
+endif
+set prompt = "[$env_name] $prompt"
+unset env_name
+
+rehash
+
@@ -0,0 +1,79 @@
+# This file must be used with ". bin/activate.fish" *from fish* (http://fishshell.org)
+# you cannot run it directly
+
+function deactivate  -d "Exit virtualenv and return to normal shell environment"
+    # reset old environment variables
+    if test -n "$_OLD_VIRTUAL_PATH" 
+        set -gx PATH $_OLD_VIRTUAL_PATH
+        set -e _OLD_VIRTUAL_PATH
+    end
+    if test -n "$_OLD_VIRTUAL_PYTHONHOME"
+        set -gx PYTHONHOME $_OLD_VIRTUAL_PYTHONHOME
+        set -e _OLD_VIRTUAL_PYTHONHOME
+    end
+
+    if test -n "$_OLD_FISH_PROMPT_OVERRIDE"
+        functions -e fish_prompt
+        set -e _OLD_FISH_PROMPT_OVERRIDE
+    end
+
+    set -e VIRTUAL_ENV
+    if test "$argv[1]" != "nondestructive"
+        # Self destruct!
+        functions -e deactivate
+    end
+end
+
+# unset irrelavent variables
+deactivate nondestructive
+
+set -gx VIRTUAL_ENV "__VIRTUAL_ENV__"
+
+set -gx _OLD_VIRTUAL_PATH $PATH
+set -gx PATH "$VIRTUAL_ENV/__BIN_NAME__" $PATH
+
+# unset PYTHONHOME if set
+if set -q PYTHONHOME
+    set -gx _OLD_VIRTUAL_PYTHONHOME $PYTHONHOME
+    set -e PYTHONHOME
+end
+
+if test -z "$VIRTUAL_ENV_DISABLE_PROMPT"
+    # fish shell uses a function, instead of env vars,
+    # to produce the prompt. Overriding the existing function is easy.
+    # However, adding to the current prompt, instead of clobbering it,
+    # is a little more work.
+    set -l oldpromptfile (tempfile)
+    if test $status
+        # save the current fish_prompt function...
+        echo "function _old_fish_prompt" >> $oldpromptfile
+        echo -n \# >> $oldpromptfile
+        functions fish_prompt >> $oldpromptfile
+        # we've made the "_old_fish_prompt" file, source it.
+        . $oldpromptfile
+        rm -f $oldpromptfile
+        
+        if test -n "__VIRTUAL_PROMPT__"
+            # We've been given us a prompt override.
+            # 
+            # FIXME: Unsure how to handle this *safely*. We could just eval()
+            #   whatever is given, but the risk is a bit much.
+            echo "activate.fish: Alternative prompt prefix is not supported under fish-shell." 1>&2
+            echo "activate.fish: Alter the fish_prompt in this file as needed." 1>&2
+        end        
+        
+        # with the original prompt function renamed, we can override with our own.
+        function fish_prompt                
+            set -l _checkbase (basename "$VIRTUAL_ENV")
+            if test $_checkbase = "__"
+                # special case for Aspen magic directories
+                # see http://www.zetadev.com/software/aspen/
+                printf "%s[%s]%s %s" (set_color -b blue white) (basename (dirname "$VIRTUAL_ENV")) (set_color normal) (_old_fish_prompt)
+            else
+                printf "%s(%s)%s%s" (set_color -b blue white) (basename "$VIRTUAL_ENV") (set_color normal) (_old_fish_prompt)
+            end
+        end 
+        set -gx _OLD_FISH_PROMPT_OVERRIDE "$VIRTUAL_ENV"
+    end
+end
+
@@ -0,0 +1,76 @@
+# This file must be used with "source bin/activate" *from bash*
+# you cannot run it directly
+
+deactivate () {
+    # reset old environment variables
+    if [ -n "$_OLD_VIRTUAL_PATH" ] ; then
+        PATH="$_OLD_VIRTUAL_PATH"
+        export PATH
+        unset _OLD_VIRTUAL_PATH
+    fi
+    if [ -n "$_OLD_VIRTUAL_PYTHONHOME" ] ; then
+        PYTHONHOME="$_OLD_VIRTUAL_PYTHONHOME"
+        export PYTHONHOME
+        unset _OLD_VIRTUAL_PYTHONHOME
+    fi
+
+    # This should detect bash and zsh, which have a hash command that must
+    # be called to get it to forget past commands.  Without forgetting
+    # past commands the $PATH changes we made may not be respected
+    if [ -n "$BASH" -o -n "$ZSH_VERSION" ] ; then
+        hash -r
+    fi
+
+    if [ -n "$_OLD_VIRTUAL_PS1" ] ; then
+        PS1="$_OLD_VIRTUAL_PS1"
+        export PS1
+        unset _OLD_VIRTUAL_PS1
+    fi
+
+    unset VIRTUAL_ENV
+    if [ ! "$1" = "nondestructive" ] ; then
+    # Self destruct!
+        unset -f deactivate
+    fi
+}
+
+# unset irrelavent variables
+deactivate nondestructive
+
+VIRTUAL_ENV="__VIRTUAL_ENV__"
+export VIRTUAL_ENV
+
+_OLD_VIRTUAL_PATH="$PATH"
+PATH="$VIRTUAL_ENV/__BIN_NAME__:$PATH"
+export PATH
+
+# unset PYTHONHOME if set
+# this will fail if PYTHONHOME is set to the empty string (which is bad anyway)
+# could use `if (set -u; : $PYTHONHOME) ;` in bash
+if [ -n "$PYTHONHOME" ] ; then
+    _OLD_VIRTUAL_PYTHONHOME="$PYTHONHOME"
+    unset PYTHONHOME
+fi
+
+if [ -z "$VIRTUAL_ENV_DISABLE_PROMPT" ] ; then
+    _OLD_VIRTUAL_PS1="$PS1"
+    if [ "x__VIRTUAL_PROMPT__" != x ] ; then
+	PS1="__VIRTUAL_PROMPT__$PS1"
+    else
+    if [ "`basename \"$VIRTUAL_ENV\"`" = "__" ] ; then
+        # special case for Aspen magic directories
+        # see http://www.zetadev.com/software/aspen/
+        PS1="[`basename \`dirname \"$VIRTUAL_ENV\"\``] $PS1"
+    else
+        PS1="(`basename \"$VIRTUAL_ENV\"`)$PS1"
+    fi
+    fi
+    export PS1
+fi
+
+# This should detect bash and zsh, which have a hash command that must
+# be called to get it to forget past commands.  Without forgetting
+# past commands the $PATH changes we made may not be respected
+if [ -n "$BASH" -o -n "$ZSH_VERSION" ] ; then
+    hash -r
+fi
@@ -0,0 +1,17 @@
+@echo off
+
+if defined _OLD_VIRTUAL_PROMPT (
+    set PROMPT=%_OLD_VIRTUAL_PROMPT%
+)
+set _OLD_VIRTUAL_PROMPT=
+
+if defined _OLD_VIRTUAL_PYTHONHOME (
+     set PYTHONHOME=%_OLD_VIRTUAL_PYTHONHOME%
+     set _OLD_VIRTUAL_PYTHONHOME=
+)
+
+if defined _OLD_VIRTUAL_PATH set PATH=%_OLD_VIRTUAL_PATH%
+
+set _OLD_VIRTUAL_PATH=
+
+:END
@@ -0,0 +1,6 @@
+# This is a config file local to this virtualenv installation
+# You may include options that will be used by all distutils commands,
+# and by easy_install.  For instance:
+#
+#   [easy_install]
+#   find_links = http://mylocalsite