Skip to content
Browse files

Removed from this distribution and updated document…

…ation to point to the actively maintained virtualenv instead.

branch : distribute
extra : rebase_source : accfddb40177f981dbf0e5886039fcb27c1be573
  • Loading branch information
hannosch committed Oct 23, 2009
1 parent a858356 commit 43d34734c801d2d9a72d5fa6e7fc74d80bdc11c1
Showing with 6 additions and 151 deletions.
  1. +2 −0 CHANGES.txt
  2. +4 −28 docs/easy_install.txt
  3. +0 −123
@@ -6,6 +6,8 @@ CHANGES

* Removed from this distribution and updated documentation
to point to the actively maintained virtualenv instead.
* Issue 64: use_setuptools no longer rebuilds the distribute egg every
time it is run
* use_setuptools now properly respects the requested version
@@ -1073,34 +1073,10 @@ system, but don't have root access, you can create your own "virtual"
Python installation, which uses its own library directories and some symlinks
to the site-wide Python.

In the simplest case, your virtual Python installation will live under the
``~/lib/python2.x``, ``~/include/python2.x``, and ``~/bin`` directories. Just
download ``_ and run it using the site-wide Python. If you
want to customize the location, you can use the ``--prefix`` option to specify
an installation base directory in place of ``~``. (Use ``--help`` to get the
complete list of options.)


When you're done, you'll have a ``~/bin/python`` executable that's linked to
the local Python installation and inherits all its current libraries, but which
allows you to add as many new libraries as you want. Simply use this new
Python in place of your system-defined one, and you can modify it as you like
without breaking anything that relies on the system Python. You'll also still
need to follow the standard `installation instructions`_ to install setuptools
and EasyInstall, using your new ``~/bin/python`` executable in place of the
system Python.

Note that if you were previously setting a ``PYTHONPATH`` and/or had other
special configuration options in your ``~/.pydistutils.cfg``, you may need to
remove these settings *before* running ````. This is because
your new Python executable will not need *any* custom configuration for the
distutils or EasyInstall; everything will go to the correct ``~/lib`` and
``~/bin`` directories automatically.

You should, however, also make sure that the ``bin`` subdirectory of your
installation prefix (e.g. ``~/bin``) is on your ``PATH``, because that is where
EasyInstall and the distutils will install new Python scripts.
Please refer to the `virtualenv`_ documentation for creating such an

.. _virtualenv:

"Traditional" ``PYTHONPATH``-based Installation

This file was deleted.

0 comments on commit 43d3473

Please sign in to comment.