Permalink
Browse files

Fixed many more ReST indentation errors, somehow accidentally missed …

…from [16955]

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16983 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 5109ac3 commit d1e5c55258d624058a93c8cacdb1f25ae7857554 @spookylukey spookylukey committed Oct 14, 2011
Showing with 5,861 additions and 5,893 deletions.
  1. +10 −10 docs/faq/admin.txt
  2. +9 −9 docs/faq/contributing.txt
  3. +5 −5 docs/faq/install.txt
  4. +29 −29 docs/faq/usage.txt
  5. +22 −22 docs/howto/apache-auth.txt
  6. +5 −5 docs/howto/custom-file-storage.txt
  7. +60 −60 docs/howto/custom-model-fields.txt
  8. +202 −202 docs/howto/custom-template-tags.txt
  9. +3 −3 docs/howto/deployment/fastcgi.txt
  10. +17 −17 docs/howto/deployment/modpython.txt
  11. +9 −9 docs/howto/deployment/modwsgi.txt
  12. +36 −48 docs/howto/error-reporting.txt
  13. +16 −16 docs/howto/i18n.txt
  14. +6 −6 docs/howto/jython.txt
  15. +6 −6 docs/howto/legacy-databases.txt
  16. +22 −22 docs/howto/outputting-csv.txt
  17. +31 −31 docs/howto/outputting-pdf.txt
  18. +31 −31 docs/howto/static-files.txt
  19. +142 −142 docs/index.txt
  20. +77 −77 docs/internals/contributing/bugs-and-features.txt
  21. +62 −62 docs/internals/contributing/committing-code.txt
  22. +24 −24 docs/internals/contributing/index.txt
  23. +22 −22 docs/internals/contributing/translations.txt
  24. +121 −117 docs/internals/contributing/triaging-tickets.txt
  25. +35 −35 docs/internals/contributing/writing-code/branch-policy.txt
  26. +104 −104 docs/internals/contributing/writing-code/coding-style.txt
  27. +46 −46 docs/internals/contributing/writing-code/submitting-patches.txt
  28. +27 −27 docs/internals/contributing/writing-code/unit-tests.txt
  29. +130 −130 docs/internals/contributing/writing-documentation.txt
  30. +173 −173 docs/internals/deprecation.txt
  31. +52 −52 docs/internals/release-process.txt
  32. +9 −9 docs/intro/install.txt
  33. +6 −6 docs/intro/overview.txt
  34. +64 −64 docs/intro/tutorial01.txt
  35. +38 −38 docs/intro/tutorial02.txt
  36. +30 −30 docs/intro/tutorial03.txt
  37. +87 −87 docs/intro/tutorial04.txt
  38. +79 −79 docs/intro/whatsnext.txt
  39. +84 −84 docs/misc/api-stability.txt
  40. +2 −2 docs/misc/design-philosophies.txt
  41. +130 −130 docs/ref/class-based-views.txt
  42. +4 −4 docs/ref/contrib/admin/actions.txt
  43. +22 −22 docs/ref/contrib/admin/admindocs.txt
  44. +6 −6 docs/ref/contrib/comments/custom.txt
  45. +40 −40 docs/ref/contrib/comments/index.txt
  46. +42 −42 docs/ref/contrib/comments/signals.txt
  47. +20 −20 docs/ref/contrib/comments/upgrade.txt
  48. +38 −38 docs/ref/contrib/contenttypes.txt
  49. +33 −33 docs/ref/contrib/csrf.txt
  50. +26 −26 docs/ref/contrib/databrowse.txt
  51. +20 −20 docs/ref/contrib/flatpages.txt
  52. +42 −42 docs/ref/contrib/formtools/form-preview.txt
  53. +35 −35 docs/ref/contrib/formtools/form-wizard.txt
  54. +36 −36 docs/ref/contrib/humanize.txt
  55. +4 −4 docs/ref/contrib/markup.txt
  56. +14 −14 docs/ref/contrib/messages.txt
  57. +11 −11 docs/ref/contrib/redirects.txt
  58. +40 −40 docs/ref/contrib/sitemaps.txt
  59. +14 −14 docs/ref/contrib/sites.txt
  60. +10 −10 docs/ref/contrib/staticfiles.txt
  61. +82 −82 docs/ref/contrib/syndication.txt
  62. +15 −15 docs/ref/contrib/webdesign.txt
  63. +55 −55 docs/ref/databases.txt
  64. +81 −81 docs/ref/django-admin.txt
  65. +9 −9 docs/ref/exceptions.txt
  66. +27 −27 docs/ref/forms/api.txt
  67. +230 −229 docs/ref/forms/fields.txt
  68. +66 −66 docs/ref/forms/validation.txt
  69. +57 −74 docs/ref/forms/widgets.txt
  70. +494 −494 docs/ref/generic-views.txt
  71. +32 −32 docs/ref/middleware.txt
  72. +33 −33 docs/ref/models/fields.txt
  73. +41 −41 docs/ref/models/instances.txt
  74. +15 −15 docs/ref/models/options.txt
  75. +15 −15 docs/ref/models/relations.txt
  76. +39 −39 docs/ref/request-response.txt
  77. +27 −27 docs/ref/settings.txt
  78. +39 −46 docs/ref/signals.txt
  79. +6 −6 docs/ref/template-response.txt
  80. +108 −108 docs/ref/templates/api.txt
  81. +141 −141 docs/ref/templates/builtins.txt
  82. +48 −48 docs/ref/unicode.txt
  83. +12 −12 docs/ref/utils.txt
  84. +40 −40 docs/releases/0.95.txt
  85. +41 −41 docs/releases/0.96.txt
  86. +15 −15 docs/releases/1.0-porting-guide.txt
  87. +3 −3 docs/releases/1.1-alpha-1.txt
  88. +30 −30 docs/releases/1.1-beta-1.txt
  89. +3 −3 docs/releases/1.1-rc-1.txt
  90. +6 −6 docs/releases/1.1.4.txt
  91. +27 −27 docs/releases/1.1.txt
  92. +47 −47 docs/releases/1.2-alpha-1.txt
  93. +3 −3 docs/releases/1.2-beta-1.txt
  94. +3 −3 docs/releases/1.2-rc-1.txt
  95. +6 −6 docs/releases/1.2.5.txt
  96. +64 −64 docs/releases/1.2.txt
  97. +18 −18 docs/releases/1.3-alpha-1.txt
  98. +21 −21 docs/releases/1.3-beta-1.txt
  99. +36 −36 docs/releases/1.3.txt
  100. +85 −85 docs/topics/cache.txt
  101. +16 −16 docs/topics/class-based-views.txt
  102. +16 −16 docs/topics/conditional-view-processing.txt
  103. +20 −20 docs/topics/db/managers.txt
  104. +148 −148 docs/topics/db/models.txt
  105. +11 −11 docs/topics/db/optimization.txt
  106. +37 −37 docs/topics/db/queries.txt
  107. +18 −18 docs/topics/db/transactions.txt
  108. +83 −83 docs/topics/email.txt
  109. +34 −34 docs/topics/forms/index.txt
  110. +62 −62 docs/topics/forms/modelforms.txt
  111. +18 −18 docs/topics/generic-views-migration.txt
  112. +16 −16 docs/topics/generic-views.txt
  113. +88 −88 docs/topics/http/file-uploads.txt
  114. +13 −13 docs/topics/http/middleware.txt
  115. +40 −40 docs/topics/http/sessions.txt
  116. +25 −25 docs/topics/http/shortcuts.txt
  117. +88 −88 docs/topics/http/urls.txt
  118. +30 −30 docs/topics/http/views.txt
  119. +83 −83 docs/topics/i18n/deployment.txt
  120. +18 −18 docs/topics/i18n/index.txt
  121. +56 −56 docs/topics/i18n/internationalization.txt
  122. +23 −23 docs/topics/i18n/localization.txt
  123. +10 −10 docs/topics/install.txt
  124. +70 −71 docs/topics/logging.txt
  125. +9 −9 docs/topics/serialization.txt
  126. +10 −10 docs/topics/settings.txt
  127. +14 −14 docs/topics/signals.txt
  128. +6 −6 docs/topics/signing.txt
  129. +159 −159 docs/topics/testing.txt
