Django

Code

Changeset 6190

Show
Ignore:
Timestamp:
09/14/07 10:33:42 (1 year ago)
Author:
adrian
Message:

Edited docs/install.txt changes from [6178]

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • django/trunk/docs/install.txt

    r6178 r6190  
    130130    2. Untar the downloaded file (e.g. ``tar xzvf Django-NNN.tar.gz``, 
    131131       where ``NNN`` is the version number of the latest release). 
    132        If you are a Windows user, you can download the command-line tool 
     132       If you're using Windows, you can download the command-line tool 
    133133       bsdtar_ to do this, or you can use a GUI-based tool such as 7-zip_. 
    134134 
    135135    3. Change into the directory created in step 2 (e.g. ``cd Django-NNN``). 
    136136 
    137     4. If you are using Linux, Mac OSX or some other flavour of Unix, enter 
    138        the command``sudo python setup.py install`` at the shell prompt. 
    139        If you are using Windows, start up a command shell with administrator 
     137    4. If you're using Linux, Mac OS X or some other flavor of Unix, enter 
     138       the command ``sudo python setup.py install`` at the shell prompt. 
     139       If you're using Windows, start up a command shell with administrator 
    140140       privileges and run the command ``setup.py install``. 
    141141 
    …… 
    154154 
    1551551. Make sure that you have Subversion_ installed, and that you can run its 
    156    commands from a shell. (Enter ``svn help`` at a shell prompt to test 
     156   commands from a shell. (Enter ``svn help`` at a shell prompt to test 
    157157   this.) 
    158158 
    …… 
    161161       svn co http://code.djangoproject.com/svn/django/trunk/ django-trunk 
    162162 
    163 3. Next, you need to make sure that the Python interpreter can load Django's 
    164    code.  There are various ways of accomplishing this.  One of the most 
    165    convenient, on Linux, Mac OSX or other Unix-like systems, is to use a 
    166    symbolic link:: 
     1633. Next, make sure that the Python interpreter can load Django's code. There 
     164   are various ways of accomplishing this.  One of the most convenient, on 
     165   Linux, Mac OSX or other Unix-like systems, is to use a symbolic link:: 
    167166 
    168167       ln -s `pwd`/django-trunk/django SITE-PACKAGES-DIR/django 
    …… 
    175174   so that it includes the ``django`` subdirectory of ``django-trunk``. 
    176175   This is perhaps the most convenient solution on Windows systems, which 
    177    don't support symbolic links. (Environment variables can be defined on 
     176   don't support symbolic links. (Environment variables can be defined on 
    178177   Windows systems `from the Control Panel`_.) 
    179178 
    180179   .. admonition:: What about Apache and mod_python? 
    181180 
    182       If you are using Apache and mod_python rather than Django's 
    183       development server, then instead of defining the ``PYTHONPATH`` 
    184       shell environment variable, you will need to specify the 
    185       ``PythonPath`` directive in your Apache configuration file. 
     181      If you take the approach of setting ``PYTHONPATH``, you'll need to 
     182      remember to do the same thing in your Apache configuration once you 
     183      deploy your production site. Do this by setting ``PythonPath`` in your 
     184      Apache configuration file. 
     185 
     186      More information about deployment is available, of course, in our 
     187      `How to use Django with mod_python`_ documentation. 
     188 
     189      .. _How to use Django with mod_python: ../modpython/ 
    186190 
    1871914. Copy the file ``django-trunk/django/bin/django-admin.py`` to somewhere on