Ticket #19344: 19344.diff
File 19344.diff, 3.6 KB (added by , 12 years ago) |
---|
-
docs/faq/troubleshooting.txt
diff --git a/docs/faq/troubleshooting.txt b/docs/faq/troubleshooting.txt index f984be4..a961096 100644
a b Troubleshooting 5 5 This page contains some advice about errors and problems commonly encountered 6 6 during the development of Django applications. 7 7 8 .. _troubleshooting-django-admin: 9 10 Problems running django-admin.py 11 -------------------------------- 12 8 13 "command not found: django-admin.py" 9 ------------------------------------ 14 ==================================== 10 15 11 16 :doc:`django-admin.py </ref/django-admin>` should be on your system path if you 12 17 installed Django via ``python setup.py``. If it's not on your path, you can 13 18 find it in ``site-packages/django/bin``, where ``site-packages`` is a directory 14 19 within your Python installation. Consider symlinking to :doc:`django-admin.py 15 20 </ref/django-admin>` from some place on your path, such as 16 :file:`/usr/local/bin`. 17 No newline at end of file 21 :file:`/usr/local/bin`. 22 23 Script name may differ in distribution packages 24 =============================================== 25 26 If you installed Django using a Linux distribution's package manager 27 (e.g. ``apt-get`` or ``yum``) ``django-admin.py`` may have been renamed to 28 ``django-admin``; use that instead. 29 30 Mac OS X permissions 31 ==================== 32 33 If you're using Mac OS X, you may see the message "permission denied" when 34 you try to run ``django-admin.py startproject``. This is because, on 35 Unix-based systems like OS X, a file must be marked as "executable" before it 36 can be run as a program. To do this, open Terminal.app and navigate (using 37 the ``cd`` command) to the directory where :doc:`django-admin.py 38 </ref/django-admin>` is installed, then run the command 39 ``sudo chmod +x django-admin.py``. 40 41 Running virtualenv on Windows 42 ============================= 43 44 If you used virtualenv_ to :ref:`install Django <installing-official-release>` 45 on Windows, you may get an ``ImportError`` when you try to run 46 ``django-admin.py startproject``. This is because Windows does not run the 47 Python interpreter from your virtual environment unless you invoke it 48 directly. Instead, prefix all commands that use .py files with ``python`` and 49 use the full path to the file, like so: 50 ``python C:\pythonXY\Scripts\django-admin.py startproject mysite``. 51 52 .. _virtualenv: http://www.virtualenv.org/ -
docs/intro/tutorial01.txt
diff --git a/docs/intro/tutorial01.txt b/docs/intro/tutorial01.txt index 9913b21..5275cc5 100644
a b code, then run the following command: 53 53 django-admin.py startproject mysite 54 54 55 55 This will create a ``mysite`` directory in your current directory. If it didn't 56 work, see :doc:`Troubleshooting </faq/troubleshooting>`. 57 58 .. admonition:: Script name may differ in distribution packages 59 60 If you installed Django using a Linux distribution's package manager 61 (e.g. apt-get or yum) ``django-admin.py`` may have been renamed to 62 ``django-admin``. You may continue through this documentation by omitting 63 ``.py`` from each command. 64 65 .. admonition:: Mac OS X permissions 66 67 If you're using Mac OS X, you may see the message "permission denied" when 68 you try to run ``django-admin.py startproject``. This is because, on 69 Unix-based systems like OS X, a file must be marked as "executable" before it 70 can be run as a program. To do this, open Terminal.app and navigate (using 71 the ``cd`` command) to the directory where :doc:`django-admin.py 72 </ref/django-admin>` is installed, then run the command 73 ``sudo chmod +x django-admin.py``. 56 work, see :ref:`Troubleshooting <troubleshooting-django-admin>`. 74 57 75 58 .. note:: 76 59