View
@@ -8,16 +8,16 @@ The login cookie isn't being set correctly, because the domain of the cookie
sent out by Django doesn't match the domain in your browser. Try these two
things:
- * Set the :setting:`SESSION_COOKIE_DOMAIN` setting in your admin config
- file to match your domain. For example, if you're going to
- "http://www.example.com/admin/" in your browser, in
- "myproject.settings" you should set ``SESSION_COOKIE_DOMAIN = 'www.example.com'``.
-
- * Some browsers (Firefox?) don't like to accept cookies from domains that
- don't have dots in them. If you're running the admin site on "localhost"
- or another domain that doesn't have a dot in it, try going to
- "localhost.localdomain" or "127.0.0.1". And set
- :setting:`SESSION_COOKIE_DOMAIN` accordingly.
+* Set the :setting:`SESSION_COOKIE_DOMAIN` setting in your admin config
+ file to match your domain. For example, if you're going to
+ "http://www.example.com/admin/" in your browser, in
+ "myproject.settings" you should set ``SESSION_COOKIE_DOMAIN = 'www.example.com'``.
+
+* Some browsers (Firefox?) don't like to accept cookies from domains that
+ don't have dots in them. If you're running the admin site on "localhost"
+ or another domain that doesn't have a dot in it, try going to
+ "localhost.localdomain" or "127.0.0.1". And set
+ :setting:`SESSION_COOKIE_DOMAIN` accordingly.
I can't log in. When I enter a valid username and password, it brings up the login page again, with a "Please enter a correct username and password" error.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
View
@@ -26,17 +26,17 @@ The best way to make sure tickets do not get hung up on the way to checkin is
to make it dead easy, even for someone who may not be intimately familiar with
that area of the code, to understand the problem and verify the fix:
- * Are there clear instructions on how to reproduce the bug? If this
- touches a dependency (such as PIL), a contrib module, or a specific
- database, are those instructions clear enough even for someone not
- familiar with it?
+* Are there clear instructions on how to reproduce the bug? If this
+ touches a dependency (such as PIL), a contrib module, or a specific
+ database, are those instructions clear enough even for someone not
+ familiar with it?
- * If there are several patches attached to the ticket, is it clear what
- each one does, which ones can be ignored and which matter?
+* If there are several patches attached to the ticket, is it clear what
+ each one does, which ones can be ignored and which matter?
- * Does the patch include a unit test? If not, is there a very clear
- explanation why not? A test expresses succinctly what the problem is,
- and shows that the patch actually fixes it.
+* Does the patch include a unit test? If not, is there a very clear
+ explanation why not? A test expresses succinctly what the problem is,
+ and shows that the patch actually fixes it.
If your patch stands no chance of inclusion in Django, we won't ignore it --
we'll just close the ticket. So if your ticket is still open, it doesn't mean
View
@@ -4,11 +4,11 @@ FAQ: Installation
How do I get started?
---------------------
- #. `Download the code`_.
- #. Install Django (read the :doc:`installation guide </intro/install>`).
- #. Walk through the :doc:`tutorial </intro/tutorial01>`.
- #. Check out the rest of the :doc:`documentation </index>`, and `ask questions`_ if you
- run into trouble.
+#. `Download the code`_.
+#. Install Django (read the :doc:`installation guide </intro/install>`).
+#. Walk through the :doc:`tutorial </intro/tutorial01>`.
+#. Check out the rest of the :doc:`documentation </index>`, and `ask questions`_ if you
+ run into trouble.
.. _`Download the code`: http://www.djangoproject.com/download/
.. _ask questions: http://www.djangoproject.com/community/
View
@@ -6,21 +6,21 @@ Why do I get an error about importing DJANGO_SETTINGS_MODULE?
Make sure that:
- * The environment variable DJANGO_SETTINGS_MODULE is set to a
- fully-qualified Python module (i.e. "mysite.settings").
+* The environment variable DJANGO_SETTINGS_MODULE is set to a
+ fully-qualified Python module (i.e. "mysite.settings").
- * Said module is on ``sys.path`` (``import mysite.settings`` should work).
+* Said module is on ``sys.path`` (``import mysite.settings`` should work).
- * The module doesn't contain syntax errors (of course).
+* The module doesn't contain syntax errors (of course).
- * If you're using mod_python but *not* using Django's request handler,
- you'll need to work around a mod_python bug related to the use of
- ``SetEnv``; before you import anything from Django you'll need to do
- the following::
+* If you're using mod_python but *not* using Django's request handler,
+ you'll need to work around a mod_python bug related to the use of
+ ``SetEnv``; before you import anything from Django you'll need to do
+ the following::
- os.environ.update(req.subprocess_env)
+ os.environ.update(req.subprocess_env)
- (where ``req`` is the mod_python request object).
+ (where ``req`` is the mod_python request object).
I can't stand your template language. Do I have to use it?
----------------------------------------------------------
@@ -46,25 +46,25 @@ How do I use image and file fields?
Using a :class:`~django.db.models.FileField` or an
:class:`~django.db.models.ImageField` in a model takes a few steps:
- #. In your settings file, you'll need to define :setting:`MEDIA_ROOT` as
- the full path to a directory where you'd like Django to store uploaded
- files. (For performance, these files are not stored in the database.)
- Define :setting:`MEDIA_URL` as the base public URL of that directory.
- Make sure that this directory is writable by the Web server's user
- account.
-
- #. Add the :class:`~django.db.models.FileField` or
- :class:`~django.db.models.ImageField` to your model, making sure to
- define the :attr:`~django.db.models.FileField.upload_to` option to tell
- Django to which subdirectory of :setting:`MEDIA_ROOT` it should upload
- files.
-
- #. All that will be stored in your database is a path to the file
- (relative to :setting:`MEDIA_ROOT`). You'll most likely want to use the
- convenience :attr:`~django.core.files.File.url` attribute provided by
- Django. For example, if your :class:`~django.db.models.ImageField` is
- called ``mug_shot``, you can get the absolute path to your image in a
- template with ``{{ object.mug_shot.url }}``.
+#. In your settings file, you'll need to define :setting:`MEDIA_ROOT` as
+ the full path to a directory where you'd like Django to store uploaded
+ files. (For performance, these files are not stored in the database.)
+ Define :setting:`MEDIA_URL` as the base public URL of that directory.
+ Make sure that this directory is writable by the Web server's user
+ account.
+
+#. Add the :class:`~django.db.models.FileField` or
+ :class:`~django.db.models.ImageField` to your model, making sure to
+ define the :attr:`~django.db.models.FileField.upload_to` option to tell
+ Django to which subdirectory of :setting:`MEDIA_ROOT` it should upload
+ files.
+
+#. All that will be stored in your database is a path to the file
+ (relative to :setting:`MEDIA_ROOT`). You'll most likely want to use the
+ convenience :attr:`~django.core.files.File.url` attribute provided by
+ Django. For example, if your :class:`~django.db.models.ImageField` is
+ called ``mug_shot``, you can get the absolute path to your image in a
+ template with ``{{ object.mug_shot.url }}``.
How do I make a variable available to all my templates?
-------------------------------------------------------
View
@@ -14,12 +14,12 @@ dealing with Apache, you can configuring Apache to authenticate against Django's
:doc:`authentication system </topics/auth>` directly. For example, you
could:
- * Serve static/media files directly from Apache only to authenticated users.
+* Serve static/media files directly from Apache only to authenticated users.
- * Authenticate access to a Subversion_ repository against Django users with
- a certain permission.
+* Authenticate access to a Subversion_ repository against Django users with
+ a certain permission.
- * Allow certain users to connect to a WebDAV share created with mod_dav_.
+* Allow certain users to connect to a WebDAV share created with mod_dav_.
.. _Subversion: http://subversion.tigris.org/
.. _mod_dav: http://httpd.apache.org/docs/2.0/mod/mod_dav.html
@@ -93,29 +93,29 @@ By default, the authentication handler will limit access to the ``/example/``
location to users marked as staff members. You can use a set of
``PythonOption`` directives to modify this behavior:
- ================================ =========================================
- ``PythonOption`` Explanation
- ================================ =========================================
- ``DjangoRequireStaffStatus`` If set to ``on`` only "staff" users (i.e.
- those with the ``is_staff`` flag set)
- will be allowed.
+================================ =========================================
+``PythonOption`` Explanation
+================================ =========================================
+``DjangoRequireStaffStatus`` If set to ``on`` only "staff" users (i.e.
+ those with the ``is_staff`` flag set)
+ will be allowed.
- Defaults to ``on``.
+ Defaults to ``on``.
- ``DjangoRequireSuperuserStatus`` If set to ``on`` only superusers (i.e.
- those with the ``is_superuser`` flag set)
- will be allowed.
+``DjangoRequireSuperuserStatus`` If set to ``on`` only superusers (i.e.
+ those with the ``is_superuser`` flag set)
+ will be allowed.
- Defaults to ``off``.
+ Defaults to ``off``.
- ``DjangoPermissionName`` The name of a permission to require for
- access. See :ref:`custom permissions
- <custom-permissions>` for more
- information.
+``DjangoPermissionName`` The name of a permission to require for
+ access. See :ref:`custom permissions
+ <custom-permissions>` for more
+ information.
- By default no specific permission will be
- required.
- ================================ =========================================
+ By default no specific permission will be
+ required.
+================================ =========================================
Note that sometimes ``SetEnv`` doesn't play well in this mod_python
configuration, for reasons unknown. If you're having problems getting
@@ -37,11 +37,11 @@ You'll need to follow these steps:
Your custom storage system may override any of the storage methods explained in
:doc:`/ref/files/storage`, but you **must** implement the following methods:
- * :meth:`Storage.delete`
- * :meth:`Storage.exists`
- * :meth:`Storage.listdir`
- * :meth:`Storage.size`
- * :meth:`Storage.url`
+* :meth:`Storage.delete`
+* :meth:`Storage.exists`
+* :meth:`Storage.listdir`
+* :meth:`Storage.size`
+* :meth:`Storage.url`
You'll also usually want to use hooks specifically designed for custom storage
objects. These are:
Oops, something went wrong.

0 comments on commit d1e5c55

Please sign in to comment.