5
How to install Django This document will get you up and running with Django. Install Python Being a Python Web framework, Django requires Python. It works with any Python version from 2.4 to 2.7 (due to backwards incompatibilities in Python 3.0, Django does not currently work with Python 3.0; see the Django FAQ for more information on supported Python versions and the 3.0 transition). Get Python at http://www.python.org. If you’re running Linux or Mac OS X, you probably already have it installed. Django on Jython If you use Jython (a Python implementation for the Java platform), you’ll need to follow a few additional steps. See Running Django on Jython for details. Install Apache and mod_wsgi If you just want to experiment with Django, skip ahead to the next section; Django includes a lightweight Web server you can use for testing, so you won’t need to set up Apache until you’re ready to deploy Django in production. If you want to use Django on a production site, use Apache with 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 process can run as a different user than the Web server, possibly leading to improved security, and the daemon process can be restarted without restarting the entire Apache Web server, possibly making 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 How to use Django with mod_wsgi 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 many other deployment options. Another option is 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. Get your database running This document is for an insecure version of Django that is no longer supported. Please upgrade to a newer release! How to install Django | Django documentation | Django https://docs.djangoproject.com/en/1.3/topics/install/ 1 de 5 09/07/2014 02:03 p.m.

How to Install Django _ Django Documentation _ Django

Embed Size (px)

Citation preview

Page 1: How to Install Django _ Django Documentation _ Django

How to install DjangoThis document will get you up and running with Django.

Install Python

Being a Python Web framework, Django requires Python.

It works with any Python version from 2.4 to 2.7 (due to backwards incompatibilities inPython 3.0, Django does not currently work with Python 3.0; see the Django FAQ for moreinformation on supported Python versions and the 3.0 transition).

Get Python at http://www.python.org. If you’re running Linux or Mac OS X, you probablyalready have it installed.

Django on Jython

If you use Jython (a Python implementation for the Java platform), you’ll need tofollow a few additional steps. See Running Django on Jython for details.

Install Apache and mod_wsgi

If you just want to experiment with Django, skip ahead to the next section; Django includesa lightweight Web server you can use for testing, so you won’t need to set up Apache untilyou’re ready to deploy Django in production.

If you want to use Django on a production site, use Apache with mod_wsgi. mod_wsgi canoperate 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 codeinto memory when the server starts. Code stays in memory throughout the life of an Apacheprocess, which leads to significant performance gains over other server arrangements. Indaemon mode, mod_wsgi spawns an independent daemon process that handles requests.The daemon process can run as a different user than the Web server, possibly leading toimproved security, and the daemon process can be restarted without restarting the entireApache Web server, possibly making refreshing your codebase more seamless. Consult themod_wsgi documentation to determine which mode is right for your setup. Make sure youhave Apache installed, with the mod_wsgi module activated. Django will work with anyversion of Apache that supports mod_wsgi.

See How to use Django with mod_wsgi for information on how to configure mod_wsgi onceyou have it installed.

If you can’t use mod_wsgi for some reason, fear not: Django supports many otherdeployment options. Another option is FastCGI, perfect for using Django with servers otherthan Apache. Additionally, Django follows the WSGI spec, which allows it to run on a varietyof server platforms. See the server-arrangements wiki page for specific installationinstructions for each platform.

Get your database running

This document is for an insecure version of Django that is no longer supported. Please upgrade to a newer release!

How to install Django | Django documentation | Django https://docs.djangoproject.com/en/1.3/topics/install/

1 de 5 09/07/2014 02:03 p.m.

Page 2: How to Install Django _ Django Documentation _ Django

server is running. Django supports many different database servers and is officiallysupported with PostgreSQL, MySQL, Oracle and SQLite (although SQLite doesn’t require aseparate server to be running).

In addition to the officially supported databases, there are backends provided by 3rd partiesthat 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 varyconsiderably. Queries regarding the specific capabilities of these unofficial backends, alongwith any support queries, should be directed to the support channels provided by each 3rdparty project.

In addition to a database backend, you’ll need to make sure your Python database bindingsare installed.

If you’re using PostgreSQL, you’ll need the psycopg package. Django supports bothversion 1 and 2. (When you configure Django’s database layer, specify eitherpostgresql [for version 1] or postgresql_psycopg2 [for version 2].) You might want torefer to our PostgreSQL notes for further technical details specific to this database.

If you’re on Windows, check out the unofficial compiled Windows version.

If you’re using MySQL, you’ll need MySQLdb, version 1.2.1p2 or higher. You will alsowant to read the database-specific notes for the MySQL backend.

If you’re using SQLite and Python 2.4, you’ll need pysqlite. Use version 2.0.3 or higher.Python 2.5 ships with an SQLite wrapper in the standard library, so you don’t need toinstall anything extra in that case. Please read the SQLite backend notes.

If you’re using Oracle, you’ll need a copy of cx_Oracle, but please read the database-specific notes for the Oracle backend for important information regarding supportedversions of both Oracle and cx_Oracle.

If you’re using an unofficial 3rd party backend, please consult the documentationprovided for any additional requirements.

If you plan to use Django’s manage.py syncdb command to automatically create databasetables for your models, you’ll need to ensure that Django has permission to create and altertables in the database you’re using; if you plan to manually create the tables, you cansimply grant Django SELECT, INSERT, UPDATE and DELETE permissions. On some databases,Django will need ALTER TABLE privileges during syncdb but won’t issue ALTER TABLEstatements on a table once syncdb has created it.

