Commit 8cfac560 authored by Jan Dittberner's avatar Jan Dittberner

Imported Upstream version 4.7.2

parent 9720a53e
......@@ -14,12 +14,22 @@ Doug Hellmann <doug.hellmann@gmail.com>
Doug Hellmann <doug@doughellmann.com>
Erik B <erik.bernoth@gmail.com>
Greg Haskins <greg@greghaskins.com>
Harry <hjwp2@cantab.net>
Ismail Badawi <isbadawi@gmail.com>
Ismail Sunni <imajimatika@gmail.com>
James Bennett <james@b-list.org>
Jason Myers <jason@jasonamyers.com>
Jason Myers <jason@mailthemyers.com>
Jason Veatch <jtveatch@yahoo.com>
Jeff Byrnes <jeff@evertrue.com>
Jessamyn Smith <geekchick77@gmail.com>
John Brewer <brewerja@gmail.com>
Justin Abrahms <justin@abrah.ms>
Justin Barber <barber.justin@gmail.com>
Kevin Deldycke <kevin@deldycke.com>
Manuel Kaufmann <humitos@gmail.com>
Martin Etnestad Johansen <gnawybol@gmail.com>
Michael A. Smith <michaels@syapse.com>
Michael Brooks <mjbrooks@uw.edu>
Michael Elsdoerfer <michael@elsdoerfer.com>
Michael Elsdörfer <michael@elsdoerfer.com>
......@@ -27,10 +37,14 @@ Mike Fogel <mike@fogel.ca>
Monty Taylor <mordred@inaugust.com>
Nat Williams <nwilliams@leapfrogonline.com>
Nishikar Sapkota <Nishikar.Sapkota@Cerner.com>
Oleg Broytman <phd@phdru.name>
OmeGak <omegak@gmail.com>
Paul McLanahan <paul@mclanahan.net>
Peter Bittner <django@bittner.it>
Radu Voicilas <radu.voicilas@gmail.com>
Ralph Bean <rbean@redhat.com>
Raphael Das Gupta <bitbucket.org@raphael.dasgupta.ch>
Robson Peixoto <robsonpeixoto@gmail.com>
Sander Smits <jhmsmits@gmail.com>
Scott Stevenson <scott@scottstvnsn.com>
Shrikant-Sharat <shrikantsharat.k@gmail.com>
......@@ -51,3 +65,4 @@ seth@seth-ec-laptop <seth@seth-ec-laptop>
t2y <none@none>
t2y <tetsuya.morimoto@gmail.com>
wam@talyn.cisco.com <wam@talyn.cisco.com>
Éric Lemoine <eric.lemoine@gmail.com>
CHANGES
=======
4.7.2
-----
* Baseline testing to python27
* Fixing naming in tests
* Merged in phd/virtualenvwrapper (pull request #46)
* Ignore *.pyo byte-code files
* Fix docs: fix URLs whenever possible, change protocol to https
* Add wipeenv and allvirtualenv for lazy loading
* Remove one-time functions from the environment
* Fix the problem with lazy completion for bash
* Last set of docs
* Docs fixes
* Merged in fix/issue-282-link-to-virtualenvwrapper (pull request #49)
* Updating to virtualenvwrapper
* Merged in ismailsunni/virtualenvwrapper/ismailsunni/command_refrst-edited-online-with-bitbuc-1454377958615 (pull request #44)
* command_ref.rst edited online with Bitbucket Adding -d for remove extra path
* use a ref instead of hard-coded link in new tip
* Merged in kojiromike/virtualenvwrapper/deactivate-on-logout-tip (pull request #43)
* Add Deactivate-on-Logout Tip
* update REAMDE with new bug tracker URL
* more dir fixes for El Capitan
* add testing for python 3.5
* temporary dir fixes for OS X El Capitan (10.11)
* update to work with tox 2.1.1
* Merged in jveatch/virtualenvwrapper/fix-py26-logging (pull request #41)
* Pass stream as arg rather than kwarg to avoid py26 conflict. Fixes issue #274. StreamHandler arg was named strm in python 2.6
* enhance verbose output of hook loader
* Merged in erilem/virtualenvwrapper/user-scheme-installation (pull request #38)
* Change install docs to use --user
4.7.0
-----
* Merged in gnawybol/virtualenvwrapper/support_MINGW64 (pull request #36)
* Detect MSYS if MSYSTEM is MINGW64
* Merged in kdeldycke/virtualenvwrapper/kdeldycke/restore-overridden-cd-command-to-its-def-1435073839852 (pull request #34)
* Restore overridden cd command to its default builtin behaviour
4.6.0
-----
* remove some explicit tox environments
* Merged in jessamynsmith/virtualenvwrapper/py34 (pull request #30)
* quiet some of the lsvirtualenv tests
* add test for previous patch
* Merged in robsonpeixoto/virtualenvwrapper/bug/265 (pull request #33)
* Removes empty when list all virtualenvs
* Merged in justinabrahms/virtualenvwrapper/justinabrahms/update-links-and-name-for-venv-post-1431982402822 (pull request #32)
* Update links and name for venv post
* Added testing and updated docs for python 3.4
* Merged in jessamynsmith/virtualenvwrapper/env_with_space (pull request #28)
* Changes as per code review
* Added tests to verify that cpvirtualenv, lsvirtualenv, and mkproject work with spaces in env names
* Made rmvirtualenv work with spaces
* Added tests for leading spaces (trailing spaces don't work in Linux, so don't test them)
* Made lsvirtualenv and allvirtualenv work with spaces in env names
* Made cd command work with space in virtualenv name
* Fixed ordering in asserts for workon tests
* Made workon fully support virtualenvs with spaces in names
* fix default for VIRTUALENVWRAPPER_WORKON_CD
4.5.0
-----
* Add -c/-n options to mktmpenv
* update mktmpenv test to assert changed directory
* Add test for creating venv with space in name
4.4.1
-----
* Touch temporary file after a name is created
* document 'workon .' and give attribution
* Support "workon ."
* fix pep8 error
* make cd after workon optional
* fix sphinx build
* Merged in hjwp/virtualenvwrapper (pull request #25)
* Stop mangling the python argument to virtualenv
* ignore -f lines in pip freeze output
* Merged in bittner/virtualenvwrapper (pull request #22)
* hacked attempt to get round MSYS_HOME environ dependency on windows/git-bash/msys
* Change "distribute" to "setuptools" in docs
* Merged in jessamynsmith/virtualenvwrapper (pull request #23)
* Override tox's desire to install pre-releases
* Reworded the documentation around user scripts vs plugin creation, to make it more clear which one you need. Also added a simple example of user scripts
* do not install distribute in test environments
* Correct spelling of "Bitbucket"
* Update issue tracker URL
4.3.2
-----
* build universal wheels
* Merged in das_g/virtualenvwrapper/das_g/removed-gratuitous-preposition-1413208408920 (pull request #19)
* removed gratuitous preposition
* Fix test invocation for zsh
* add -q option to cd for zsh
* make run_tests use the SHELL var to run test script
4.3.1
-----
......@@ -540,7 +641,7 @@ CHANGES
* closes #70 by adding a list of supported shells and python versions to documentation and trove classifiers
* fix #60 by setting install_requires instead of requires
* change the way we determine the python version
* convert test scripts to use tox instead of home-grown multi-version system in the Makefile
* convert test scripts to use tox instead of home-grown multi-version system in the Makefile
* create the WORKON_HOME dir if it doesn't exist
* fix platforms definition so upload to pypi will work
* Added tag 2.5.3 for changeset dc74f106d8d2
......@@ -896,7 +997,7 @@ CHANGES
* fix for ticket #14: relative paths don't work with add2virtualenv
* incorporate patch from Sascha Brossmann to fix #15
* Applying my own ridiculous formatting to the README file. Give me 72 characters or give me death!
* Applying my own ridiculous formatting to the README file. Give me 72 characters or give me death!
* Added tag 1.18 for changeset 24190e878fa8
1.18
......@@ -984,8 +1085,8 @@ CHANGES
* merge ChrisHas35's postactivatehook changes
* start 1.11 with optimization suggestion from ChrisHas35
* Added tag 1.10 for changeset 274d4576d606
* add global postactivate hook. related to #3
* remove unnecssary egrep calls on show_workon_options. fixes #4
* add global postactivate hook. related to #3
* remove unnecssary egrep calls on show_workon_options. fixes #4
1.10
----
......@@ -1011,7 +1112,7 @@ CHANGES
1.8
---
* Fix for processing the argument list in mkvirtualenv from jorgevargas (#1
* Fix for processing the argument list in mkvirtualenv from jorgevargas (#1)
* Added tag 1.7 for changeset 32f2a081d649
1.7
......
......@@ -6,7 +6,7 @@ help:
@echo "upload - upload a new release to PyPI"
@echo "develop - install development version"
@echo "test - run the test suite"
@echo "test-quick - run the test suite for bash and one version of Python ($(PYTHON26))"
@echo "test-quick - run the test suite for bash and one version of Python ($(PYTHON27))"
.PHONY: sdist
sdist: html
......
Metadata-Version: 1.1
Name: virtualenvwrapper
Version: 4.3.1
Version: 4.7.2
Summary: Enhancements to virtualenv
Home-page: http://virtualenvwrapper.readthedocs.org/
Author: Doug Hellmann
......@@ -71,7 +71,7 @@ Description: .. -*- mode: rst -*-
Python Versions
===============
virtualenvwrapper is tested under Python 2.6 - 3.3.
virtualenvwrapper is tested under Python 2.6 - 3.4.
=======
Support
......@@ -81,8 +81,8 @@ Description: .. -*- mode: rst -*-
<http://groups.google.com/group/virtualenvwrapper/>`__ to discuss
issues and features.
Report bugs via the `bug tracker on BitBucket
<http://bitbucket.org/dhellmann/virtualenvwrapper/>`__.
Report bugs via the `bug tracker on Bitbucket
<https://bitbucket.org/virtualenvwrapper/virtualenvwrapper/issues>`__.
Shell Aliases
=============
......@@ -135,6 +135,8 @@ Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.3
Classifier: Programming Language :: Python :: 3.4
Classifier: Programming Language :: Python :: 3.5
Classifier: Intended Audience :: Developers
Classifier: Environment :: Console
Provides: virtualenvwrapper
......
......@@ -63,7 +63,7 @@ from this page.
Python Versions
===============
virtualenvwrapper is tested under Python 2.6 - 3.3.
virtualenvwrapper is tested under Python 2.6 - 3.4.
=======
Support
......@@ -73,8 +73,8 @@ Join the `virtualenvwrapper Google Group
<http://groups.google.com/group/virtualenvwrapper/>`__ to discuss
issues and features.
Report bugs via the `bug tracker on BitBucket
<http://bitbucket.org/dhellmann/virtualenvwrapper/>`__.
Report bugs via the `bug tracker on Bitbucket
<https://bitbucket.org/virtualenvwrapper/virtualenvwrapper/issues>`__.
Shell Aliases
=============
......
sphinxcontrib-bitbucket
sphinx>=1.1.2,!=1.2.0,!=1.3b1,<1.3
......@@ -33,7 +33,7 @@ activated after being initialized.
$ workon
$ mkvirtualenv mynewenv
New python executable in mynewenv/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......@@ -57,7 +57,7 @@ installed.
* :ref:`scripts-postmkvirtualenv`
* `requirements file format`_
.. _requirements file format: http://www.pip-installer.org/en/latest/requirements.html
.. _requirements file format: https://pip.pypa.io/en/latest/reference/pip_install/#requirements-file-format
.. _command-mktmpenv:
......@@ -68,10 +68,18 @@ Create a new virtualenv in the ``WORKON_HOME`` directory.
Syntax::
mktmpenv [VIRTUALENV_OPTIONS]
mktmpenv [(-c|--cd)|(-n|--no-cd)] [VIRTUALENV_OPTIONS]
A unique virtualenv name is generated.
If ``-c`` or ``--cd`` is specified the working directory is changed to
the virtualenv directory during the post-activate phase, regardless of
the value of ``VIRTUALENVWRAPPER_WORKON_CD``.
If ``-n`` or ``--no-cd`` is specified the working directory is **not**
changed to the virtualenv directory during the post-activate phase,
regardless of the value of ``VIRTUALENVWRAPPER_WORKON_CD``.
::
$ mktmpenv
......@@ -79,7 +87,7 @@ A unique virtualenv name is generated.
New python executable in 1e513ac6-616e-4d56-9aa5-9d0a3b305e20/bin/python
Overwriting 1e513ac6-616e-4d56-9aa5-9d0a3b305e20/lib/python2.7/distutils/__init__.py
with new content
Installing distribute...............................................
Installing setuptools...............................................
....................................................................
.................................................................done.
This is a temporary environment. It will be deleted when deactivated.
......@@ -180,7 +188,7 @@ Syntax::
$ workon
$ mkvirtualenv source
New python executable in source/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......@@ -238,23 +246,35 @@ List or change working virtual environments
Syntax::
workon [environment_name]
workon [(-c|--cd)|(-n|--no-cd)] [environment_name|"."]
If no ``environment_name`` is given the list of available environments
is printed to stdout.
If ``-c`` or ``--cd`` is specified the working directory is changed to
the project directory during the post-activate phase, regardless of
the value of ``VIRTUALENVWRAPPER_WORKON_CD``.
If ``-n`` or ``--no-cd`` is specified the working directory is **not**
changed to the project directory during the post-activate phase,
regardless of the value of ``VIRTUALENVWRAPPER_WORKON_CD``.
If ``"."`` is passed as the environment name, the name is derived from
the base name of the current working directory (contributed by Matias
Saguir).
::
$ workon
$ mkvirtualenv env1
New python executable in env1/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
(env1)$ mkvirtualenv env2
New python executable in env2/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......@@ -276,6 +296,7 @@ is printed to stdout.
* :ref:`scripts-postdeactivate`
* :ref:`scripts-preactivate`
* :ref:`scripts-postactivate`
* :ref:`variable-VIRTUALENVWRAPPER_WORKON_CD`
.. _command-deactivate:
......@@ -301,7 +322,7 @@ Syntax::
$ mkvirtualenv env1
New python executable in env1/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......@@ -342,7 +363,7 @@ subdirectory.
$ mkvirtualenv env1
New python executable in env1/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......@@ -376,7 +397,7 @@ directory to change into.
$ mkvirtualenv env1
New python executable in env1/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......@@ -400,13 +421,13 @@ Syntax::
$ mkvirtualenv env1
New python executable in env1/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
(env1)$ $ workon env1
(env1)$ lssitepackages
distribute-0.6.10-py2.6.egg pip-0.6.3-py2.6.egg
setuptools-0.6.10-py2.6.egg pip-0.6.3-py2.6.egg
easy-install.pth setuptools.pth
===============
......@@ -436,6 +457,7 @@ in a ``.pth`` file inside ``site-packages`` using ``add2virtualenv``.
2. Run: ``add2virtualenv path_to_source``.
3. Run: ``add2virtualenv``.
4. A usage message and list of current "extra" paths is printed.
5. Use option ``-d`` to remove the added path.
The directory names are added to a path file named
``_virtualenv_path_extensions.pth`` inside the site-packages directory
......@@ -462,7 +484,7 @@ output.
$ mkvirtualenv env1
New python executable in env1/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......@@ -505,7 +527,7 @@ create a virtual environment with the same name as the project.
$ mkproject myproj
New python executable in myproj/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......@@ -540,14 +562,14 @@ virtualenv and project directory. An association is made so that when
$ mkproject myproj
New python executable in myproj/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
Creating /Users/dhellmann/Devel/myproj
(myproj)$ mkvirtualenv myproj_new_libs
New python executable in myproj/bin/python
Installing distribute.............................................
Installing setuptools.............................................
..................................................................
..................................................................
done.
......
......@@ -27,7 +27,8 @@ import subprocess
# ones.
extensions = ['sphinxcontrib.bitbucket']
bitbucket_project_url = 'http://bitbucket.org/dhellmann/virtualenvwrapper/'
bitbucket_project_url = 'https://bitbucket.org/virtualenvwrapper/virtualenvw' \
'rapper/'
# Add any paths that contain templates here, relative to this directory.
# templates_path = ['pkg/templates']
......
......@@ -147,7 +147,7 @@ far I have dealt with the ports by encouraging other developers to
handle them, and then trying to link to and otherwise promote the
results.
.. _fish: http://ridiculousfish.com/shell/
.. _fish: https://fishshell.com/
Not As Bad As It Seems
======================
......@@ -169,10 +169,10 @@ what virtualenvwrapper is doing, it's a natural fit.
* `Environment variable`_ on Wikipedia
* `Linux implementation of fork()`_
.. _Advanced Programming in the UNIX Environment: http://www.amazon.com/gp/product/0321637739/ref=as_li_ss_tl?ie=UTF8&camp=1789&creative=390957&creativeASIN=0321637739&linkCode=as2&tag=hellflynet-20
.. _Advanced Programming in the UNIX Environment: https://www.amazon.com/gp/product/0321637739/ref=as_li_ss_tl?ie=UTF8&camp=1789&creative=390957&creativeASIN=0321637739&linkCode=as2&tag=hellflynet-20
.. _Fork (operating system): http://en.wikipedia.org/wiki/Fork_(operating_system)
.. _Fork (operating system): https://en.wikipedia.org/wiki/Fork_(operating_system)
.. _Environment variable: http://en.wikipedia.org/wiki/Environment_variable
.. _Environment variable: https://en.wikipedia.org/wiki/Environment_variable
.. _Linux implementation of fork(): https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/kernel/fork.c?id=refs/tags/v3.9-rc8#n1558
......@@ -5,7 +5,7 @@ For Developers
If you would like to contribute to virtualenvwrapper directly, these
instructions should help you get started. Patches, bug reports, and
feature requests are all welcome through the `BitBucket site
<http://bitbucket.org/dhellmann/virtualenvwrapper/>`_. Contributions
<https://bitbucket.org/virtualenvwrapper/virtualenvwrapper/>`_. Contributions
in the form of patches or pull requests are easier to integrate and
will receive priority attention.
......@@ -40,7 +40,7 @@ documentation::
updating environment: 0 added, 2 changed, 0 removed
reading sources... [ 50%] command_ref
reading sources... [100%] developers
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
......@@ -48,17 +48,17 @@ documentation::
writing output... [ 33%] command_ref
writing output... [ 66%] developers
writing output... [100%] index
writing additional files... search
copying static files... WARNING: static directory '/Users/dhellmann/Devel/virtualenvwrapper/plugins/docs/sphinx/pkg/static' does not exist
done
dumping search index... done
dumping object inventory... done
build succeeded, 1 warning.
Build finished. The HTML pages are in build/html.
cp -r docs/build/html virtualenvwrapper/docs
The output version of the documentation ends up in
``./virtualenvwrapper/docs`` inside your sandbox.
......@@ -89,9 +89,9 @@ Python::
Add new tests by modifying an existing file or creating new script in
the ``tests`` directory.
.. _shunit2: http://shunit2.googlecode.com/
.. _shunit2: https://github.com/kward/shunit2
.. _tox: http://codespeak.net/tox
.. _tox: https://tox.testrun.org/
.. _developer-templates:
......@@ -100,7 +100,7 @@ Creating a New Template
virtualenvwrapper.project templates work like `virtualenvwrapper
plugins
<http://www.doughellmann.com/docs/virtualenvwrapper/plugins.html>`__.
<https://virtualenvwrapper.readthedocs.io/en/latest/plugins.html>`__.
The *entry point* group name is
``virtualenvwrapper.project.template``. Configure your entry point to
refer to a function that will **run** (source hooks are not supported
......
......@@ -14,9 +14,9 @@ used as a project file similar to other IDEs. The emacs-desktop_
plugin adds a trigger to save the current desktop file and load a new
one when activating a new virtualenv using ``workon``.
.. _desktop-mode: http://www.emacswiki.org/emacs/DeskTop
.. _desktop-mode: https://www.emacswiki.org/emacs/DeskTop
.. _emacs-desktop: http://www.doughellmann.com/projects/virtualenvwrapper-emacs-desktop/
.. _emacs-desktop: https://pypi.python.org/pypi/virtualenvwrapper-emacs-desktop
.. _extensions-user_scripts:
......@@ -53,7 +53,7 @@ bitbucket
The bitbucket_ extension automatically clones a mercurial repository
from the specified bitbucket project.
.. _bitbucket: http://www.doughellmann.com/projects/virtualenvwrapper.bitbucket/
.. _bitbucket: https://pypi.python.org/pypi/virtualenvwrapper.bitbucket
.. _templates-django:
......@@ -62,7 +62,7 @@ django
The django_ extension automatically creates a new Django project.
.. _django: http://www.doughellmann.com/projects/virtualenvwrapper.django/
.. _django: https://pypi.python.org/pypi/virtualenvwrapper.django
SublimeText
-----------
......
......@@ -5,7 +5,10 @@
virtualenvwrapper adds several hook points you can use to change your
settings, shell environment, or other configuration values when
creating, deleting, or moving between environments. These hooks are
exposed in two ways:
exposed in two ways. :ref:`scripts` allows a user to perform generic actions
for every virtualenv in your environment, including customization of
virtualenv creation. :ref:`plugins` makes it possible to share common
behaviors between systems and developers.
.. toctree::
:maxdepth: 1
......
......@@ -8,7 +8,7 @@ virtualenvwrapper |release|
###########################
virtualenvwrapper is a set of extensions to Ian Bicking's `virtualenv
<http://pypi.python.org/pypi/virtualenv>`_ tool. The extensions
<https://pypi.python.org/pypi/virtualenv>`_ tool. The extensions
include wrappers for creating and deleting virtual environments and
otherwise managing your development workflow, making it easier to work
on more than one project at a time without introducing conflicts in
......@@ -50,7 +50,7 @@ installed by pip.
$ source /usr/local/bin/virtualenvwrapper.sh
$ mkvirtualenv env1
Installing
distribute..........................................
setuptools..........................................
....................................................
....................................................
...............................done.
......@@ -79,7 +79,7 @@ We can see the new package with ``lssitepackages``::
(env1)$ lssitepackages
Django-1.1.1-py2.6.egg-info easy-install.pth
distribute-0.6.10-py2.6.egg pip-0.6.3-py2.6.egg
setuptools-0.6.10-py2.6.egg pip-0.6.3-py2.6.egg
django setuptools.pth
Of course we are not limited to a single virtualenv::
......@@ -87,7 +87,7 @@ Of course we are not limited to a single virtualenv::
(env1)$ ls $WORKON_HOME
env1 hook.log
(env1)$ mkvirtualenv env2
Installing distribute...............................
Installing setuptools...............................
....................................................
....................................................
........... ...............................done.
......@@ -103,7 +103,7 @@ Switch between environments with ``workon``::
(env2)$ workon env1
(env1)$ echo $VIRTUAL_ENV
/Users/dhellmann/Envs/env1
(env1)$
(env1)$
The ``workon`` command also includes tab completion for the
environment names, and invokes customization scripts as an environment
......@@ -124,7 +124,7 @@ created, letting you automatically install commonly-used tools.
(env2)$ echo 'pip install sphinx' >> $WORKON_HOME/postmkvirtualenv
(env3)$ mkvirtualenv env3
New python executable in env3/bin/python
Installing distribute...............................
Installing setuptools...............................
....................................................
....................................................
........... ...............................done.
......@@ -155,7 +155,7 @@ created, letting you automatically install commonly-used tools.
Installing sphinx-build script to /Users/dhellmann/Envs/env3/bin
Installing sphinx-quickstart script to /Users/dhellmann/Envs/env3/bin
Installing sphinx-autogen script to /Users/dhellmann/Envs/env3/bin
Successfully installed docutils Jinja2 Pygments sphinx (env3)$
Successfully installed docutils Jinja2 Pygments sphinx (env3)$
(venv3)$ which sphinx-build
/Users/dhellmann/Envs/env3/bin/sphinx-build
......@@ -189,34 +189,34 @@ Details
References
==========
`virtualenv <http://pypi.python.org/pypi/virtualenv>`_, from Ian
`virtualenv <https://pypi.python.org/pypi/virtualenv>`_, from Ian
Bicking, is a pre-requisite to using these extensions.
For more details, refer to the column I wrote for the May 2008 issue
of Python Magazine: `virtualenvwrapper | And Now For Something
Completely Different
<http://www.doughellmann.com/articles/CompletelyDifferent-2008-05-virtualenvwrapper/index.html>`_.
<https://doughellmann.com/blog/2008/05/01/virtualenvwrapper/>`_.
Rich Leland has created a short `screencast
<http://mathematism.com/2009/jul/30/presentation-pip-and-virtualenv/>`__
<http://mathematism.com/2009/07/30/presentation-pip-and-virtualenv/>`__
showing off the features of virtualenvwrapper.
Manuel Kaufmann has `translated this documentation into Spanish
<http://virtualenvwrapper-docs-es.readthedocs.org/en/latest/>`__.
<https://virtualenvwrapper-docs-es.readthedocs.org/es/latest/>`__.
Tetsuya Morimoto has `translated this documentation into Japanese
<http://virtualenvwrapper-docs-ja.readthedocs.org/en/latest/>`__.
<https://virtualenvwrapper-docs-ja.readthedocs.org/en/latest/>`__.
=======
Support
=======
Join the `virtualenvwrapper Google Group
<http://groups.google.com/group/virtualenvwrapper/>`__ to discuss
issues and features.
<https://groups.google.com/group/virtualenvwrapper/>`__ to discuss
issues and features.
Report bugs via the `bug tracker on BitBucket
<http://bitbucket.org/dhellmann/virtualenvwrapper/>`__.
<https://bitbucket.org/virtualenvwrapper/virtualenvwrapper/>`__.
Shell Aliases
=============
......
......@@ -22,7 +22,7 @@ request through the `bitbucket project page`_. If you write a clone to
work with an incompatible shell, let me know and I will link to it
from this page.
.. _bitbucket project page: https://bitbucket.org/dhellmann/virtualenvwrapper/
.. _bitbucket project page: https://bitbucket.org/virtualenvwrapper/virtualenvwrapper/
Windows Command Prompt
----------------------
......@@ -32,7 +32,7 @@ which can be run under Microsoft Windows Command Prompt. This is also
a separately distributed re-implementation. You can download
`virtualenvwrapper-win`_ from PyPI.
.. _virtualenvwrapper-win: http://pypi.python.org/pypi/virtualenvwrapper-win
.. _virtualenvwrapper-win: https://pypi.python.org/pypi/virtualenvwrapper-win
MSYS
----
......@@ -58,7 +58,7 @@ or::
Depending on your MSYS setup, you may need to install the `MSYS mktemp
binary`_ in the ``MSYS_HOME/bin`` folder.
.. _MSYS mktemp binary: http://sourceforge.net/projects/mingw/files/MSYS/mktemp/
.. _MSYS mktemp binary: https://sourceforge.net/projects/mingw/files/MSYS/
PowerShell
----------
......@@ -69,14 +69,14 @@ with the rest of the extensions, and is largely a re-implementation
(rather than an adaptation), it should be distributed separately. You
can download virtualenvwrapper-powershell_ from PyPI.
.. _virtualenvwrapper-powershell: http://pypi.python.org/pypi/virtualenvwrapper-powershell/2.7.1
.. _virtualenvwrapper-powershell: https://pypi.python.org/pypi/virtualenvwrapper-powershell
.. _supported-versions:
Python Versions
===============
virtualenvwrapper is tested under Python 2.6-3.3.
virtualenvwrapper is tested under Python 2.6-3.4.
.. _install-basic:
......@@ -104,12 +104,12 @@ or::
An alternative to installing it into the global site-packages is to
add it to `your user local directory
<http://docs.python.org/install/index.html#alternate-installation-the-home-scheme>`__
<https://docs.python.org/install/index.html#alternate-installation-the-user-scheme>`__
(usually `~/.local`).
::
$ pip install --install-option="--user" virtualenvwrapper
$ pip install --user virtualenvwrapper
.. _install-shell-config:
......@@ -207,6 +207,20 @@ project working directory. The default is ``.project``.
* :ref:`project-management`
.. _variable-VIRTUALENVWRAPPER_WORKON_CD:
Enable Project Directory Switching
----------------------------------
The variable ``VIRTUALENVWRAPPER_WORKON_CD`` controls whether the
working directory is changed during the post activate phase. The
default is ``1``, to enable changing directories. Set the value to
``0`` to disable this behavior for all invocations of ``workon``.
.. seealso::
* :ref:`command-workon`
.. _variable-VIRTUALENVWRAPPER_HOOK_DIR:
Location of Hook Scripts
......@@ -317,4 +331,4 @@ supported. In your startup file, change ``source
/usr/local/bin/virtualenvwrapper_bashrc`` to ``source
/usr/local/bin/virtualenvwrapper.sh``.
.. _pip: http://pypi.python.org/pypi/pip
.. _pip: https://pypi.python.org/pypi/pip
......@@ -12,6 +12,13 @@ virtualenvwrapper continues the tradition of encouraging a craftsman
to modify their tools to work the way they want, rather than the other
way around.
There are two ways to attach your code so that virtualenvwrapper will
run it: End-users can use shell scripts or other programs for personal
customization, e.g. automatically performing an action on every new
virtualenv (see :ref:`scripts`). Extensions can also be
implemented in Python by using `Setuptools entry points`_, making it
possible to share common behaviors between systems and developers.
Use the hooks provided to eliminate repetitive manual operations and
streamline your development workflow. For example, set up the
:ref:`plugins-pre_activate` and :ref:`plugins-post_activate` hooks to
......@@ -25,12 +32,6 @@ install basic requirements into each new development environment,
initialize a source code control repository, or otherwise set up a new
project.
There are two ways to attach your code so that virtualenvwrapper will
run it: End-users can use shell scripts or other programs for personal
customization (see :ref:`scripts`). Extensions can also be
implemented in Python by using Distribute_ *entry points*, making it
possible to share common behaviors between systems and developers.