summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorJannis Leidel <jannis@leidel.info>2012-07-08 12:57:04 +0200
committerJannis Leidel <jannis@leidel.info>2012-07-08 12:57:04 +0200
commiteffc2cad95dbf96ee6fd0ac3fd2da18948135d49 (patch)
tree466ab44277bc612864dc3f74f7245f5c7ad6ec5e /docs/ref
parent3727f6d09681e4cb23d67e14ecc677a364c991bd (diff)
parent5e94ef293cb1cfe4dc43cbd5509653c0e0bf66cf (diff)
Merge branch 'master' of github.com:django/django
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/contrib/gis/install.txt11
-rw-r--r--docs/ref/django-admin.txt3
-rw-r--r--docs/ref/forms/fields.txt6
-rw-r--r--docs/ref/models/querysets.txt16
4 files changed, 7 insertions, 29 deletions
diff --git a/docs/ref/contrib/gis/install.txt b/docs/ref/contrib/gis/install.txt
index 00f8f8a370..805772fa88 100644
--- a/docs/ref/contrib/gis/install.txt
+++ b/docs/ref/contrib/gis/install.txt
@@ -838,17 +838,6 @@ your ``.profile`` to be able to run the package programs from the command-line::
__ http://www.kyngchaos.com/software/frameworks
__ http://www.kyngchaos.com/software/postgres
-.. note::
-
- Use of these binaries requires Django 1.0.3 and above. If you are
- using a previous version of Django (like 1.0.2), then you will have
- to add the following in your settings:
-
- .. code-block:: python
-
- GEOS_LIBRARY_PATH='/Library/Frameworks/GEOS.framework/GEOS'
- GDAL_LIBRARY_PATH='/Library/Frameworks/GDAL.framework/GDAL'
-
.. _psycopg2_kyngchaos:
psycopg2
diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
index 7ca1ee5ddd..31c46c7fa0 100644
--- a/docs/ref/django-admin.txt
+++ b/docs/ref/django-admin.txt
@@ -888,7 +888,8 @@ through the template engine: the files whose extensions match the
with the ``--name`` option. The :class:`template context
<django.template.Context>` used is:
-- Any option passed to the startapp command
+- Any option passed to the startapp command (among the command's supported
+ options)
- ``app_name`` -- the app name as passed to the command
- ``app_directory`` -- the full path of the newly created app
diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt
index 486d49d796..082ec17a35 100644
--- a/docs/ref/forms/fields.txt
+++ b/docs/ref/forms/fields.txt
@@ -591,7 +591,11 @@ For each field, we describe the default widget used if you don't specify
* Error message keys: ``required``, ``invalid``, ``missing``, ``empty``,
``invalid_image``
- Using an ImageField requires that the `Python Imaging Library`_ is installed.
+ Using an ``ImageField`` requires that the `Python Imaging Library`_ (PIL)
+ is installed and supports the image formats you use. If you encounter a
+ ``corrupt image`` error when you upload an image, it usually means PIL
+ doesn't understand its format. To fix this, install the appropriate
+ library and reinstall PIL.
When you use an ``ImageField`` on a form, you must also remember to
:ref:`bind the file data to the form <binding-uploaded-files>`.
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 2876f1474d..0a9005ad26 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -1768,22 +1768,6 @@ This queryset will be evaluated as subselect statement::
SELECT ... WHERE blog.id IN (SELECT id FROM ... WHERE NAME LIKE '%Cheddar%')
-The above code fragment could also be written as follows::
-
- inner_q = Blog.objects.filter(name__contains='Cheddar').values('pk').query
- entries = Entry.objects.filter(blog__in=inner_q)
-
-.. warning::
-
- This ``query`` attribute should be considered an opaque internal attribute.
- It's fine to use it like above, but its API may change between Django
- versions.
-
-This second form is a bit less readable and unnatural to write, since it
-accesses the internal ``query`` attribute and requires a ``ValuesQuerySet``.
-If your code doesn't require compatibility with Django 1.0, use the first
-form, passing in a queryset directly.
-
If you pass in a ``ValuesQuerySet`` or ``ValuesListQuerySet`` (the result of
calling ``values()`` or ``values_list()`` on a queryset) as the value to an
``__in`` lookup, you need to ensure you are only extracting one field in the