If you’re using Django’s testing framework to test database queries, Django will needpermission to create a test database.

Remove any old versions of Django

This document is for an insecure version of Django that is no longer supported. Please upgrade to a newer release!

How to install Django | Django documentation | Django https://docs.djangoproject.com/en/1.3/topics/install/

2 de 5 09/07/2014 02:03 p.m.

Page 3: How to Install Django _ Django Documentation _ Django

uninstall the old Django version before installing the new version.

If you installed Django using setup.py install, uninstalling is as simple as deleting thedjango directory from your Python site-packages.

If you installed Django from a Python egg, remove the Django .egg file, and remove thereference to the egg in the file named easy-install.pth. This file should also be located inyour site-packages directory.

Where are my site-packages stored?

The location of the site-packages directory depends on the operating system,and the location in which Python was installed. To find out your system’ssite-packages location, execute the following:

python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"

(Note that this should be run from a shell prompt, not a Python interactiveprompt.)

Install the Django code

Installation instructions are slightly different depending on whether you're installing adistribution-specific package, downloading the latest official release, or fetching the latestdevelopment version.

It's easy, no matter which way you choose.

Installing a distribution-specific package

Check the distribution specific notes to see if your platform/distribution provides officialDjango packages/installers. Distribution-provided packages will typically allow for automaticinstallation of dependencies and easy upgrade paths.

Installing an official release

Download the latest release from our download page.1.Untar the downloaded file (e.g. tar xzvf Django-NNN.tar.gz, where NNN is theversion number of the latest release). If you're using Windows, you can download thecommand-line tool bsdtar to do this, or you can use a GUI-based tool such as 7-zip.

2.

Change into the directory created in step 2 (e.g. cd Django-NNN).3.If you're using Linux, Mac OS X or some other flavor of Unix, enter the commandsudo python setup.py install at the shell prompt. If you're using Windows, start upa command shell with administrator privileges and run the commandsetup.py install.

4.

These commands will install Django in your Python installation's site-packages directory.

Installing the development version

This document is for an insecure version of Django that is no longer supported. Please upgrade to a newer release!

How to install Django | Django documentation | Django https://docs.djangoproject.com/en/1.3/topics/install/

3 de 5 09/07/2014 02:03 p.m.

Page 4: How to Install Django _ Django Documentation _ Django

If you decide to use the latest development version of Django, you'll want to payclose attention to the development timeline, and you'll want to keep an eye onthe list of backwards-incompatible changes. This will help you stay on top of anynew features you might want to use, as well as any changes you'll need to maketo your code when updating your copy of Django. (For stable releases, anynecessary changes are documented in the release notes.)

If you'd like to be able to update your Django code occasionally with the latest bug fixes andimprovements, follow these instructions:

Make sure that you have Subversion installed, and that you can run its commands froma shell. (Enter svn help at a shell prompt to test this.)

1.

Check out Django's main development branch (the 'trunk') like so:

svn co http://code.djangoproject.com/svn/django/trunk/ django-trunk

2.

Next, make sure that the Python interpreter can load Django's code. The mostconvenient way to do this is to modify Python's search path. Add a .pth file containingthe full path to the django-trunk directory to your system's site-packages directory.For example, on a Unix-like system:

echo WORKING-DIR/django-trunk > SITE-PACKAGES-DIR/django.pth

(In the above line, change SITE-PACKAGES-DIR to match the location of your system'ssite-packages directory, as explained in the Where are my site-packages stored?section above. Change WORKING-DIR/django-trunk to match the full path to your newdjango-trunk directory.)

3.

On Unix-like systems, create a symbolic link to the filedjango-trunk/django/bin/django-admin.py in a directory on your system path, suchas /usr/local/bin. For example:

ln -s WORKING-DIR/django-trunk/django/bin/django-admin.py /usr/local/bin

(In the above line, change WORKING-DIR to match the full path to your newdjango-trunk directory.)

This simply lets you type django-admin.py from within any directory, rather thanhaving to qualify the command with the full path to the file.

On Windows systems, the same result can be achieved by copying the filedjango-trunk/django/bin/django-admin.py to somewhere on your system path, forexample C:\Python24\Scripts.

4.

You don't have to run python setup.py install, because you've already carried out theequivalent actions in steps 3 and 4.

When you want to update your copy of the Django source code, just run the commandsvn update from within the django-trunk directory. When you do this, Subversion willautomatically download any changes.

This document is for an insecure version of Django that is no longer supported. Please upgrade to a newer release!

How to install Django | Django documentation | Django https://docs.djangoproject.com/en/1.3/topics/install/

4 de 5 09/07/2014 02:03 p.m.

Page 5: How to Install Django _ Django Documentation _ Django

© 2005-2014 Django Software Foundation unless otherwise noted. Django isa registered trademark of the Django Software Foundation. Linux Web hostinggraciously provided by Media Temple.

This document is for an insecure version of Django that is no longer supported. Please upgrade to a newer release!

How to install Django | Django documentation | Django https://docs.djangoproject.com/en/1.3/topics/install/

5 de 5 09/07/2014 02:03 p.m.