Ticket #14000: 14000-remove-versionxxx-1.0-1.2.x-branch.diff

File 14000-remove-versionxxx-1.0-1.2.x-branch.diff, 50.5 KB (added by Ramiro Morales, 14 years ago)

Removes ".. version*:: 1.0" stuff -- for 1.2.X branch@ r13763

  • docs/howto/custom-management-commands.txt

    diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt
    a b  
    22Writing custom django-admin commands
    33====================================
    44
    5 .. versionadded:: 1.0
    6 
    75Applications can register their own actions with ``manage.py``. For example,
    86you might want to add a ``manage.py`` action for a Django app that you're
    97distributing. In this document, we will be building a custom ``closepoll``
  • docs/howto/custom-model-fields.txt

    diff --git a/docs/howto/custom-model-fields.txt b/docs/howto/custom-model-fields.txt
    a b  
    22Writing custom model fields
    33===========================
    44
    5 .. versionadded:: 1.0
    65.. currentmodule:: django.db.models
    76
    87Introduction
  • docs/howto/custom-template-tags.txt

    diff --git a/docs/howto/custom-template-tags.txt b/docs/howto/custom-template-tags.txt
    a b  
    155155Filters and auto-escaping
    156156~~~~~~~~~~~~~~~~~~~~~~~~~
    157157
    158 .. versionadded:: 1.0
    159 
    160158When writing a custom filter, give some thought to how the filter will interact
    161159with Django's auto-escaping behavior. Note that three types of strings can be
    162160passed around inside the template code:
     
    426424Auto-escaping considerations
    427425~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    428426
    429 .. versionadded:: 1.0
    430 
    431427The output from template tags is **not** automatically run through the
    432428auto-escaping filters. However, there are still a couple of things you should
    433429keep in mind when writing a template tag.
     
    605601            raise template.TemplateSyntaxError, "%r tag's argument should be in quotes" % tag_name
    606602        return FormatTimeNode(date_to_be_formatted, format_string[1:-1])
    607603
    608 .. versionchanged:: 1.0
    609     Variable resolution has changed in the 1.0 release of Django. ``template.resolve_variable()``
    610     has been deprecated in favor of a new ``template.Variable`` class.
    611 
    612604You also have to change the renderer to retrieve the actual contents of the
    613605``date_updated`` property of the ``blog_entry`` object.  This can be
    614606accomplished by using the ``Variable()`` class in ``django.template``.
  • docs/howto/deployment/modpython.txt

    diff --git a/docs/howto/deployment/modpython.txt b/docs/howto/deployment/modpython.txt
    a b  
    5656Django mod_python handler." It passes the value of :ref:`DJANGO_SETTINGS_MODULE
    5757<django-settings-module>` so mod_python knows which settings to use.
    5858
    59 .. versionadded:: 1.0
    60     The ``PythonOption django.root ...`` is new in this version.
    61 
    6259Because mod_python does not know we are serving this site from underneath the
    6360``/mysite/`` prefix, this value needs to be passed through to the mod_python
    6461handler in Django, via the ``PythonOption django.root ...`` line. The value set
  • docs/ref/contrib/flatpages.txt

    diff --git a/docs/ref/contrib/flatpages.txt b/docs/ref/contrib/flatpages.txt
    a b  
    1717A flatpage can use a custom template or a default, systemwide flatpage
    1818template. It can be associated with one, or multiple, sites.
    1919
    20 .. versionadded:: 1.0
    21 
    22 The content field may optionally be left blank if you prefer to put your
     20The content field may optionally be left blank if you prefer to put your
    2321content in a custom template.
    2422
    2523Here are some examples of flatpages on Django-powered sites:
     
    3533    1. Install the :mod:`sites framework <django.contrib.sites>` by adding
    3634       ``'django.contrib.sites'`` to your :setting:`INSTALLED_APPS` setting,
    3735       if it's not already in there.
    38        
     36
    3937       Also make sure you've correctly set :setting:`SITE_ID` to the ID of the
    4038       site the settings file represents. This will usually be ``1`` (i.e.
    4139       ``SITE_ID = 1``, but if you're using the sites framework to manage
    4240       multiple sites, it could be the ID of a different site.
    43        
     41
    4442    2. Add ``'django.contrib.flatpages'`` to your :setting:`INSTALLED_APPS`
    4543       setting.
    46        
     44
    4745    3. Add ``'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware'``
    4846       to your :setting:`MIDDLEWARE_CLASSES` setting.
    49        
     47
    5048    4. Run the command :djadmin:`manage.py syncdb <syncdb>`.
    51  
     49
    5250How it works
    5351============
    5452
     
    6765
    6866    * If the flatpage has a custom template, it loads that template. Otherwise,
    6967      it loads the template :file:`flatpages/default.html`.
    70    
     68
    7169    * It passes that template a single context variable, :data:`flatpage`, which
    7270      is the flatpage object. It uses
    7371      :class:`~django.template.context.RequestContext` in rendering the
     
    9492</topics/http/middleware>`.
    9593
    9694.. admonition:: Ensure that your 404 template works
    97    
     95
    9896    Note that the
    9997    :class:`~django.contrib.flatpages.middleware.FlatpageFallbackMiddleware`
    10098    only steps in once another view has successfully produced a 404 response.
  • docs/ref/contrib/formtools/form-wizard.txt

    diff --git a/docs/ref/contrib/formtools/form-wizard.txt b/docs/ref/contrib/formtools/form-wizard.txt
    a b  
    55.. module:: django.contrib.formtools.wizard
    66    :synopsis: Splits forms across multiple Web pages.
    77
    8 .. versionadded:: 1.0
    9 
    108Django comes with an optional "form wizard" application that splits
    119:doc:`forms </topics/forms/index>` across multiple Web pages. It maintains
    1210state in hashed HTML :samp:`<input type="hidden">` fields, and the data isn't
  • docs/ref/contrib/gis/index.txt

    diff --git a/docs/ref/contrib/gis/index.txt b/docs/ref/contrib/gis/index.txt
    a b  
    44GeoDjango
    55=========
    66
    7 .. versionadded:: 1.0
    8 
    97.. module:: django.contrib.gis
    108   :synopsis: Geographic Information System (GIS) extensions for Django
    119
  • docs/ref/contrib/humanize.txt

    diff --git a/docs/ref/contrib/humanize.txt b/docs/ref/contrib/humanize.txt
    a b  
    7272naturalday
    7373----------
    7474
    75 .. versionadded:: 1.0
    76 
    7775For dates that are the current day or within one day, return "today",
    7876"tomorrow" or "yesterday", as appropriate. Otherwise, format the date using
    7977the passed in format string.
  • docs/ref/contrib/index.txt

    diff --git a/docs/ref/contrib/index.txt b/docs/ref/contrib/index.txt
    a b  
    6060comments
    6161========
    6262
    63 .. versionchanged:: 1.0
    64    The comments application has been rewriten. See :doc:`/ref/contrib/comments/upgrade`
    65    for information on howto upgrade.
    66 
    6763A simple yet flexible comments system. See :doc:`/ref/contrib/comments/index`.
    6864
    6965contenttypes
  • docs/ref/contrib/sitemaps.txt

    diff --git a/docs/ref/contrib/sitemaps.txt b/docs/ref/contrib/sitemaps.txt
    a b  
    340340Pinging Google via `manage.py`
    341341------------------------------
    342342
    343 .. versionadded:: 1.0
    344 
    345343Once the sitemaps application is added to your project, you may also
    346344ping the Google server's through the command line manage.py interface::
    347345
  • docs/ref/contrib/sites.txt

    diff --git a/docs/ref/contrib/sites.txt b/docs/ref/contrib/sites.txt
    a b  
    228228Caching the current ``Site`` object
    229229===================================
    230230
    231 .. versionadded:: 1.0
    232 
    233231As the current site is stored in the database, each call to
    234232``Site.objects.get_current()`` could result in a database query. But Django is a
    235233little cleverer than that: on the first request, the current site is cached, and
     
    383381
    384382.. _requestsite-objects:
    385383
    386 .. versionadded:: 1.0
    387 
    388384Some :doc:`django.contrib </ref/contrib/index>` applications take advantage of
    389385the sites framework but are architected in a way that doesn't *require* the
    390386sites framework to be installed in your database. (Some people don't want to, or
  • docs/ref/databases.txt

    diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
    a b  
    586586field would also generate an index, but no tablespace for it is specified, so
    587587it would be stored in the model tablespace ``tables`` by default.
    588588
    589 .. versionadded:: 1.0
    590 
    591589Use the :setting:`DEFAULT_TABLESPACE` and :setting:`DEFAULT_INDEX_TABLESPACE`
    592590settings to specify default values for the db_tablespace options.
    593591These are useful for setting a tablespace for the built-in Django apps and
  • docs/ref/django-admin.txt

    diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt
    a b  
    8888
    8989.. django-admin:: cleanup
    9090
    91 .. versionadded:: 1.0
    92 
    9391Can be run as a cronjob or directly to clean out old data from the database
    9492(only expired sessions at the moment).
    9593
     
    9896
    9997.. django-admin:: compilemessages
    10098
    101 .. versionchanged:: 1.0
    102    Before 1.0 this was the "bin/compile-messages.py" command.
    103 
    10499Compiles .po files created with ``makemessages`` to .mo files for use with
    105100the builtin gettext support. See :doc:`/topics/i18n/index`.
    106101
     
    129124
    130125.. django-admin:: createsuperuser
    131126
    132 .. versionadded:: 1.0
    133 
    134127Creates a superuser account (a user who has all permissions). This is
    135128useful if you need to create an initial superuser account but did not
    136129do so during ``syncdb``, or if you need to programmatically generate
     
    220213easy for humans to read, so you can use the ``--indent`` option to
    221214pretty-print the output with a number of indentation spaces.
    222215
    223 .. versionadded:: 1.0
    224 
    225216The :djadminopt:`--exclude` option may be provided to prevent specific
    226217applications from being dumped.
    227218
     
    426417
    427418.. django-admin:: makemessages
    428419
    429 .. versionchanged:: 1.0
    430    Before 1.0 this was the ``bin/make-messages.py`` command.
    431 
    432420Runs over the entire source tree of the current directory and pulls out all
    433421strings marked for translation. It creates (or updates) a message file in the
    434422conf/locale (in the django tree) or locale (for project and application)
     
    831819
    832820.. django-admin:: testserver
    833821
    834 .. versionadded:: 1.0
    835 
    836822Runs a Django development server (as in ``runserver``) using data from the
    837823given fixture(s).
    838824
  • docs/ref/forms/api.txt

    diff --git a/docs/ref/forms/api.txt b/docs/ref/forms/api.txt
    a b  
    195195    >>> f.cleaned_data
    196196    {'cc_myself': True, 'message': u'Hi there', 'sender': u'foo@example.com', 'subject': u'hello'}
    197197
    198 .. versionchanged:: 1.0
    199     The ``cleaned_data`` attribute was called ``clean_data`` in earlier releases.
    200 
    201198Note that any text-based field -- such as ``CharField`` or ``EmailField`` --
    202199always cleans the input into a Unicode string. We'll cover the encoding
    203200implications later in this document.
     
    667664Binding uploaded files to a form
    668665--------------------------------
    669666
    670 .. versionadded:: 1.0
    671 
    672667Dealing with forms that have ``FileField`` and ``ImageField`` fields
    673668is a little more complicated than a normal form.
    674669
  • docs/ref/forms/fields.txt

    diff --git a/docs/ref/forms/fields.txt b/docs/ref/forms/fields.txt
    a b  
    230230``error_messages``
    231231~~~~~~~~~~~~~~~~~~
    232232
    233 .. versionadded:: 1.0
    234 
    235233.. attribute:: Field.error_messages
    236234
    237235The ``error_messages`` argument lets you override the default messages that the
     
    303301      the field has ``required=True``.
    304302    * Error message keys: ``required``
    305303
    306 .. versionchanged:: 1.0
    307    The empty value for a ``CheckboxInput`` (and hence the standard
    308    ``BooleanField``) has changed to return ``False`` instead of ``None`` in
    309    the Django 1.0.
    310 
    311304.. note::
    312305
    313306    Since all ``Field`` subclasses have ``required=True`` by default, the
     
    443436    '%m/%d/%y %H:%M',        # '10/25/06 14:30'
    444437    '%m/%d/%y',              # '10/25/06'
    445438
    446 .. versionchanged:: 1.0
    447    The ``DateTimeField`` used to use a ``TextInput`` widget by default. This has now changed.
    448 
    449439``DecimalField``
    450440~~~~~~~~~~~~~~~~
    451441
    452 .. versionadded:: 1.0
    453 
    454442.. class:: DecimalField(**kwargs)
    455443
    456444    * Default widget: ``TextInput``
     
    503491``FileField``
    504492~~~~~~~~~~~~~
    505493
    506 .. versionadded:: 1.0
    507 
    508494.. class:: FileField(**kwargs)
    509495
    510496    * Default widget: ``FileInput``
     
    523509``FilePathField``
    524510~~~~~~~~~~~~~~~~~
    525511
    526 .. versionadded:: 1.0
    527 
    528512.. class:: FilePathField(**kwargs)
    529513
    530514    * Default widget: ``Select``
     
    569553``ImageField``
    570554~~~~~~~~~~~~~~
    571555
    572 .. versionadded:: 1.0
    573 
    574556.. class:: ImageField(**kwargs)
    575557
    576558    * Default widget: ``FileInput``
  • docs/ref/forms/widgets.txt

    diff --git a/docs/ref/forms/widgets.txt b/docs/ref/forms/widgets.txt
    a b  
    5757
    5858.. class:: DateTimeInput
    5959
    60     .. versionadded:: 1.0
    61 
    6260    Date/time input as a simple text box: ``<input type='text' ...>``
    6361
    6462    Takes one optional argument:
  • docs/ref/generic-views.txt

    diff --git a/docs/ref/generic-views.txt b/docs/ref/generic-views.txt
    a b  
    176176      specified in ``date_field`` is greater than the current date/time. By
    177177      default, this is ``False``.
    178178
    179     .. versionadded:: 1.0
    180 
    181179    * ``template_object_name``: Designates the name of the template variable
    182180      to use in the template context. By default, this is ``'latest'``.
    183181
     
    202200      ordered in reverse. This is equivalent to
    203201      ``queryset.dates(date_field, 'year')[::-1]``.
    204202
    205     .. versionchanged:: 1.0
    206        The behaviour depending on ``template_object_name`` is new in this version.
    207 
    208203    * ``latest``: The ``num_latest`` objects in the system, ordered descending
    209204      by ``date_field``. For example, if ``num_latest`` is ``10``, then
    210205      ``latest`` will be a list of the latest 10 objects in ``queryset``.
     
    374369
    375370    * ``date_list``: A list of ``datetime.date`` objects representing all
    376371      days that have objects available in the given month, according to
    377       ``queryset``, in ascending order.   
     372      ``queryset``, in ascending order.
    378373
    379374    * ``month``: A ``datetime.date`` object representing the given month.
    380375
     
    721716
    722717**Template context:**
    723718
    724 .. versionadded:: 1.0
    725    The ``paginator`` and ``page_obj`` context variables are new.
    726 
    727719In addition to ``extra_context``, the template's context will be:
    728720
    729721    * ``object_list``: The list of objects. This variable's name depends on the
     
    767759For more on pagination, read the :doc:`pagination documentation
    768760</topics/pagination>`.
    769761
    770 .. versionadded:: 1.0
    771 
    772762As a special case, you are also permitted to use ``last`` as a value for
    773763``page``::
    774764
     
    853843The ``django.views.generic.create_update`` module contains a set of functions
    854844for creating, editing and deleting objects.
    855845
    856 .. versionchanged:: 1.0
    857 
    858846``django.views.generic.create_update.create_object`` and
    859847``django.views.generic.create_update.update_object`` now use the new :doc:`forms
    860848library </topics/forms/index>` to build and display the form.
  • docs/ref/middleware.txt

    diff --git a/docs/ref/middleware.txt b/docs/ref/middleware.txt
    a b  
    5252      you don't have a valid URL pattern for ``foo.com/bar`` but *do* have a
    5353      valid pattern for ``foo.com/bar/``.
    5454
    55       .. versionchanged:: 1.0
    56          The behavior of :setting:`APPEND_SLASH` has changed slightly in this
    57          version. It didn't used to check whether the pattern was matched in
    58          the URLconf.
    59 
    6055      If :setting:`PREPEND_WWW` is ``True``, URLs that lack a leading "www."
    6156      will be redirected to the same URL with a leading "www."
    6257
     
    183178
    184179.. class:: django.middleware.csrf.CsrfMiddleware
    185180
    186 .. versionadded:: 1.0
    187 
    188181Adds protection against Cross Site Request Forgeries by adding hidden form
    189182fields to POST forms and checking requests for the correct value. See the
    190183:doc:`Cross Site Request Forgery protection documentation </ref/contrib/csrf>`.
  • docs/ref/models/fields.txt

    diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
    a b  
    171171
    172172.. attribute:: Field.db_tablespace
    173173
    174 .. versionadded:: 1.0
    175 
    176174The name of the database tablespace to use for this field's index, if this field
    177175is indexed. The default is the project's :setting:`DEFAULT_INDEX_TABLESPACE`
    178176setting, if set, or the :attr:`~Field.db_tablespace` of the model, if any. If
     
    425423``DecimalField``
    426424----------------
    427425
    428 .. versionadded:: 1.0
    429 
    430426.. class:: DecimalField(max_digits=None, decimal_places=None, [**options])
    431427
    432428A fixed-precision decimal number, represented in Python by a
     
    482478    date/time of the file upload (so that uploaded files don't fill up the given
    483479    directory).
    484480
    485     .. versionchanged:: 1.0
    486 
    487481    This may also be a callable, such as a function, which will be called to
    488482    obtain the upload path, including the filename. This callable must be able
    489483    to accept two arguments, and return a Unix-style path (with forward slashes)
     
    512506
    513507.. attribute:: FileField.storage
    514508
    515     .. versionadded:: 1.0
    516 
    517509    Optional. A storage object, which handles the storage and retrieval of your
    518510    files. See :doc:`/topics/files` for details on how to provide this object.
    519511
     
    560552root, then somebody could upload a CGI or PHP script and execute that script by
    561553visiting its URL on your site. Don't allow that.
    562554
    563 .. versionadded:: 1.0
    564    The ``max_length`` argument was added in this version.
    565 
    566555By default, :class:`FileField` instances are
    567556created as ``varchar(100)`` columns in your database. As with other fields, you
    568557can change the maximum length using the :attr:`~CharField.max_length` argument.
     
    645634because the :attr:`~FilePathField.match` applies to the base filename
    646635(``foo.gif`` and ``bar.gif``).
    647636
    648 .. versionadded:: 1.0
    649    The ``max_length`` argument was added in this version.
    650 
    651637By default, :class:`FilePathField` instances are
    652638created as ``varchar(100)`` columns in your database. As with other fields, you
    653639can change the maximum length using the :attr:`~CharField.max_length` argument.
     
    657643
    658644.. class:: FloatField([**options])
    659645
    660 .. versionchanged:: 1.0
    661 
    662646A floating-point number represented in Python by a ``float`` instance.
    663647
    664648The admin represents this as an ``<input type="text">`` (a single-line input).
     
    692676
    693677.. _Python Imaging Library: http://www.pythonware.com/products/pil/
    694678
    695 .. versionadded:: 1.0
    696    The ``max_length`` argument was added in this version.
    697 
    698679By default, :class:`ImageField` instances are created as ``varchar(100)``
    699680columns in your database. As with other fields, you can change the maximum
    700681length using the :attr:`~CharField.max_length` argument.
     
    867848    class Manufacturer(models.Model):
    868849        # ...
    869850
    870 .. versionadded:: 1.0
    871 
    872851To refer to models defined in another application, you can explicitly specify
    873852a model with the full application label. For example, if the ``Manufacturer``
    874853model above is defined in another application called ``production``, you'd
  • docs/ref/models/instances.txt

    diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
    a b  
    133133
    134134.. method:: Model.save([force_insert=False, force_update=False, using=DEFAULT_DB_ALIAS])
    135135
    136 .. versionadded:: 1.0
    137    The ``force_insert`` and ``force_update`` arguments were added.
    138 
    139136.. versionadded:: 1.2
    140137   The ``using`` argument was added.
    141138
     
    168165The ``pk`` property
    169166~~~~~~~~~~~~~~~~~~~
    170167
    171 .. versionadded:: 1.0
    172 
    173168.. attribute:: Model.pk
    174169
    175170Regardless of whether you define a primary key field yourself, or let Django
     
    278273Forcing an INSERT or UPDATE
    279274~~~~~~~~~~~~~~~~~~~~~~~~~~~
    280275
    281 .. versionadded:: 1.0
    282 
    283276In some rare circumstances, it's necessary to be able to force the ``save()``
    284277method to perform an SQL ``INSERT`` and not fall back to doing an ``UPDATE``.
    285278Or vice-versa: update, if possible, but not insert a new row. In these cases
  • docs/ref/models/options.txt

    diff --git a/docs/ref/models/options.txt b/docs/ref/models/options.txt
    a b  
    6565
    6666.. attribute:: Options.db_tablespace
    6767
    68 .. versionadded:: 1.0
    69 
    7068The name of the database tablespace to use for the model. If the backend doesn't
    7169support tablespaces, this option is ignored.
    7270
     
    212210appropriate ``UNIQUE`` statements are included in the ``CREATE TABLE``
    213211statement).
    214212
    215 .. versionadded:: 1.0
    216 
    217213For convenience, unique_together can be a single list when dealing with a single
    218214set of fields::
    219215
  • docs/ref/models/querysets.txt

    diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
    a b  
    278278ordering may well be exactly what you want to do. Use ordering on multi-valued
    279279fields with care and make sure the results are what you expect.
    280280
    281 .. versionadded:: 1.0
    282 
    283281If you don't want any ordering to be applied to a query, not even the default
    284282ordering, call ``order_by()`` with no parameters.
    285283
    286 .. versionadded:: 1.0
    287 
    288 The syntax for ordering across related models has changed. See the `Django 0.96
    289 documentation`_ for the old behaviour.
    290 
    291 .. _Django 0.96 documentation: http://www.djangoproject.com/documentation/0.96/model-api/#floatfield
    292 
    293284There's no way to specify whether ordering should be case sensitive. With
    294285respect to case-sensitivity, Django will order results however your database
    295286backend normally orders them.
     
    305296
    306297.. method:: reverse()
    307298
    308 .. versionadded:: 1.0
    309 
    310299Use the ``reverse()`` method to reverse the order in which a queryset's
    311300elements are returned. Calling ``reverse()`` a second time restores the
    312301ordering back to the normal direction.
     
    431420      if the ``extra()`` clause is used after the ``values()``, the
    432421      fields added by the select will be included automatically.
    433422
    434 .. versionadded:: 1.0
    435 
    436 Previously, it was not possible to pass ``blog_id`` to ``values()`` in the above
    437 example, only ``blog``.
    438 
    439423A ``ValuesQuerySet`` is useful when you know you're only going to need values
    440424from a small number of the available fields and you won't need the
    441425functionality of a model instance object. It's more efficient to select only
     
    458442
    459443.. method:: values_list(*fields)
    460444
    461 .. versionadded:: 1.0
    462 
    463445This is similar to ``values()`` except that instead of returning dictionaries,
    464446it returns tuples when iterated over. Each tuple contains the value from the
    465447respective field passed into the ``values_list()`` call -- so the first item is
     
    524506
    525507.. method:: none()
    526508
    527 .. versionadded:: 1.0
    528 
    529509Returns an ``EmptyQuerySet`` -- a ``QuerySet`` that always evaluates to
    530510an empty list. This can be used in cases where you know that you should
    531511return an empty result set and your caller is expecting a ``QuerySet``
     
    541521
    542522.. method:: all()
    543523
    544 .. versionadded:: 1.0
    545 
    546524Returns a ''copy'' of the current ``QuerySet`` (or ``QuerySet`` subclass you
    547525pass in). This can be useful in some situations where you might want to pass
    548526in either a model manager or a ``QuerySet`` and do further filtering on the
     
    656634parameter in the same ``select_related()`` call, since they are
    657635conflicting options.
    658636
    659 .. versionadded:: 1.0
    660 
    661 Both the ``depth`` argument and the ability to specify field names in the call
    662 to ``select_related()`` are new in Django version 1.0.
    663 
    664637.. versionchanged:: 1.2
    665638
    666639You can also refer to the reverse direction of a ``OneToOneFields`` in
     
    733706    some database backends, such as some MySQL versions, don't support
    734707    subqueries.
    735708
    736     .. versionadded:: 1.0
    737 
    738709    In some rare cases, you might wish to pass parameters to the SQL fragments
    739710    in ``extra(select=...)``. For this purpose, use the ``select_params``
    740711    parameter. Since ``select_params`` is a sequence and the ``select``
     
    12501221    SELECT ... WHERE id = 14;
    12511222    SELECT ... WHERE id IS NULL;
    12521223
    1253 .. versionchanged:: 1.0
    1254    The semantics of ``id__exact=None`` have changed in Django 1.0. Previously,
    1255    it was (intentionally) converted to ``WHERE id = NULL`` at the SQL level,
    1256    which would never match anything. It has now been changed to behave the
    1257    same as ``id__isnull=True``.
    1258 
    12591224.. admonition:: MySQL comparisons
    12601225
    12611226    In MySQL, a database table's "collation" setting determines whether
     
    16631628regex
    16641629~~~~~
    16651630
    1666 .. versionadded:: 1.0
    1667 
    16681631Case-sensitive regular expression match.
    16691632
    16701633The regular expression syntax is that of the database backend in use.
     
    16941657iregex
    16951658~~~~~~
    16961659
    1697 .. versionadded:: 1.0
    1698 
    16991660Case-insensitive regular expression match.
    17001661
    17011662Example::
  • docs/ref/request-response.txt

    diff --git a/docs/ref/request-response.txt b/docs/ref/request-response.txt
    a b  
    4747
    4848.. attribute:: HttpRequest.encoding
    4949
    50     .. versionadded:: 1.0
    51 
    5250    A string representing the current encoding used to decode form submission
    5351    data (or ``None``, which means the ``DEFAULT_CHARSET`` setting is used).
    5452    You can write to this attribute to change the encoding used when accessing
     
    111109    ``enctype="multipart/form-data"``. Otherwise, ``FILES`` will be a blank
    112110    dictionary-like object.
    113111
    114     .. versionchanged:: 1.0
    115 
    116     In previous versions of Django, ``request.FILES`` contained simple ``dict``
    117     objects representing uploaded files. This is no longer true -- files are
    118     represented by ``UploadedFile`` objects as described below.
    119 
    120112    These ``UploadedFile`` objects will emulate the old-style ``dict``
    121113    interface, but this is deprecated and will be removed in the next release of
    122114    Django.
     
    189181
    190182.. method:: HttpRequest.get_host()
    191183
    192    .. versionadded:: 1.0
    193 
    194184   Returns the originating host of the request using information from the
    195185   ``HTTP_X_FORWARDED_HOST`` and ``HTTP_HOST`` headers (in that order). If
    196186   they don't provide a value, the method uses a combination of
     
    208198
    209199.. method:: HttpRequest.build_absolute_uri(location)
    210200
    211    .. versionadded:: 1.0
    212 
    213201   Returns the absolute URI form of ``location``. If no location is provided,
    214202   the location will be set to ``request.get_full_path()``.
    215203
     
    226214
    227215.. method:: HttpRequest.is_ajax()
    228216
    229    .. versionadded:: 1.0
    230 
    231217   Returns ``True`` if the request was made via an ``XMLHttpRequest``, by
    232218   checking the ``HTTP_X_REQUESTED_WITH`` header for the string
    233219   ``'XMLHttpRequest'``. Most modern JavaScript libraries send this header.
     
    478464
    479465    ``status`` is the `HTTP Status code`_ for the response.
    480466
    481     .. versionadded:: 1.0
    482 
    483467    ``content_type`` is an alias for ``mimetype``. Historically, this parameter
    484468    was only called ``mimetype``, but since this is actually the value included
    485469    in the HTTP ``Content-Type`` header, it can also include the character set
     
    576560
    577561.. class:: HttpResponseBadRequest
    578562
    579     .. versionadded:: 1.0
    580 
    581563    Acts just like :class:`HttpResponse` but uses a 400 status code.
    582564
    583565.. class:: HttpResponseNotFound
  • docs/ref/settings.txt

    diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
    a b  
    538538DEBUG_PROPAGATE_EXCEPTIONS
    539539--------------------------
    540540
    541 .. versionadded:: 1.0
    542 
    543541Default: ``False``
    544542
    545543If set to True, Django's normal exception handling of view functions
     
    605603DEFAULT_INDEX_TABLESPACE
    606604------------------------
    607605
    608 .. versionadded:: 1.0
    609 
    610606Default: ``''`` (Empty string)
    611607
    612608Default tablespace to use for indexes on fields that don't specify
     
    617613DEFAULT_TABLESPACE
    618614------------------
    619615
    620 .. versionadded:: 1.0
    621 
    622616Default: ``''`` (Empty string)
    623617
    624618Default tablespace to use for models that don't specify one, if the
     
    721715EMAIL_USE_TLS
    722716-------------
    723717
    724 .. versionadded:: 1.0
    725 
    726718Default: ``False``
    727719
    728720Whether to use a TLS (secure) connection when talking to the SMTP server.
     
    732724FILE_CHARSET
    733725------------
    734726
    735 .. versionadded:: 1.0
    736 
    737727Default: ``'utf-8'``
    738728
    739729The character encoding used to decode any files read from disk. This includes
     
    744734FILE_UPLOAD_HANDLERS
    745735--------------------
    746736
    747 .. versionadded:: 1.0
    748 
    749737Default::
    750738
    751739    ("django.core.files.uploadhandler.MemoryFileUploadHandler",
     
    758746FILE_UPLOAD_MAX_MEMORY_SIZE
    759747---------------------------
    760748
    761 .. versionadded:: 1.0
    762 
    763749Default: ``2621440`` (i.e. 2.5 MB).
    764750
    765751The maximum size (in bytes) that an upload will be before it gets streamed to
     
    798784FILE_UPLOAD_TEMP_DIR
    799785--------------------
    800786
    801 .. versionadded:: 1.0
    802 
    803787Default: ``None``
    804788
    805789The directory to store data temporarily while uploading files. If ``None``,
     
    945929LANGUAGE_COOKIE_NAME
    946930--------------------
    947931
    948 .. versionadded:: 1.0
    949 
    950932Default: ``'django_language'``
    951933
    952934The name of the cookie to use for the language cookie. This can be whatever you
     
    1011993LOGIN_REDIRECT_URL
    1012994------------------
    1013995
    1014 .. versionadded:: 1.0
    1015 
    1016996Default: ``'/accounts/profile/'``
    1017997
    1018998The URL where requests are redirected after login when the
     
    10261006LOGIN_URL
    10271007---------
    10281008
    1029 .. versionadded:: 1.0
    1030 
    10311009Default: ``'/accounts/login/'``
    10321010
    10331011The URL where requests are redirected for login, especially when using the
     
    10381016LOGOUT_URL
    10391017----------
    10401018
    1041 .. versionadded:: 1.0
    1042 
    10431019Default: ``'/accounts/logout/'``
    10441020
    10451021LOGIN_URL counterpart.
     
    13041280SESSION_COOKIE_PATH
    13051281-------------------
    13061282
    1307 .. versionadded:: 1.0
    1308 
    13091283Default: ``'/'``
    13101284
    13111285The path set on the session cookie. This should either match the URL path of your
     
    13321306SESSION_ENGINE
    13331307--------------
    13341308
    1335 .. versionadded:: 1.0
    1336 
    13371309.. versionchanged:: 1.1
    13381310   The ``cached_db`` backend was added
    13391311
     
    13631335SESSION_FILE_PATH
    13641336-----------------
    13651337
    1366 .. versionadded:: 1.0
    1367 
    13681338Default: ``None``
    13691339
    13701340If you're using file-based session storage, this sets the directory in
  • docs/ref/templates/api.txt

    diff --git a/docs/ref/templates/api.txt b/docs/ref/templates/api.txt
    a b  
    426426django.core.context_processors.media
    427427~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    428428
    429 .. versionadded:: 1.0
    430 
    431429If :setting:`TEMPLATE_CONTEXT_PROCESSORS` contains this processor, every
    432430``RequestContext`` will contain a variable ``MEDIA_URL``, providing the
    433431value of the :setting:`MEDIA_URL` setting.
  • docs/ref/templates/builtins.txt

    diff --git a/docs/ref/templates/builtins.txt b/docs/ref/templates/builtins.txt
    a b  
    1919autoescape
    2020~~~~~~~~~~
    2121
    22 .. versionadded:: 1.0
    23 
    2422Control the current auto-escaping behavior. This tag takes either ``on`` or
    2523``off`` as an argument and that determines whether auto-escaping is in effect
    2624inside the block. The block is closed with an ``endautoescape`` ending tag.
     
    7270cycle
    7371~~~~~
    7472
    75 .. versionchanged:: 1.0
    76     Cycle among the given strings or variables each time this tag is encountered.
     73Cycle among the given strings or variables each time this tag is encountered.
    7774
    7875Within a loop, cycles among the given strings each time through the
    7976loop::
     
    239236
    240237You can loop over a list in reverse by using ``{% for obj in list reversed %}``.
    241238
    242 .. versionadded:: 1.0
    243 
    244239If you need to loop over a list of lists, you can unpack the values
    245240in each sub-list into individual variables. For example, if your context
    246241contains a list of (x,y) coordinates called ``points``, you could use the
     
    953948
    954949The template tag will output the string ``/clients/client/123/``.
    955950
    956 .. versionadded:: 1.0
    957 
    958951If you're using :ref:`named URL patterns <naming-url-patterns>`, you can
    959952refer to the name of the pattern in the ``url`` tag instead of using the
    960953path to the view.
     
    963956:exc:`NoReverseMatch` exception raised, which will cause your site to display an
    964957error page.
    965958
    966 .. versionadded:: 1.0
    967 
    968959If you'd like to retrieve a URL without displaying it, you can use a slightly
    969960different call::
    970961
     
    10261017with
    10271018~~~~
    10281019
    1029 .. versionadded:: 1.0
    1030 
    10311020Caches a complex variable under a simpler name. This is useful when accessing
    10321021an "expensive" method (e.g., one that hits the database) multiple times.
    10331022
     
    12781267it is safe to use this function even in auto-escaping environments. If you want
    12791268multiple escaping passes to be applied, use the ``force_escape`` filter.
    12801269
    1281 .. versionchanged:: 1.0
    1282     Due to auto-escaping, the behavior of this filter has changed slightly.
    1283     The replacements are only made once, after
    1284     all other filters are applied -- including filters before and after it.
    1285 
    12861270.. templatefilter:: escapejs
    12871271
    12881272escapejs
    12891273~~~~~~~~
    12901274
    1291 .. versionadded:: 1.0
    1292 
    12931275Escapes characters for use in JavaScript strings. This does *not* make the
    12941276string safe for use in HTML, but does protect you from syntax errors when using
    12951277templates to generate JavaScript/JSON.
     
    13331315fix_ampersands
    13341316~~~~~~~~~~~~~~
    13351317
    1336 .. versionchanged:: 1.0
    1337     This is rarely useful as ampersands are now automatically escaped. See escape_ for more information.
     1318..note::
     1319
     1320    This is rarely useful as ampersands are automatically escaped. See escape_ for more information.
    13381321
    13391322Replaces ampersands with ``&amp;`` entities.
    13401323
     
    13911374force_escape
    13921375~~~~~~~~~~~~
    13931376
    1394 .. versionadded:: 1.0
    1395 
    13961377Applies HTML escaping to a string (see the ``escape`` filter for details).
    13971378This filter is applied *immediately* and returns a new, escaped string. This
    13981379is useful in the rare cases where you need multiple escaping or want to apply
     
    14521433last
    14531434~~~~
    14541435
    1455 .. versionadded:: 1.0
    1456 
    14571436Returns the last item in a list.
    14581437
    14591438For example::
     
    19181897Recursively takes a self-nested list and returns an HTML unordered list --
    19191898WITHOUT opening and closing <ul> tags.
    19201899
    1921 .. versionchanged:: 1.0
    1922    The format accepted by ``unordered_list`` has changed to be easier to understand.
    1923 
    19241900The list is assumed to be in the proper format. For example, if ``var`` contains
    19251901``['States', ['Kansas', ['Lawrence', 'Topeka'], 'Illinois']]``, then
    19261902``{{ var|unordered_list }}`` would return::
     
    19371913    </ul>
    19381914    </li>
    19391915
    1940 Note: the previous more restrictive and verbose format is still supported:
     1916Note: An older, more restrictive and verbose input format is also supported:
    19411917``['States', [['Kansas', [['Lawrence', []], ['Topeka', []]]], ['Illinois', []]]]``,
    19421918
    19431919.. templatefilter:: upper
  • docs/ref/unicode.txt

    diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt
    a b  
    22Unicode data
    33============
    44
    5 .. versionadded:: 1.0
    6 
    75Django natively supports Unicode data everywhere. Providing your database can
    86somehow store the data, you can safely pass around Unicode strings to
    97templates, models and the database.
  • docs/topics/auth.txt

    diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt
    a b  
    190190
    191191    .. method:: models.User.set_unusable_password()
    192192
    193         .. versionadded:: 1.0
    194 
    195193        Marks the user as having no password set.  This isn't the same as
    196194        having a blank string for a password.
    197195        :meth:`~django.contrib.auth.models.User.check_password()` for this user
     
    203201
    204202    .. method:: models.User.has_usable_password()
    205203
    206         .. versionadded:: 1.0
    207 
    208204        Returns ``False`` if
    209205        :meth:`~django.contrib.auth.models.User.set_unusable_password()` has
    210206        been called for this user.
     
    395391only supported on platforms that have the standard Python ``crypt`` module
    396392available.
    397393
    398 .. versionadded:: 1.0
    399     Support for the ``crypt`` module is new in Django 1.0.
    400 
    401394For example::
    402395
    403396    sha1$a1976$a36cc8cbf81742a8fb52e221aaeab48ed7f58ab4
     
    450443Creating superusers
    451444-------------------
    452445
    453 .. versionadded:: 1.0
    454    The ``manage.py createsuperuser`` command is new.
    455 
    456446:djadmin:`manage.py syncdb <syncdb>` prompts you to create a superuser the
    457447first time you run it after adding ``'django.contrib.auth'`` to your
    458448:setting:`INSTALLED_APPS`. If you need to create a superuser at a later date,
     
    653643    Note that :func:`~django.contrib.auth.logout()` doesn't throw any errors if
    654644    the user wasn't logged in.
    655645
    656     .. versionchanged:: 1.0
    657        Calling ``logout()`` now cleans session data.
    658 
    659646    When you call :func:`~django.contrib.auth.logout()`, the session data for
    660647    the current request is completely cleaned out. All existing data is
    661648    removed. This is to prevent another person from using the same web browser
  • docs/topics/cache.txt

    diff --git a/docs/topics/cache.txt b/docs/topics/cache.txt
    a b  
    238238Using a custom cache backend
    239239----------------------------
    240240
    241 .. versionadded:: 1.0
    242 
    243241While Django includes support for a number of cache backends out-of-the-box,
    244242sometimes you might want to use a customized cache backend. To use an external
    245243cache backend with Django, use a Python import path as the scheme portion (the
     
    291289The per-site cache
    292290==================
    293291
    294 .. versionchanged:: 1.0
    295     (previous versions of Django only provided a single ``CacheMiddleware`` instead
    296     of the two pieces described below).
    297 
    298292Once the cache is set up, the simplest way to use caching is to cache your
    299293entire site. You'll need to add
    300294``'django.middleware.cache.UpdateCacheMiddleware'`` and
     
    344338
    345339See :doc:`/topics/http/middleware` for more on middleware.
    346340
    347 .. versionadded:: 1.0
    348 
    349341If a view sets its own cache expiry time (i.e. it has a ``max-age`` section in
    350342its ``Cache-Control`` header) then the page will be cached until the expiry
    351343time, rather than ``CACHE_MIDDLEWARE_SECONDS``. Using the decorators in
     
    441433Template fragment caching
    442434=========================
    443435
    444 .. versionadded:: 1.0
    445 
    446436If you're after even more control, you can also cache template fragments using
    447437the ``cache`` template tag. To give your template access to this tag, put
    448438``{% load cache %}`` near the top of your template.
     
    558548    >>> cache.get('my_key', 'has expired')
    559549    'has expired'
    560550
    561 .. versionadded:: 1.0
    562 
    563551To add a key only if it doesn't already exist, use the ``add()`` method.
    564552It takes the same parameters as ``set()``, but it will not attempt to
    565553update the cache if the key specified is already present::
  • docs/topics/db/models.txt

    diff --git a/docs/topics/db/models.txt b/docs/topics/db/models.txt
    a b  
    387387Extra fields on many-to-many relationships
    388388~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    389389
    390 .. versionadded:: 1.0
    391 
    392390When you're only dealing with simple many-to-many relationships such as
    393391mixing and matching pizzas and toppings, a standard :class:`~django.db.models.ManyToManyField` is all you need. However, sometimes
    394392you may need to associate data with the relationship between two models.
     
    552550
    553551.. _One-to-one relationship model example: http://www.djangoproject.com/documentation/models/one_to_one/
    554552
    555 .. versionadded:: 1.0
    556 
    557553:class:`~django.db.models.OneToOneField` fields also accept one optional argument
    558554described in the :ref:`model field reference <ref-onetoone>`.
    559555
     
    605601Custom field types
    606602------------------
    607603
    608 .. versionadded:: 1.0
    609 
    610604If one of the existing model fields cannot be used to fit your purposes, or if
    611605you wish to take advantage of some less common database column types, you can
    612606create your own field class. Full coverage of creating your own fields is
     
    768762Model inheritance
    769763=================
    770764
    771 .. versionadded:: 1.0
    772 
    773765Model inheritance in Django works almost identically to the way normal
    774766class inheritance works in Python. The only decision you have to make
    775767is whether you want the parent models to be models in their own right
  • docs/topics/db/queries.txt

    diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt
    a b  
    437437Spanning multi-valued relationships
    438438~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    439439
    440 .. versionadded:: 1.0
    441 
    442440When you are filtering an object based on a ``ManyToManyField`` or a reverse
    443441``ForeignKey``, there are two different sorts of filter you may be
    444442interested in. Consider the ``Blog``/``Entry`` relationship (``Blog`` to
     
    766764Updating multiple objects at once
    767765=================================
    768766
    769 .. versionadded:: 1.0
    770 
    771767Sometimes you want to set a field to a particular value for all the objects in
    772768a ``QuerySet``. You can do this with the ``update()`` method. For example::
    773769
  • docs/topics/email.txt

    diff --git a/docs/topics/email.txt b/docs/topics/email.txt
    a b  
    196196The EmailMessage class
    197197======================
    198198
    199 .. versionadded:: 1.0
    200 
    201199Django's :meth:`~django.core.mail.send_mail()` and
    202200:meth:`~django.core.mail.send_mass_mail()` functions are actually thin
    203201wrappers that make use of the :class:`~django.core.mail.EmailMessage` class.
  • docs/topics/files.txt

    diff --git a/docs/topics/files.txt b/docs/topics/files.txt
    a b  
    22Managing files
    33==============
    44
    5 .. versionadded:: 1.0
    6 
    75This document describes Django's file access APIs.
    86
    97By default, Django stores files locally, using the :setting:`MEDIA_ROOT` and
  • docs/topics/forms/index.txt

    diff --git a/docs/topics/forms/index.txt b/docs/topics/forms/index.txt
    a b  
    113113    3. If the form has been submitted but is invalid, the bound form instance is
    114114       passed on to the template.
    115115
    116 .. versionchanged:: 1.0
    117     The ``cleaned_data`` attribute was called ``clean_data`` in earlier releases.
    118 
    119116The distinction between **bound** and **unbound** forms is important. An unbound
    120117form does not have any data associated with it; when rendered to the user, it
    121118will be empty or will contain default values. A bound form does have submitted
  • docs/topics/forms/modelforms.txt

    diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt
    a b  
    105105                                     ``widget=forms.Textarea``
    106106    ===============================  ========================================
    107107
    108 
    109 .. versionadded:: 1.0
    110     The ``FloatField`` form field and ``DecimalField`` model and form fields
    111     are new in Django 1.0.
    112 
    113108.. versionadded:: 1.2
    114109    The ``BigIntegerField`` is new in Django 1.2.
    115110
  • docs/topics/http/file-uploads.txt

    diff --git a/docs/topics/http/file-uploads.txt b/docs/topics/http/file-uploads.txt
    a b  
    44
    55.. currentmodule:: django.core.files
    66
    7 .. versionadded:: 1.0
    8 
    97When Django handles a file upload, the file data ends up placed in
    108:attr:`request.FILES <django.http.HttpRequest.FILES>` (for more on the
    119``request`` object see the documentation for :doc:`request and response objects
  • docs/topics/http/sessions.txt

    diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt
    a b  
    2929Configuring the session engine
    3030==============================
    3131
    32 .. versionadded:: 1.0
    33 
    3432By default, Django stores sessions in your database (using the model
    3533``django.contrib.sessions.models.Session``). Though this is convenient, in
    3634some setups it's faster to store session data elsewhere, so Django can be
     
    138136
    139137    * ``clear()``
    140138
    141 .. versionadded:: 1.0
    142    ``setdefault()`` and ``clear()`` are new in this version.
    143 
    144139It also has these methods:
    145140
    146141    * ``flush()``
    147142
    148       .. versionadded:: 1.0
    149 
    150143      Delete the current session data from the session and regenerate the
    151144      session key value that is sent back to the user in the cookie. This is
    152145      used if you want to ensure that the previous session data can't be
     
    173166
    174167    * ``set_expiry(value)``
    175168
    176       .. versionadded:: 1.0
    177 
    178169      Sets the expiration time for the session. You can pass a number of
    179170      different values:
    180171
     
    198189
    199190    * ``get_expiry_age()``
    200191
    201       .. versionadded:: 1.0
    202 
    203192      Returns the number of seconds until this session expires. For sessions
    204193      with no custom expiration (or those set to expire at browser close), this
    205194      will equal ``settings.SESSION_COOKIE_AGE``.
    206195
    207196    * ``get_expiry_date()``
    208197
    209       .. versionadded:: 1.0
    210 
    211198      Returns the date this session will expire. For sessions with no custom
    212199      expiration (or those set to expire at browser close), this will equal the
    213200      date ``settings.SESSION_COOKIE_AGE`` seconds from now.
    214201
    215202    * ``get_expire_at_browser_close()``
    216203
    217       .. versionadded:: 1.0
    218 
    219204      Returns either ``True`` or ``False``, depending on whether the user's
    220205      session cookie will expire when the user's Web browser is closed.
    221206
     
    302287Using sessions out of views
    303288===========================
    304289
    305 .. versionadded:: 1.0
    306 
    307290An API is available to manipulate session data outside of a view::
    308291
    309292    >>> from django.contrib.sessions.backends.db import SessionStore
     
    384367her browser. Use this if you want people to have to log in every time they open
    385368a browser.
    386369
    387 .. versionadded:: 1.0
    388 
    389370This setting is a global default and can be overwritten at a per-session level
    390371by explicitly calling ``request.session.set_expiry()`` as described above in
    391372`using sessions in views`_.
     
    415396SESSION_ENGINE
    416397--------------
    417398
    418 .. versionadded:: 1.0
    419 
    420399.. versionchanged:: 1.1
    421400   The ``cached_db`` backend was added
    422401
     
    434413SESSION_FILE_PATH
    435414-----------------
    436415
    437 .. versionadded:: 1.0
    438 
    439416Default: ``/tmp/``
    440417
    441418If you're using file-based session storage, this sets the directory in
     
    467444SESSION_COOKIE_PATH
    468445-------------------
    469446
    470 .. versionadded:: 1.0
    471 
    472447Default: ``'/'``
    473448
    474449The path set on the session cookie. This should either match the URL path of
  • docs/topics/http/shortcuts.txt

    diff --git a/docs/topics/http/shortcuts.txt b/docs/topics/http/shortcuts.txt
    a b  
    4848
    4949``mimetype``
    5050
    51     .. versionadded:: 1.0
    52 
    5351    The MIME type to use for the resulting document. Defaults to the value of
    5452    the :setting:`DEFAULT_CONTENT_TYPE` setting.
    5553
  • docs/topics/http/urls.txt

    diff --git a/docs/topics/http/urls.txt b/docs/topics/http/urls.txt
    a b  
    223223url
    224224---
    225225
    226 .. versionadded:: 1.0
    227 
    228226.. function:: url(regex, view, kwargs=None, name=None, prefix='')
    229227
    230228You can use the ``url()`` function, instead of a tuple, as an argument to
     
    634632Naming URL patterns
    635633===================
    636634
    637 .. versionadded:: 1.0
    638 
    639635It's fairly common to use the same view function in multiple URL patterns in
    640636your URLconf. For example, these two URL patterns both point to the ``archive``
    641637view::
  • docs/topics/i18n/deployment.txt

    diff --git a/docs/topics/i18n/deployment.txt b/docs/topics/i18n/deployment.txt
    a b  
    8181
    8282    * Failing that, it looks for a cookie.
    8383
    84       .. versionchanged:: 1.0
    85 
    86       In Django version 0.96 and before, the cookie's name is hard-coded to
    87       ``django_language``. In Django 1,0, The cookie name is set by the
    88       ``LANGUAGE_COOKIE_NAME`` setting. (The default name is
    89       ``django_language``.)
     84      The name of the cookie used is set by the ``LANGUAGE_COOKIE_NAME``
     85      setting. (The default name is ``django_language``.)
    9086
    9187    * Failing that, it looks at the ``Accept-Language`` HTTP header. This
    9288      header is sent by your browser and tells the server which language(s) you
  • docs/topics/pagination.txt

    diff --git a/docs/topics/pagination.txt b/docs/topics/pagination.txt
    a b  
    55.. module:: django.core.paginator
    66   :synopsis: Classes to help you easily manage paginated data.
    77
    8 .. versionchanged:: 1.0
    9    Pagination facilities have been almost fully reworked.
    10 
    118Django provides a few classes that help you manage paginated data -- that is,
    129data that's split across several pages, with "Previous/Next" links. These
    1310classes live in :file:`django/core/paginator.py`.
  • docs/topics/templates.txt

    diff --git a/docs/topics/templates.txt b/docs/topics/templates.txt
    a b  
    390390Automatic HTML escaping
    391391=======================
    392392
    393 .. versionadded:: 1.0
    394 
    395393When generating HTML from templates, there's always a risk that a variable will
    396394include characters that affect the resulting HTML. For example, consider this
    397395template fragment::
  • docs/topics/testing.txt

    diff --git a/docs/topics/testing.txt b/docs/topics/testing.txt
    a b  
    256256
    257257Note that we used ``animals``, not ``myproject.animals``.
    258258
    259 .. versionadded:: 1.0
    260    You can now choose which test to run.
    261 
    262259You can be even *more* specific by naming an individual test case. To
    263260run a single test case in an application (for example, the
    264261``AnimalTestCase`` described in the "Writing unit tests" section), add
     
    352349to make sure that the given user account has sufficient privileges to
    353350create a new database on the system.
    354351
    355 .. versionadded:: 1.0
    356 
    357352For fine-grained control over the character encoding of your test
    358353database, use the :setting:`TEST_CHARSET` option. If you're using
    359354MySQL, you can also use the :setting:`TEST_COLLATION` option to
     
    778773
    779774    .. method:: Client.login(**credentials)
    780775
    781         .. versionadded:: 1.0
    782 
    783776        If your site uses Django's :doc:`authentication system</topics/auth>`
    784777        and you deal with logging in users, you can use the test client's
    785778        ``login()`` method to simulate the effect of a user logging into the
     
    824817
    825818    .. method:: Client.logout()
    826819
    827         .. versionadded:: 1.0
    828 
    829820        If your site uses Django's :doc:`authentication system</topics/auth>`,
    830821        the ``logout()`` method can be used to simulate the effect of a user
    831822        logging out of your site.
     
    10371028Default test client
    10381029~~~~~~~~~~~~~~~~~~~
    10391030
    1040 .. versionadded:: 1.0
    1041 
    10421031.. attribute:: TestCase.client
    10431032
    10441033Every test case in a ``django.test.TestCase`` instance has access to an
     
    11431132URLconf configuration
    11441133~~~~~~~~~~~~~~~~~~~~~
    11451134
    1146 .. versionadded:: 1.0
    1147 
    11481135.. attribute:: TestCase.urls
    11491136
    11501137If your application provides views, you may want to include tests that use the
     
    12121199Emptying the test outbox
    12131200~~~~~~~~~~~~~~~~~~~~~~~~
    12141201
    1215 .. versionadded:: 1.0
    1216 
    12171202If you use Django's custom ``TestCase`` class, the test runner will clear the
    12181203contents of the test e-mail outbox at the start of each test case.
    12191204
     
    12221207Assertions
    12231208~~~~~~~~~~
    12241209
    1225 .. versionadded:: 1.0
    1226 
    12271210.. versionchanged:: 1.2
    12281211    Addded ``msg_prefix`` argument.
    12291212
     
    12931276E-mail services
    12941277---------------
    12951278
    1296 .. versionadded:: 1.0
    1297 
    12981279If any of your Django views send e-mail using :doc:`Django's e-mail
    12991280functionality </topics/email>`, you probably don't want to send e-mail each time
    13001281you run a test using that view. For this reason, Django's test runner
     
    15431524    :setting:`NAME` in :setting:`DATABASES` to match the name of the test
    15441525    database.
    15451526
    1546     .. versionchanged:: 1.0
    1547        ``create_test_db()`` now returns the name of the test database.
    1548 
    15491527.. function:: destroy_test_db(old_database_name, verbosity=1)
    15501528
    15511529    Destroys the database whose name is in stored in :setting:`NAME` in the
Back to Top