2005-07-16 05:21:18 +08:00
|
|
|
=====================
|
|
|
|
How to install Django
|
|
|
|
=====================
|
|
|
|
|
2005-07-16 05:51:05 +08:00
|
|
|
This document will get you up and running with Django.
|
|
|
|
|
2005-11-12 11:24:32 +08:00
|
|
|
Install Python
|
|
|
|
==============
|
|
|
|
|
|
|
|
Being a Python Web framework, Django requires Python.
|
|
|
|
|
2011-06-10 04:01:28 +08:00
|
|
|
It works with any Python version from 2.5 to 2.7 (due to backwards
|
2008-12-10 06:39:58 +08:00
|
|
|
incompatibilities in Python 3.0, Django does not currently work with
|
2010-08-20 03:27:44 +08:00
|
|
|
Python 3.0; see :doc:`the Django FAQ </faq/install>` for more
|
2008-12-10 06:48:23 +08:00
|
|
|
information on supported Python versions and the 3.0 transition).
|
2005-11-12 11:24:32 +08:00
|
|
|
|
2007-05-19 12:17:54 +08:00
|
|
|
Get Python at http://www.python.org. If you're running Linux or Mac OS X, you
|
|
|
|
probably already have it installed.
|
2005-11-12 11:24:32 +08:00
|
|
|
|
2008-08-26 23:52:21 +08:00
|
|
|
.. admonition:: Django on Jython
|
|
|
|
|
|
|
|
If you use Jython_ (a Python implementation for the Java platform), you'll
|
2010-08-20 03:27:44 +08:00
|
|
|
need to follow a few additional steps. See :doc:`/howto/jython` for details.
|
2008-08-26 23:52:21 +08:00
|
|
|
|
|
|
|
.. _jython: http://jython.org/
|
|
|
|
|
2009-05-13 01:23:33 +08:00
|
|
|
Install Apache and mod_wsgi
|
2005-07-16 05:51:05 +08:00
|
|
|
=============================
|
|
|
|
|
2010-08-28 10:40:57 +08:00
|
|
|
If you just want to experiment with Django, skip ahead to the next
|
2011-06-17 00:34:12 +08:00
|
|
|
section; Django includes a lightweight web server you can use for
|
2010-08-28 10:40:57 +08:00
|
|
|
testing, so you won't need to set up Apache until you're ready to
|
|
|
|
deploy Django in production.
|
|
|
|
|
2011-06-17 00:34:12 +08:00
|
|
|
If you want to use Django on a production site, use `Apache`_ with
|
2010-08-28 10:40:57 +08:00
|
|
|
`mod_wsgi`_. mod_wsgi can operate in one of two modes: an embedded
|
|
|
|
mode and a daemon mode. In embedded mode, mod_wsgi is similar to
|
|
|
|
mod_perl -- it embeds Python within Apache and loads Python code into
|
|
|
|
memory when the server starts. Code stays in memory throughout the
|
|
|
|
life of an Apache process, which leads to significant performance
|
|
|
|
gains over other server arrangements. In daemon mode, mod_wsgi spawns
|
|
|
|
an independent daemon process that handles requests. The daemon
|
2010-10-09 16:12:50 +08:00
|
|
|
process can run as a different user than the Web server, possibly
|
2010-08-28 10:40:57 +08:00
|
|
|
leading to improved security, and the daemon process can be restarted
|
2010-10-09 16:12:50 +08:00
|
|
|
without restarting the entire Apache Web server, possibly making
|
2010-08-28 10:40:57 +08:00
|
|
|
refreshing your codebase more seamless. Consult the mod_wsgi
|
|
|
|
documentation to determine which mode is right for your setup. Make
|
|
|
|
sure you have Apache installed, with the mod_wsgi module activated.
|
|
|
|
Django will work with any version of Apache that supports mod_wsgi.
|
|
|
|
|
|
|
|
See :doc:`How to use Django with mod_wsgi </howto/deployment/modwsgi>`
|
|
|
|
for information on how to configure mod_wsgi once you have it
|
|
|
|
installed.
|
|
|
|
|
|
|
|
If you can't use mod_wsgi for some reason, fear not: Django supports
|
2011-06-17 00:34:12 +08:00
|
|
|
many other deployment options. One is :doc:`uWSGI </howto/deployment/fastcgi>`;
|
|
|
|
it works very well with `nginx`_. Another is :doc:`FastCGI
|
2010-08-28 10:40:57 +08:00
|
|
|
</howto/deployment/fastcgi>`, perfect for using Django with servers
|
|
|
|
other than Apache. Additionally, Django follows the WSGI_ spec, which
|
|
|
|
allows it to run on a variety of server platforms. See the
|
|
|
|
`server-arrangements wiki page`_ for specific installation
|
|
|
|
instructions for each platform.
|
2005-07-16 05:51:05 +08:00
|
|
|
|
|
|
|
.. _Apache: http://httpd.apache.org/
|
2011-06-17 00:34:12 +08:00
|
|
|
.. _nginx: http://nginx.net/
|
2009-05-13 01:23:33 +08:00
|
|
|
.. _mod_wsgi: http://code.google.com/p/modwsgi/
|
2009-12-26 14:37:26 +08:00
|
|
|
.. _WSGI: http://www.python.org/dev/peps/pep-0333/
|
2005-10-12 21:25:24 +08:00
|
|
|
.. _server-arrangements wiki page: http://code.djangoproject.com/wiki/ServerArrangements
|
2005-07-16 05:51:05 +08:00
|
|
|
|
2008-08-24 06:25:40 +08:00
|
|
|
.. _database-installation:
|
|
|
|
|
2005-07-16 05:51:05 +08:00
|
|
|
Get your database running
|
|
|
|
=========================
|
|
|
|
|
2009-06-24 22:00:53 +08:00
|
|
|
If you plan to use Django's database API functionality, you'll need to make
|
|
|
|
sure a database server is running. Django supports many different database
|
|
|
|
servers and is officially supported with PostgreSQL_, MySQL_, Oracle_ and
|
|
|
|
SQLite_ (although SQLite doesn't require a separate server to be running).
|
2005-07-16 05:51:05 +08:00
|
|
|
|
2009-06-24 22:00:53 +08:00
|
|
|
In addition to the officially supported databases, there are backends provided
|
|
|
|
by 3rd parties that allow you to use other databases with Django:
|
|
|
|
|
|
|
|
* `Sybase SQL Anywhere`_
|
|
|
|
* `IBM DB2`_
|
|
|
|
* `Microsoft SQL Server 2005`_
|
|
|
|
* Firebird_
|
|
|
|
* ODBC_
|
|
|
|
|
|
|
|
The Django versions and ORM features supported by these unofficial backends
|
|
|
|
vary considerably. Queries regarding the specific capabilities of these
|
|
|
|
unofficial backends, along with any support queries, should be directed to the
|
|
|
|
support channels provided by each 3rd party project.
|
|
|
|
|
|
|
|
In addition to a database backend, you'll need to make sure your Python
|
|
|
|
database bindings are installed.
|
2005-07-19 02:47:55 +08:00
|
|
|
|
2011-04-18 04:45:06 +08:00
|
|
|
* If you're using PostgreSQL, you'll need the ``postgresql_psycopg2`` package.
|
2010-11-08 05:42:11 +08:00
|
|
|
You might want to refer to our :ref:`PostgreSQL notes <postgresql-notes>` for
|
|
|
|
further technical details specific to this database.
|
2007-04-26 22:58:18 +08:00
|
|
|
|
2007-02-27 05:39:09 +08:00
|
|
|
If you're on Windows, check out the unofficial `compiled Windows version`_.
|
2007-05-11 17:51:07 +08:00
|
|
|
|
2008-08-24 06:25:40 +08:00
|
|
|
* If you're using MySQL, you'll need MySQLdb_, version 1.2.1p2 or higher. You
|
2010-11-08 05:42:11 +08:00
|
|
|
will also want to read the database-specific :ref:`notes for the MySQL
|
|
|
|
backend <mysql-notes>`.
|
2007-02-27 05:39:09 +08:00
|
|
|
|
2009-02-28 14:03:18 +08:00
|
|
|
* If you're using Oracle, you'll need a copy of cx_Oracle_, but please
|
2010-11-08 05:42:11 +08:00
|
|
|
read the database-specific :ref:`notes for the Oracle backend <oracle-notes>`
|
|
|
|
for important information regarding supported versions of both Oracle and
|
|
|
|
``cx_Oracle``.
|
2007-06-23 22:16:00 +08:00
|
|
|
|
2009-06-24 22:00:53 +08:00
|
|
|
* If you're using an unofficial 3rd party backend, please consult the
|
|
|
|
documentation provided for any additional requirements.
|
|
|
|
|
2007-09-15 12:58:41 +08:00
|
|
|
If you plan to use Django's ``manage.py syncdb`` command to
|
|
|
|
automatically create database tables for your models, you'll need to
|
2007-12-02 01:44:59 +08:00
|
|
|
ensure that Django has permission to create and alter tables in the
|
|
|
|
database you're using; if you plan to manually create the tables, you
|
|
|
|
can simply grant Django ``SELECT``, ``INSERT``, ``UPDATE`` and
|
2007-12-04 14:07:44 +08:00
|
|
|
``DELETE`` permissions. On some databases, Django will need
|
|
|
|
``ALTER TABLE`` privileges during ``syncdb`` but won't issue
|
|
|
|
``ALTER TABLE`` statements on a table once ``syncdb`` has created it.
|
|
|
|
|
2010-08-20 03:27:44 +08:00
|
|
|
If you're using Django's :doc:`testing framework</topics/testing>` to test database queries,
|
2007-12-04 14:07:44 +08:00
|
|
|
Django will need permission to create a test database.
|
2007-09-15 12:58:41 +08:00
|
|
|
|
2005-07-16 05:51:05 +08:00
|
|
|
.. _PostgreSQL: http://www.postgresql.org/
|
|
|
|
.. _MySQL: http://www.mysql.com/
|
2008-09-14 17:34:31 +08:00
|
|
|
.. _psycopg: http://initd.org/pub/software/psycopg/
|
2005-07-19 02:47:55 +08:00
|
|
|
.. _compiled Windows version: http://stickpeople.com/projects/python/win-psycopg/
|
2005-07-16 06:45:03 +08:00
|
|
|
.. _MySQLdb: http://sourceforge.net/projects/mysql-python
|
2005-07-29 02:21:46 +08:00
|
|
|
.. _SQLite: http://www.sqlite.org/
|
2009-12-26 14:37:26 +08:00
|
|
|
.. _pysqlite: http://trac.edgewall.org/wiki/PySqlite
|
2007-09-16 23:57:15 +08:00
|
|
|
.. _cx_Oracle: http://cx-oracle.sourceforge.net/
|
2007-06-26 20:53:33 +08:00
|
|
|
.. _Oracle: http://www.oracle.com/
|
2009-06-24 22:00:53 +08:00
|
|
|
.. _Sybase SQL Anywhere: http://code.google.com/p/sqlany-django/
|
|
|
|
.. _IBM DB2: http://code.google.com/p/ibm-db/
|
|
|
|
.. _Microsoft SQL Server 2005: http://code.google.com/p/django-mssql/
|
|
|
|
.. _Firebird: http://code.google.com/p/django-firebird/
|
|
|
|
.. _ODBC: http://code.google.com/p/django-pyodbc/
|
2008-08-24 06:25:40 +08:00
|
|
|
.. _removing-old-versions-of-django:
|
2005-07-16 05:51:05 +08:00
|
|
|
|
2007-04-12 21:59:09 +08:00
|
|
|
Remove any old versions of Django
|
|
|
|
=================================
|
|
|
|
|
2007-05-11 17:51:07 +08:00
|
|
|
If you are upgrading your installation of Django from a previous version,
|
|
|
|
you will need to uninstall the old Django version before installing the
|
|
|
|
new version.
|
2007-04-12 21:59:09 +08:00
|
|
|
|
|
|
|
If you installed Django using ``setup.py install``, uninstalling
|
2007-05-11 17:51:07 +08:00
|
|
|
is as simple as deleting the ``django`` directory from your Python
|
2007-04-12 21:59:09 +08:00
|
|
|
``site-packages``.
|
|
|
|
|
2007-06-20 14:23:15 +08:00
|
|
|
If you installed Django from a Python egg, remove the Django ``.egg`` file,
|
2007-05-11 17:51:07 +08:00
|
|
|
and remove the reference to the egg in the file named ``easy-install.pth``.
|
2007-04-12 21:59:09 +08:00
|
|
|
This file should also be located in your ``site-packages`` directory.
|
|
|
|
|
2010-11-23 11:54:13 +08:00
|
|
|
.. _finding-site-packages:
|
|
|
|
|
2007-04-12 21:59:09 +08:00
|
|
|
.. admonition:: Where are my ``site-packages`` stored?
|
|
|
|
|
|
|
|
The location of the ``site-packages`` directory depends on the operating
|
2007-06-20 14:23:15 +08:00
|
|
|
system, and the location in which Python was installed. To find out your
|
2008-08-24 06:25:40 +08:00
|
|
|
system's ``site-packages`` location, execute the following:
|
2009-04-01 09:36:44 +08:00
|
|
|
|
2008-08-24 06:25:40 +08:00
|
|
|
.. code-block:: bash
|
2007-05-11 17:51:07 +08:00
|
|
|
|
2007-06-20 14:23:15 +08:00
|
|
|
python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"
|
2007-04-12 21:59:09 +08:00
|
|
|
|
2007-06-20 14:23:15 +08:00
|
|
|
(Note that this should be run from a shell prompt, not a Python interactive
|
|
|
|
prompt.)
|
2009-04-01 09:36:44 +08:00
|
|
|
|
2011-08-22 15:36:42 +08:00
|
|
|
Some Debian-based Linux distributions have separate ``site-packages``
|
|
|
|
directories for user-installed packages, such as when installing Django
|
|
|
|
from a downloaded tarball. The command listed above will give you the
|
|
|
|
system's ``site-packages``, the user's directory can be found in
|
|
|
|
``/usr/local/lib/`` instead of ``/usr/lib/``.
|
|
|
|
|
2008-08-26 23:52:21 +08:00
|
|
|
.. _install-django-code:
|
2007-04-12 21:59:09 +08:00
|
|
|
|
2005-07-16 05:51:05 +08:00
|
|
|
Install the Django code
|
|
|
|
=======================
|
|
|
|
|
2005-07-16 05:21:18 +08:00
|
|
|
Installation instructions are slightly different depending on whether you're
|
2008-08-24 06:25:40 +08:00
|
|
|
installing a distribution-specific package, downloading the latest official
|
2007-07-12 22:41:32 +08:00
|
|
|
release, or fetching the latest development version.
|
2005-07-16 05:21:18 +08:00
|
|
|
|
2007-07-12 22:41:32 +08:00
|
|
|
It's easy, no matter which way you choose.
|
2005-07-16 05:21:18 +08:00
|
|
|
|
2007-07-12 22:41:32 +08:00
|
|
|
Installing a distribution-specific package
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
2005-07-16 05:21:18 +08:00
|
|
|
|
2010-08-20 03:27:44 +08:00
|
|
|
Check the :doc:`distribution specific notes </misc/distributions>` to see if your
|
2007-07-12 22:41:32 +08:00
|
|
|
platform/distribution provides official Django packages/installers.
|
2008-08-24 06:25:40 +08:00
|
|
|
Distribution-provided packages will typically allow for automatic installation
|
|
|
|
of dependencies and easy upgrade paths.
|
|
|
|
|
|
|
|
.. _installing-official-release:
|
2007-02-27 07:23:01 +08:00
|
|
|
|
2007-07-12 22:41:32 +08:00
|
|
|
Installing an official release
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
2007-02-27 07:23:01 +08:00
|
|
|
|
2007-07-12 22:41:32 +08:00
|
|
|
1. Download the latest release from our `download page`_.
|
2007-02-27 07:23:01 +08:00
|
|
|
|
2007-09-14 16:04:07 +08:00
|
|
|
2. Untar the downloaded file (e.g. ``tar xzvf Django-NNN.tar.gz``,
|
|
|
|
where ``NNN`` is the version number of the latest release).
|
2007-09-14 23:33:42 +08:00
|
|
|
If you're using Windows, you can download the command-line tool
|
2007-09-14 16:04:07 +08:00
|
|
|
bsdtar_ to do this, or you can use a GUI-based tool such as 7-zip_.
|
2007-02-27 07:23:01 +08:00
|
|
|
|
2007-09-14 16:04:07 +08:00
|
|
|
3. Change into the directory created in step 2 (e.g. ``cd Django-NNN``).
|
2007-07-12 22:41:32 +08:00
|
|
|
|
2007-09-14 23:33:42 +08:00
|
|
|
4. If you're using Linux, Mac OS X or some other flavor of Unix, enter
|
|
|
|
the command ``sudo python setup.py install`` at the shell prompt.
|
|
|
|
If you're using Windows, start up a command shell with administrator
|
2007-09-14 16:04:07 +08:00
|
|
|
privileges and run the command ``setup.py install``.
|
2005-07-21 09:33:13 +08:00
|
|
|
|
2007-09-14 16:04:07 +08:00
|
|
|
These commands will install Django in your Python installation's
|
|
|
|
``site-packages`` directory.
|
2005-11-16 13:35:59 +08:00
|
|
|
|
2007-09-14 16:04:07 +08:00
|
|
|
.. _bsdtar: http://gnuwin32.sourceforge.net/packages/bsdtar.htm
|
|
|
|
.. _7-zip: http://www.7-zip.org/
|
2005-07-16 05:21:18 +08:00
|
|
|
|
2008-08-24 06:25:40 +08:00
|
|
|
.. _installing-development-version:
|
|
|
|
|
2005-07-16 05:21:18 +08:00
|
|
|
Installing the development version
|
2005-07-16 05:51:05 +08:00
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
2005-07-16 05:21:18 +08:00
|
|
|
|
2008-03-19 07:18:52 +08:00
|
|
|
.. admonition:: Tracking Django development
|
2009-04-01 09:36:44 +08:00
|
|
|
|
2008-03-19 07:18:52 +08:00
|
|
|
If you decide to use the latest development version of Django,
|
|
|
|
you'll want to pay close attention to `the development timeline`_,
|
|
|
|
and you'll want to keep an eye on `the list of
|
2008-03-25 12:42:21 +08:00
|
|
|
backwards-incompatible changes`_. This will help you stay on top
|
2008-03-19 07:18:52 +08:00
|
|
|
of any new features you might want to use, as well as any changes
|
2008-03-25 12:42:21 +08:00
|
|
|
you'll need to make to your code when updating your copy of Django.
|
|
|
|
(For stable releases, any necessary changes are documented in the
|
|
|
|
release notes.)
|
2008-03-19 07:18:52 +08:00
|
|
|
|
|
|
|
.. _the development timeline: http://code.djangoproject.com/timeline
|
|
|
|
.. _the list of backwards-incompatible changes: http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges
|
|
|
|
|
2006-10-17 06:38:18 +08:00
|
|
|
If you'd like to be able to update your Django code occasionally with the
|
|
|
|
latest bug fixes and improvements, follow these instructions:
|
|
|
|
|
2011-06-27 00:52:13 +08:00
|
|
|
1. Make sure that you have Subversion_, Git_, or Mercurial_ installed, and
|
|
|
|
that you can run its commands from a shell. (Enter ``svn help``,
|
|
|
|
``git help``, or ``hg help`` at a shell prompt to test this.) Note that
|
|
|
|
the Subversion repository is the canonical source for the official
|
|
|
|
Git and Mercurial repositories and as such will always be the most up-to-date.
|
2007-06-20 14:23:15 +08:00
|
|
|
|
2008-08-24 06:25:40 +08:00
|
|
|
2. Check out Django's main development branch (the 'trunk') like so:
|
|
|
|
|
|
|
|
.. code-block:: bash
|
2005-07-16 05:52:16 +08:00
|
|
|
|
2011-06-27 00:52:13 +08:00
|
|
|
# Subversion
|
2007-09-14 16:04:07 +08:00
|
|
|
svn co http://code.djangoproject.com/svn/django/trunk/ django-trunk
|
|
|
|
|
2011-06-27 00:52:13 +08:00
|
|
|
Mirrors of the Subversion repository can be obtained like so:
|
|
|
|
|
|
|
|
.. code-block:: bash
|
|
|
|
|
|
|
|
# Git
|
|
|
|
git clone https://github.com/django/django.git
|
|
|
|
|
|
|
|
# Mercurial
|
|
|
|
hg clone https://bitbucket.org/django/django
|
|
|
|
|
|
|
|
.. warning ::
|
|
|
|
|
|
|
|
These mirrors should be updated every 5 minutes but aren't guaranteed
|
|
|
|
to be up-to-date since they are hosted on external services.
|
|
|
|
|
2010-11-23 11:54:13 +08:00
|
|
|
3. Next, make sure that the Python interpreter can load Django's code. The most
|
2010-11-28 05:47:08 +08:00
|
|
|
convenient way to do this is to `modify Python's search path`_. Add a ``.pth``
|
2010-11-23 11:54:13 +08:00
|
|
|
file containing the full path to the ``django-trunk`` directory to your
|
|
|
|
system's ``site-packages`` directory. For example, on a Unix-like system:
|
2009-04-01 09:36:44 +08:00
|
|
|
|
2008-08-24 06:25:40 +08:00
|
|
|
.. code-block:: bash
|
2007-09-14 16:04:07 +08:00
|
|
|
|
2010-11-23 11:54:13 +08:00
|
|
|
echo WORKING-DIR/django-trunk > SITE-PACKAGES-DIR/django.pth
|
2005-07-16 05:52:16 +08:00
|
|
|
|
2007-06-20 14:23:15 +08:00
|
|
|
(In the above line, change ``SITE-PACKAGES-DIR`` to match the location of
|
|
|
|
your system's ``site-packages`` directory, as explained in the
|
2010-11-23 11:54:13 +08:00
|
|
|
:ref:`Where are my site-packages stored? <finding-site-packages>` section
|
|
|
|
above. Change ``WORKING-DIR/django-trunk`` to match the full path to your
|
|
|
|
new ``django-trunk`` directory.)
|
2006-10-17 06:38:18 +08:00
|
|
|
|
2007-11-30 00:57:20 +08:00
|
|
|
4. On Unix-like systems, create a symbolic link to the file
|
|
|
|
``django-trunk/django/bin/django-admin.py`` in a directory on your system
|
2008-08-24 06:25:40 +08:00
|
|
|
path, such as ``/usr/local/bin``. For example:
|
2009-04-01 09:36:44 +08:00
|
|
|
|
2008-08-24 06:25:40 +08:00
|
|
|
.. code-block:: bash
|
2007-11-30 00:57:20 +08:00
|
|
|
|
2010-10-09 15:27:19 +08:00
|
|
|
ln -s WORKING-DIR/django-trunk/django/bin/django-admin.py /usr/local/bin
|
2010-11-08 05:42:11 +08:00
|
|
|
|
2010-10-09 15:27:19 +08:00
|
|
|
(In the above line, change WORKING-DIR to match the full path to your new
|
2010-10-09 15:35:46 +08:00
|
|
|
``django-trunk`` directory.)
|
2007-11-30 00:57:20 +08:00
|
|
|
|
|
|
|
This simply lets you type ``django-admin.py`` from within any directory,
|
|
|
|
rather than having to qualify the command with the full path to the file.
|
|
|
|
|
|
|
|
On Windows systems, the same result can be achieved by copying the file
|
|
|
|
``django-trunk/django/bin/django-admin.py`` to somewhere on your system
|
|
|
|
path, for example ``C:\Python24\Scripts``.
|
2006-10-17 06:38:18 +08:00
|
|
|
|
2007-09-14 16:04:07 +08:00
|
|
|
You *don't* have to run ``python setup.py install``, because you've already
|
|
|
|
carried out the equivalent actions in steps 3 and 4.
|
2005-07-18 22:03:56 +08:00
|
|
|
|
2006-10-17 06:38:18 +08:00
|
|
|
When you want to update your copy of the Django source code, just run the
|
2007-09-14 16:04:07 +08:00
|
|
|
command ``svn update`` from within the ``django-trunk`` directory. When you do
|
|
|
|
this, Subversion will automatically download any changes.
|
2005-07-16 05:21:18 +08:00
|
|
|
|
2005-07-16 06:14:15 +08:00
|
|
|
.. _`download page`: http://www.djangoproject.com/download/
|
2005-07-16 05:26:43 +08:00
|
|
|
.. _Subversion: http://subversion.tigris.org/
|
2011-06-27 00:52:13 +08:00
|
|
|
.. _Git: http://git-scm.com/
|
|
|
|
.. _Mercurial: http://mercurial.selenic.com/
|
2010-11-28 05:47:08 +08:00
|
|
|
.. _`modify Python's search path`: http://docs.python.org/install/index.html#modifying-python-s-search-path
|