Permalink
Browse files

[1.2.X] Fixed #14000 - Remove versionadded/changed tags for 1.0. than…

…ks ramiro!

git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@15056 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 40f2bb3 commit 89cb543f9e4f823fe53140c3b597e2d4b6418562 @timgraham timgraham committed Dec 26, 2010
Showing with 32 additions and 374 deletions.
  1. +0 −2 docs/howto/custom-management-commands.txt
  2. +0 −1 docs/howto/custom-model-fields.txt
  3. +0 −8 docs/howto/custom-template-tags.txt
  4. +0 −3 docs/howto/deployment/modpython.txt
  5. +8 −10 docs/ref/contrib/flatpages.txt
  6. +0 −2 docs/ref/contrib/formtools/form-wizard.txt
  7. +0 −2 docs/ref/contrib/gis/index.txt
  8. +0 −2 docs/ref/contrib/humanize.txt
  9. +0 −4 docs/ref/contrib/index.txt
  10. +0 −2 docs/ref/contrib/sitemaps.txt
  11. +0 −4 docs/ref/contrib/sites.txt
  12. +0 −2 docs/ref/databases.txt
  13. +0 −14 docs/ref/django-admin.txt
  14. +0 −5 docs/ref/forms/api.txt
  15. +0 −18 docs/ref/forms/fields.txt
  16. +0 −2 docs/ref/forms/widgets.txt
  17. +0 −12 docs/ref/generic-views.txt
  18. +0 −7 docs/ref/middleware.txt
  19. +0 −21 docs/ref/models/fields.txt
  20. +0 −7 docs/ref/models/instances.txt
  21. +0 −4 docs/ref/models/options.txt
  22. +0 −37 docs/ref/models/querysets.txt
  23. +1 −11 docs/ref/request-response.txt
  24. +0 −30 docs/ref/settings.txt
  25. +0 −2 docs/ref/templates/api.txt
  26. +5 −29 docs/ref/templates/builtins.txt
  27. +0 −2 docs/ref/unicode.txt
  28. +0 −13 docs/topics/auth.txt
  29. +0 −12 docs/topics/cache.txt
  30. +0 −8 docs/topics/db/models.txt
  31. +0 −4 docs/topics/db/queries.txt
  32. +0 −2 docs/topics/email.txt
  33. +0 −2 docs/topics/files.txt
  34. +0 −3 docs/topics/forms/index.txt
  35. +0 −5 docs/topics/forms/modelforms.txt
  36. +0 −2 docs/topics/http/file-uploads.txt
  37. +0 −25 docs/topics/http/sessions.txt
  38. +16 −22 docs/topics/http/urls.txt
  39. +2 −6 docs/topics/i18n/deployment.txt
  40. +0 −3 docs/topics/pagination.txt
  41. +0 −2 docs/topics/templates.txt
  42. +0 −22 docs/topics/testing.txt
@@ -2,8 +2,6 @@
Writing custom django-admin commands
====================================
-.. versionadded:: 1.0
-
Applications can register their own actions with ``manage.py``. For example,
you might want to add a ``manage.py`` action for a Django app that you're
distributing. In this document, we will be building a custom ``closepoll``
@@ -2,7 +2,6 @@
Writing custom model fields
===========================
-.. versionadded:: 1.0
.. currentmodule:: django.db.models
Introduction
@@ -155,8 +155,6 @@ will use the function's name as the filter name.
Filters and auto-escaping
~~~~~~~~~~~~~~~~~~~~~~~~~
-.. versionadded:: 1.0
-
When writing a custom filter, give some thought to how the filter will interact
with Django's auto-escaping behavior. Note that three types of strings can be
passed around inside the template code:
@@ -426,8 +424,6 @@ without having to be parsed multiple times.
Auto-escaping considerations
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-.. versionadded:: 1.0
-
The output from template tags is **not** automatically run through the
auto-escaping filters. However, there are still a couple of things you should
keep in mind when writing a template tag.
@@ -605,10 +601,6 @@ Now your tag should begin to look like this::
raise template.TemplateSyntaxError, "%r tag's argument should be in quotes" % tag_name
return FormatTimeNode(date_to_be_formatted, format_string[1:-1])
-.. versionchanged:: 1.0
- Variable resolution has changed in the 1.0 release of Django. ``template.resolve_variable()``
- has been deprecated in favor of a new ``template.Variable`` class.
-
You also have to change the renderer to retrieve the actual contents of the
``date_updated`` property of the ``blog_entry`` object. This can be
accomplished by using the ``Variable()`` class in ``django.template``.
@@ -65,9 +65,6 @@ This tells Apache: "Use mod_python for any URL at or under '/mysite/', using the
Django mod_python handler." It passes the value of :ref:`DJANGO_SETTINGS_MODULE
<django-settings-module>` so mod_python knows which settings to use.
-.. versionadded:: 1.0
- The ``PythonOption django.root ...`` is new in this version.
-
Because mod_python does not know we are serving this site from underneath the
``/mysite/`` prefix, this value needs to be passed through to the mod_python
handler in Django, via the ``PythonOption django.root ...`` line. The value set
@@ -17,9 +17,7 @@ custom Django application.
A flatpage can use a custom template or a default, systemwide flatpage
template. It can be associated with one, or multiple, sites.
-.. versionadded:: 1.0
-
-The content field may optionally be left blank if you prefer to put your
+The content field may optionally be left blank if you prefer to put your
content in a custom template.
Here are some examples of flatpages on Django-powered sites:
@@ -35,20 +33,20 @@ To install the flatpages app, follow these steps:
1. Install the :mod:`sites framework <django.contrib.sites>` by adding
``'django.contrib.sites'`` to your :setting:`INSTALLED_APPS` setting,
if it's not already in there.
-
+
Also make sure you've correctly set :setting:`SITE_ID` to the ID of the
site the settings file represents. This will usually be ``1`` (i.e.
``SITE_ID = 1``, but if you're using the sites framework to manage
multiple sites, it could be the ID of a different site.
-
+
2. Add ``'django.contrib.flatpages'`` to your :setting:`INSTALLED_APPS`
setting.
-
+
3. Add ``'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware'``
to your :setting:`MIDDLEWARE_CLASSES` setting.
-
+
4. Run the command :djadmin:`manage.py syncdb <syncdb>`.
-
+
How it works
============
@@ -67,7 +65,7 @@ If it finds a match, it follows this algorithm:
* If the flatpage has a custom template, it loads that template. Otherwise,
it loads the template :file:`flatpages/default.html`.
-
+
* It passes that template a single context variable, :data:`flatpage`, which
is the flatpage object. It uses
:class:`~django.template.context.RequestContext` in rendering the
@@ -94,7 +92,7 @@ For more on middleware, read the :doc:`middleware docs
</topics/http/middleware>`.
.. admonition:: Ensure that your 404 template works
-
+
Note that the
:class:`~django.contrib.flatpages.middleware.FlatpageFallbackMiddleware`
only steps in once another view has successfully produced a 404 response.
@@ -5,8 +5,6 @@ Form wizard
.. module:: django.contrib.formtools.wizard
:synopsis: Splits forms across multiple Web pages.
-.. versionadded:: 1.0
-
Django comes with an optional "form wizard" application that splits
:doc:`forms </topics/forms/index>` across multiple Web pages. It maintains
state in hashed HTML :samp:`<input type="hidden">` fields, and the data isn't
@@ -4,8 +4,6 @@
GeoDjango
=========
-.. versionadded:: 1.0
-
.. module:: django.contrib.gis
:synopsis: Geographic Information System (GIS) extensions for Django
@@ -68,8 +68,6 @@ You can pass in either an integer or a string representation of an integer.
naturalday
----------
-.. versionadded:: 1.0
-
For dates that are the current day or within one day, return "today",
"tomorrow" or "yesterday", as appropriate. Otherwise, format the date using
the passed in format string.
@@ -60,10 +60,6 @@ See :doc:`/topics/auth`.
comments
========
-.. versionchanged:: 1.0
- The comments application has been rewriten. See :doc:`/ref/contrib/comments/upgrade`
- for information on howto upgrade.
-
A simple yet flexible comments system. See :doc:`/ref/contrib/comments/index`.
contenttypes
@@ -343,8 +343,6 @@ Pinging Google via `manage.py`
.. django-admin:: ping_google
-.. versionadded:: 1.0
-
Once the sitemaps application is added to your project, you may also
ping Google using the ``ping_google`` management command::
@@ -238,8 +238,6 @@ To do this, you can use the sites framework. A simple example::
Caching the current ``Site`` object
===================================
-.. versionadded:: 1.0
-
As the current site is stored in the database, each call to
``Site.objects.get_current()`` could result in a database query. But Django is a
little cleverer than that: on the first request, the current site is cached, and
@@ -393,8 +391,6 @@ Here's how Django uses the sites framework:
.. _requestsite-objects:
-.. versionadded:: 1.0
-
Some :doc:`django.contrib </ref/contrib/index>` applications take advantage of
the sites framework but are architected in a way that doesn't *require* the
sites framework to be installed in your database. (Some people don't want to, or
@@ -601,8 +601,6 @@ many-to-many table would be stored in the ``indexes`` tablespace. The ``data``
field would also generate an index, but no tablespace for it is specified, so
it would be stored in the model tablespace ``tables`` by default.
-.. versionadded:: 1.0
-
Use the :setting:`DEFAULT_TABLESPACE` and :setting:`DEFAULT_INDEX_TABLESPACE`
settings to specify default values for the db_tablespace options.
These are useful for setting a tablespace for the built-in Django apps and
@@ -88,8 +88,6 @@ cleanup
.. django-admin:: cleanup
-.. versionadded:: 1.0
-
Can be run as a cronjob or directly to clean out old data from the database
(only expired sessions at the moment).
@@ -98,9 +96,6 @@ compilemessages
.. django-admin:: compilemessages
-.. versionchanged:: 1.0
- Before 1.0 this was the "bin/compile-messages.py" command.
-
Compiles .po files created with ``makemessages`` to .mo files for use with
the builtin gettext support. See :doc:`/topics/i18n/index`.
@@ -191,8 +186,6 @@ By default, ``dumpdata`` will output all data on a single line. This isn't
easy for humans to read, so you can use the ``--indent`` option to
pretty-print the output with a number of indentation spaces.
-.. versionadded:: 1.0
-
The :djadminopt:`--exclude` option may be provided to prevent specific
applications from being dumped.
@@ -396,9 +389,6 @@ makemessages
.. django-admin:: makemessages
-.. versionchanged:: 1.0
- Before 1.0 this was the ``bin/make-messages.py`` command.
-
Runs over the entire source tree of the current directory and pulls out all
strings marked for translation. It creates (or updates) a message file in the
conf/locale (in the django tree) or locale (for project and application)
@@ -910,8 +900,6 @@ testserver <fixture fixture ...>
.. django-admin:: testserver
-.. versionadded:: 1.0
-
Runs a Django development server (as in ``runserver``) using data from the
given fixture(s).
@@ -1009,8 +997,6 @@ createsuperuser
.. django-admin:: createsuperuser
-.. versionadded:: 1.0
-
This command is only available if Django's :doc:`authentication system
</topics/auth>` (``django.contrib.auth``) is installed.
@@ -195,9 +195,6 @@ it, you can access the clean data via its ``cleaned_data`` attribute::
>>> f.cleaned_data
{'cc_myself': True, 'message': u'Hi there', 'sender': u'foo@example.com', 'subject': u'hello'}
-.. versionchanged:: 1.0
- The ``cleaned_data`` attribute was called ``clean_data`` in earlier releases.
-
Note that any text-based field -- such as ``CharField`` or ``EmailField`` --
always cleans the input into a Unicode string. We'll cover the encoding
implications later in this document.
@@ -667,8 +664,6 @@ those classes as an argument::
Binding uploaded files to a form
--------------------------------
-.. versionadded:: 1.0
-
Dealing with forms that have ``FileField`` and ``ImageField`` fields
is a little more complicated than a normal form.
@@ -230,8 +230,6 @@ fields. We've specified ``auto_id=False`` to simplify the output::
``error_messages``
~~~~~~~~~~~~~~~~~~
-.. versionadded:: 1.0
-
.. attribute:: Field.error_messages
The ``error_messages`` argument lets you override the default messages that the
@@ -303,11 +301,6 @@ For each field, we describe the default widget used if you don't specify
the field has ``required=True``.
* Error message keys: ``required``
-.. versionchanged:: 1.0
- The empty value for a ``CheckboxInput`` (and hence the standard
- ``BooleanField``) has changed to return ``False`` instead of ``None`` in
- the Django 1.0.
-
.. note::
Since all ``Field`` subclasses have ``required=True`` by default, the
@@ -445,14 +438,9 @@ If no ``input_formats`` argument is provided, the default input formats are::
'%m/%d/%y %H:%M', # '10/25/06 14:30'
'%m/%d/%y', # '10/25/06'
-.. versionchanged:: 1.0
- The ``DateTimeField`` used to use a ``TextInput`` widget by default. This has now changed.
-
``DecimalField``
~~~~~~~~~~~~~~~~
-.. versionadded:: 1.0
-
.. class:: DecimalField(**kwargs)
* Default widget: ``TextInput``
@@ -505,8 +493,6 @@ given length.
``FileField``
~~~~~~~~~~~~~
-.. versionadded:: 1.0
-
.. class:: FileField(**kwargs)
* Default widget: ``FileInput``
@@ -525,8 +511,6 @@ When you use a ``FileField`` in a form, you must also remember to
``FilePathField``
~~~~~~~~~~~~~~~~~
-.. versionadded:: 1.0
-
.. class:: FilePathField(**kwargs)
* Default widget: ``Select``
@@ -571,8 +555,6 @@ These control the range of values permitted in the field.
``ImageField``
~~~~~~~~~~~~~~
-.. versionadded:: 1.0
-
.. class:: ImageField(**kwargs)
* Default widget: ``FileInput``
@@ -57,8 +57,6 @@ commonly used groups of widgets:
.. class:: DateTimeInput
- .. versionadded:: 1.0
-
Date/time input as a simple text box: ``<input type='text' ...>``
Takes one optional argument:
@@ -176,8 +176,6 @@ a date in the *future* are not included unless you set ``allow_future`` to
specified in ``date_field`` is greater than the current date/time. By
default, this is ``False``.
- .. versionadded:: 1.0
-
* ``template_object_name``: Designates the name of the template variable
to use in the template context. By default, this is ``'latest'``.
@@ -202,9 +200,6 @@ In addition to ``extra_context``, the template's context will be:
``datetime.datetime`` objects. These are ordered in reverse. This is
equivalent to ``queryset.dates(date_field, 'year')[::-1]``.
- .. versionchanged:: 1.0
- The behaviour depending on ``template_object_name`` is new in this version.
-
* ``latest``: The ``num_latest`` objects in the system, ordered descending
by ``date_field``. For example, if ``num_latest`` is ``10``, then
``latest`` will be a list of the latest 10 objects in ``queryset``.
@@ -721,9 +716,6 @@ If ``template_name`` isn't specified, this view will use the template
**Template context:**
-.. versionadded:: 1.0
- The ``paginator`` and ``page_obj`` context variables are new.
-
In addition to ``extra_context``, the template's context will be:
* ``object_list``: The list of objects. This variable's name depends on the
@@ -767,8 +759,6 @@ represented as page ``1``.
For more on pagination, read the :doc:`pagination documentation
</topics/pagination>`.
-.. versionadded:: 1.0
-
As a special case, you are also permitted to use ``last`` as a value for
``page``::
@@ -853,8 +843,6 @@ Create/update/delete generic views
The ``django.views.generic.create_update`` module contains a set of functions
for creating, editing and deleting objects.
-.. versionchanged:: 1.0
-
``django.views.generic.create_update.create_object`` and
``django.views.generic.create_update.update_object`` now use the new :doc:`forms
library </topics/forms/index>` to build and display the form.
@@ -52,11 +52,6 @@ Adds a few conveniences for perfectionists:
you don't have a valid URL pattern for ``foo.com/bar`` but *do* have a
valid pattern for ``foo.com/bar/``.
- .. versionchanged:: 1.0
- The behavior of :setting:`APPEND_SLASH` has changed slightly in this
- version. It didn't used to check whether the pattern was matched in
- the URLconf.
-
If :setting:`PREPEND_WWW` is ``True``, URLs that lack a leading "www."
will be redirected to the same URL with a leading "www."
@@ -186,8 +181,6 @@ CSRF protection middleware
.. class:: CsrfMiddleware
-.. versionadded:: 1.0
-
Adds protection against Cross Site Request Forgeries by adding hidden form
fields to POST forms and checking requests for the correct value. See the
:doc:`Cross Site Request Forgery protection documentation </ref/contrib/csrf>`.
Oops, something went wrong. Retry.

0 comments on commit 89cb543

Please sign in to comment.