Django

Code

Changeset 8843

Show
Ignore:
Timestamp:
09/01/08 22:40:42 (4 months ago)
Author:
jacob
Message:

Fixed #8753: converted "new in ..." callouts to proper Sphinx "versionadded/versionchanged" directives. Thanks to Marc Fargas for all the heavy lifting here.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • django/trunk/docs/_ext/djangodocs.py

    r8593 r8843  
    8989        self.body.append(')') 
    9090        pass 
     91         
     92    # 
     93    # Turn the "new in version" stuff (versoinadded/versionchanged) into a 
     94    # better callout -- the Sphinx default is just a little span, 
     95    # which is a bit less obvious that I'd like. 
     96    # 
     97    # FIXME: these messages are all hardcoded in English. We need to chanage  
     98    # that to accomodate other language docs, but I can't work out how to make 
     99    # that work and I think it'll require Sphinx 0.5 anyway. 
     100    # 
     101    version_text = { 
     102        'deprecated':       'Deprecated in Django %s', 
     103        'versionchanged':   'Changed in Django %s', 
     104        'versionadded':     'New in Django %s', 
     105    } 
     106     
     107    def visit_versionmodified(self, node): 
     108        self.body.append( 
     109            self.starttag(node, 'div', CLASS=node['type']) 
     110        ) 
     111        title = "%s%s" % ( 
     112            self.version_text[node['type']] % node['version'], 
     113            len(node) and ":" or "." 
     114        ) 
     115        self.body.append('<span class="title">%s</span> ' % title) 
     116     
     117    def depart_versionmodified(self, node): 
     118        self.body.append("</div>\n") 
    91119     
    92120    # Give each section a unique ID -- nice for custom CSS hooks 

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

    r8506 r8843  
    44==================================== 
    55 
    6 **New in Django development version** 
     6.. versionadded:: 1.0 
    77 
    88Applications can register their own actions with ``manage.py``. For example, 

  • django/trunk/docs/howto/custom-model-fields.txt

    r8616 r8843  
    55=========================== 
    66 
    7 **New in Django development version** 
     7.. versionadded:: 1.0 
    88 
    99Introduction 

  • django/trunk/docs/howto/custom-template-tags.txt

    r8828 r8843  
    158158~~~~~~~~~~~~~~~~~~~~~~~~~ 
    159159 
    160 **New in Django development version** 
     160.. versionadded:: 1.0 
    161161 
    162162When writing a custom filter, give some thought to how the filter will interact 
    …… 
    423423~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
    424424 
    425 **New in Django development version** 
     425.. versionadded:: 1.0 
    426426 
    427427The output from template tags is **not** automatically run through the 
    …… 
    548548format it accordingly. 
    549549 
    550 .. admonition:: New in development version: 
     550.. versionadded:: 1.0 
    551551 
    552552    Variable resolution has changed in the development version of Django. 

  • django/trunk/docs/howto/deployment/modpython.txt

    r8506 r8843  
    5050<django-settings-module>` so mod_python knows which settings to use. 
    5151 
    52 **New in Django development version:** Because mod_python does not know we are 
     52.. versionadded:: 1.0 
     53    The ``PythonOption django.root ...`` is new in this version. 
     54 
     55Because mod_python does not know we are 
    5356serving this site from underneath the ``/mysite/`` prefix, this value needs to 
    5457be passed through to the mod_python handler in Django, via the ``PythonOption 

  • django/trunk/docs/index.txt

    r8735 r8843  
    8484    * :ref:`topics-signals` 
    8585    * :ref:`topics-testing` 
     86    * :ref:`topics-http-sessions` 
    8687     
    8788Add-on ("contrib") applications 

  • django/trunk/docs/internals/contributing.txt

    r8731 r8843  
    573573      framework since the last release. 
    574574 
    575 Our philosophy is that "general improvements" are something that *all* current 
    576 Django users should benefit from, including users of trunk *and* users of the 
    577 latest release. Hence, the documentation section on djangoproject.com points 
    578 people by default to the newest versions of the docs, because they have the 
    579 latest and greatest content. (In fact, the Web site pulls directly from the 
    580 Subversion repository, converting to HTML on the fly.) 
    581  
    582 But this decision to feature bleeding-edge documentation has one large caveat: 
    583 any documentation of *new* features will be seen by Django users who don't 
    584 necessarily have access to those features yet, because they're only using the 
    585 latest release. Thus, our policy is: 
     575Our policy is: 
    586576 
    587577    **All documentation of new features should be written in a way that clearly 
    …… 
    590580    development version.** 
    591581 
    592 Our traditional way of marking new features is by prefacing the features' 
    593 documentation with: "New in Django development version." Changes aren't 
    594 *required* to include this exact text, but all documentation of new features 
    595 should include the phrase "development version," so we can find and remove 
    596 those phrases for the next release. 
     582Our prefered way for marking new features is by prefacing the features' 
     583documentation with: ".. versionadded:: X.Y", followed by an optional one line 
     584comment and a mandatory blank line. 
     585 
     586General improvements, or other changes to the APIs that should be emphasised 
     587should use the ".. versionchanged:: X.Y" directive (with the same format as the 
     588``versionadded`` mentioned above. 
    597589 
    598590Guidelines for ReST files 

  • django/trunk/docs/intro/tutorial01.txt

    r8506 r8843  
    115115    0 errors found. 
    116116 
    117     Django version 0.96, using settings 'mysite.settings' 
     117    Django version 1.0, using settings 'mysite.settings' 
    118118    Development server is running at http://127.0.0.1:8000/ 
    119     Quit the server with CONTROL-C (Unix) or CTRL-BREAK (Windows). 
     119    Quit the server with CONTROL-C. 
    120120 
    121121You've started the Django development server, a lightweight Web server written 

  • django/trunk/docs/intro/whatsnext.txt

    r8736 r8843  
    217217      documentation in the same Subversion commit transaction. 
    218218 
    219     * To distinguish feature changes/additions in the docs, we use the phrase 
    220       **New in Django development version**. In practice, this means that the 
    221       current documentation on djangoproject.com can be used by users of either 
    222       the latest release *or* the development version. 
     219    * To distinguish feature changes/additions in the docs, we use the phrase: 
     220      "New in version X.Y", being X.Y the next release version (hence, the one 
     221      being developed). 
    223222 
    224223    * Documentation for a particular Django release is frozen once the version 

  • django/trunk/docs/ref/contrib/flatpages.txt

    r8506 r8843  
    2020template. It can be associated with one, or multiple, sites. 
    2121 
    22 **New in Django development version** 
     22.. versionadded:: 1.0 
    2323 
    2424The content field may optionally be left blank if you prefer to put your  

  • django/trunk/docs/ref/contrib/formtools/form-wizard.txt

    r8506 r8843  
    88    :synopsis: Splits forms across multiple Web pages. 
    99 
    10 **New in Django development version.** 
     10.. versionadded:: 1.0 
    1111 
    1212Django comes with an optional "form wizard" application that splits 

  • django/trunk/docs/ref/contrib/humanize.txt

    r8506 r8843  
    7575---------- 
    7676 
    77 **New in Django development version** 
     77.. versionadded:: 1.0 
    7878 
    7979For dates that are the current day or within one day, return "today", 

  • django/trunk/docs/ref/contrib/index.txt

    r8557 r8843  
    6060======== 
    6161 
    62 **New in Django development version.** 
     62.. versionchanged:: 1.0 
     63   The comments application has been rewriten. See :ref:`ref-contrib-comments-upgrade` 
     64   for information on howto upgrade. 
    6365 
    6466A simple yet flexible comments system. See :ref:`ref-contrib-comments-index`. 

  • django/trunk/docs/ref/contrib/sitemaps.txt

    r8754 r8843  
    343343------------------------------ 
    344344 
    345 **New in Django development version** 
     345.. versionadded:: 1.0 
    346346 
    347347Once the sitemaps application is added to your project, you may also 

  • django/trunk/docs/ref/contrib/sites.txt

    r8506 r8843  
    231231=================================== 
    232232 
    233 **New in Django development version** 
     233.. versionadded:: 1.0 
    234234 
    235235As the current site is stored in the database, each call to 
    …… 
    380380.. _requestsite-objects: 
    381381 
    382 **New in Django development version** 
     382.. versionadded:: 1.0 
    383383 
    384384Some :ref:`django.contrib <ref-contrib-index>` applications take advantage of 

  • django/trunk/docs/ref/contrib/syndication.txt

    r8512 r8843  
    266266      a 404 error for that request. 
    267267 
    268       **New in Django development version:** The :meth:`get_object()` method 
    269       also has a chance to handle the :file:`/rss/beats/` url. In this case, 
    270       :data:`bits` will be an empty list. In our example, ``len(bits) != 1`` and 
    271       an :exc:`ObjectDoesNotExist` exception will be raised, so 
     268      .. versionadded:: 1.0 
     269         meth:`get_object()` can handle the :file:`/rss/beats/` url. 
     270 
     271      The :meth:`get_object()` method also has a chance to handle the 
     272      :file:`/rss/beats/` url. In this case, :data:`bits` will be an 
     273      empty list. In our example, ``len(bits) != 1`` and an 
     274      :exc:`ObjectDoesNotExist` exception will be raised, so 
    272275      :file:`/rss/beats/` will generate a 404 page. But you can handle this case 
    273276      however you like. For example, you could generate a combined feed for all 
    …… 
    477480        # (where it is the feed-level ID element). If not provided, the feed 
    478481        # link is used as the ID. 
    479         # 
    480         # (New in Django development version) 
    481482 
    482483        def feed_guid(self, obj): 
    …… 
    653654        # only used for Atom feeds (it is the ID element for an item in an 
    654655        # Atom feed). If not provided, the item's link is used by default. 
    655         # 
    656         # (New in Django development version) 
    657656 
    658657        def item_guid(self, obj): 

  • django/trunk/docs/ref/databases.txt

    r8792 r8843  
    316316it would be stored in the model tablespace ``tables`` by default. 
    317317 
    318 **New in the Django development version:** Use the :setting:`DEFAULT_TABLESPACE` 
    319 and :setting:`DEFAULT_INDEX_TABLESPACE` settings to specify default values for 
    320 the db_tablespace options. These are useful for setting a tablespace for the 
    321 built-in Django apps and other applications whose code you cannot control. 
     318.. versionadded:: 1.0 
     319 
     320Use the :setting:`DEFAULT_TABLESPACE` and :setting:`DEFAULT_INDEX_TABLESPACE` 
     321settings to specify default values for the db_tablespace options. 
     322These are useful for setting a tablespace for the built-in Django apps and 
     323other applications whose code you cannot control. 
    322324 
    323325Django does not create the tablespaces for you. Please refer to `Oracle's 

  • django/trunk/docs/ref/django-admin.txt

    r8740 r8843  
    9999------- 
    100100 
    101 **New in Django development version** 
     101.. versionadded:: 1.0 
    102102 
    103103Can be run as a cronjob or directly to clean out old data from the database 
    …… 
    107107--------------- 
    108108 
    109 **New in Django development version** 
     109.. versionchanged:: 1.0 
     110   Before 1.0 this was the "bin/compile-messages.py" command. 
    110111 
    111112Compiles .po files created with ``makemessages`` to .mo files for use with 
    …… 
    135136.. django-admin:: createsuperuser  
    136137 
    137 **New in Django development version** 
     138.. versionadded:: 1.0 
    138139 
    139140Creates a superuser account (a user who has all permissions). This is 
    …… 
    210211.. django-admin-option:: --exclude 
    211212 
    212 **New in Django development version** 
     213.. versionadded:: 1.0 
    213214 
    214215Exclude a specific application from the applications whose contents is 
    …… 
    384385------------ 
    385386 
    386 **New in Django development version** 
     387.. versionchanged:: 1.0 
     388   Before 1.0 this was the "bin/make-messages.py" command. 
    387389 
    388390Runs over the entire source tree of the current directory and pulls out all 
    …… 
    735737-------------------------------- 
    736738 
    737 **New in Django development version** 
     739.. versionadded:: 1.0 
    738740 
    739741Runs a Django development server (as in ``runserver``) using data from the 

  • django/trunk/docs/ref/forms/api.txt

    r8506 r8843  
    158158    {'cc_myself': True, 'message': u'Hi there', 'sender': u'foo@example.com', 'subject': u'hello'} 
    159159 
    160 .. note:: 
    161     **New in Django development version** The ``cleaned_data`` attribute was 
    162     called ``clean_data`` in earlier releases. 
     160.. versionchanged:: 1.0 
     161    The ``cleaned_data`` attribute was called ``clean_data`` in earlier releases. 
    163162 
    164163Note that any text-based field -- such as ``CharField`` or ``EmailField`` -- 
    …… 
    565564-------------------------------- 
    566565 
    567 **New in Django development version** 
     566.. versionadded:: 1.0 
    568567 
    569568Dealing with forms that have ``FileField`` and ``ImageField`` fields 

  • django/trunk/docs/ref/forms/fields.txt

    r8771 r8843  
    220220~~~~~~~~~~~~~~~~~~ 
    221221 
     222.. versionadded:: 1.0 
     223 
    222224.. attribute:: Field.error_messages 
    223225 
    224 **New in Django development version** 
    225226 
    226227The ``error_messages`` argument lets you override the default messages that the 
    …… 
    315316    * Error message keys: ``required`` 
    316317 
    317 **New in Django development version:** The empty value for a ``CheckboxInput`` 
    318 (and hence the standard ``BooleanField``) has changed to return ``False`` 
    319 instead of ``None`` in the development version. 
     318.. versionchanged:: 1.0 
     319   The empty value for a ``CheckboxInput`` (and hence the standard ``BooleanField``) 
     320   has changed to return ``False`` instead of ``None`` in the development version. 
    320321 
    321322.. note:: 
    …… 
    449450    '%m/%d/%y',              # '10/25/06' 
    450451 
    451 **New in Django development version:** The ``DateTimeField`` used to use a 
    452 ``TextInput`` widget by default. This has now changed. 
     452.. versionchanged:: 1.0 
     453   The ``DateTimeField`` used to use a ``TextInput`` widget by default. This has now changed. 
    453454 
    454455``DecimalField`` 
    455456~~~~~~~~~~~~~~~~ 
    456457 
     458.. versionadded:: 1.0 
     459 
    457460.. class:: DecimalField(**kwargs) 
    458  
    459 **New in Django development version** 
    460461 
    461462    * Default widget: ``TextInput`` 
    …… 
    504505~~~~~~~~~~~~~ 
    505506 
     507.. versionadded:: 1.0 
     508 
    506509.. class:: FileField(**kwargs) 
    507  
    508 **New in Django development version** 
    509510 
    510511    * Default widget: ``FileInput`` 
    …… 
    524525~~~~~~~~~~~~~~~~~ 
    525526 
     527.. versionadded:: 1.0 
     528 
    526529.. class:: FilePathField(**kwargs) 
    527  
    528 **New in Django development version** 
    529530 
    530531    * Default widget: ``Select`` 
    …… 
    570571~~~~~~~~~~~~~~ 
    571572 
     573.. versionadded:: 1.0 
     574 
    572575.. class:: ImageField(**kwargs) 
    573  
    574 **New in Django development version** 
    575576 
    576577    * Default widget: ``FileInput`` 

  • django/trunk/docs/ref/forms/widgets.txt

    r8610 r8843  
    3939.. class:: DateTimeInput 
    4040 
     41    .. versionadded:: 1.0 
     42 
    4143    Date/time input as a simple text box: ``<input type='text' ...>`` 
    42  
    43     **New in Django development version:** 
    4444 
    4545.. class:: Textarea 

  • django/trunk/docs/ref/generic-views.txt

    r8506 r8843  
    199199      default, this is ``False``. 
    200200 
    201     * **New in Django development version:** ``template_object_name``: 
    202       Designates the name of the template variable to use in the template 
    203       context. By default, this is ``'latest'``. 
     201    .. versionadded:: 1.0 
     202 
     203    * ``template_object_name``: Designates the name of the template variable 
     204      to use in the template context. By default, this is ``'latest'``. 
    204205 
    205206**Template name:** 
    …… 
    224225      ``queryset.dates(date_field, 'year')[::-1]``. 
    225226 
     227    .. versionchanged:: 1.0 
     228       The behaviour depending on ``template_object_name`` is new in this version. 
     229 
    226230    * ``latest``: The ``num_latest`` objects in the system, ordered descending 
    227231      by ``date_field``. For example, if ``num_latest`` is ``10``, then 
    228232      ``latest`` will be a list of the latest 10 objects in ``queryset``. 
    229233 
    230       **New in Django development version:** This variable's name depends on 
    231       the ``template_object_name`` parameter, which is ``'latest'`` by default. 
    232       If ``template_object_name`` is ``'foo'``, this variable's name will be 
    233       ``foo``. 
     234      This variable's name depends on the ``template_object_name`` parameter, 
     235      which is ``'latest'`` by default. If ``template_object_name`` is 
     236      ``'foo'``, this variable's name will be ``foo``. 
    234237 
    235238``django.views.generic.date_based.archive_year`` 
    …… 
    734737**Template context:** 
    735738 
     739.. versionadded:: 1.0 
     740   The ``paginator`` and ``page_obj`` context variables are new. 
     741 
    736742In addition to ``extra_context``, the template's context will be: 
    737743 
    …… 
    747753If the results are paginated, the context will contain these extra variables: 
    748754 
    749     * **New in Django development version:** ``paginator``: An instance of 
    750       ``django.core.paginator.Paginator``. 
    751  
    752     * **New in Django development version:** ``page_obj``: An instance of 
    753       ``django.core.paginator.Page``. 
     755    * ``paginator``: An instance of ``django.core.paginator.Paginator``. 
     756 
     757    * ``page_obj``: An instance of ``django.core.paginator.Page``. 
    754758 
    755759Notes on pagination 
    …… 
    779783<topics-pagination>`. 
    780784 
    781 **New in Django development version:**  
     785.. versionadded:: 1.0 
    782786 
    783787As a special case, you are also permitted to use ``last`` as a value for 

  • django/trunk/docs/ref/middleware.txt

    r8791 r8843  
    5555      pattern for ``foo.com/bar/``. 
    5656 
    57       **New in Django development version:** The behavior of 
    58       :setting:`APPEND_SLASH` has changed slightly in the development version. 
    59       It didn't used to check whether the pattern was matched in the URLconf. 
     57      .. versionchanged:: 1.0 
     58         The behavior of :setting:`APPEND_SLASH` has changed slightly in this 
     59         version. It didn't used to check whether the pattern was matched in 
     60         the URLconf. 
    6061 
    6162      If :setting:`PREPEND_WWW` is ``True``, URLs that lack a leading "www." 
    …… 
    176177.. class:: django.contrib.csrf.middleware.CsrfMiddleware 
    177178 
    178 **New in Django development version** 
     179.. versionadded:: 1.0 
    179180 
    180181Adds protection against Cross Site Request Forgeries by adding hidden form 

  • django/trunk/docs/ref/models/fields.txt

    r8830 r8843  
    172172.. attribute:: Field.db_tablespace 
    173173 
    174 **New in Django development version** 
     174.. versionadded:: 1.0 
    175175 
    176176The name of the database tablespace to use for this field's index, if this field 
    …… 
    367367---------------- 
    368368 
    369 **New in Django development version** 
     369.. versionadded:: 1.0 
    370370 
    371371.. class:: DecimalField(max_digits=None, decimal_places=None, [**options]) 
    …… 
    423423    directory). 
    424424     
    425     **New in Django development version** 
     425    .. versionadded:: 1.0 
    426426 
    427427    This may also be a callable, such as a function, which will be called to 
    …… 
    453453.. attribute:: FileField.storage 
    454454 
    455     **New in Django development version.** 
     455    .. versionadded:: 1.0 
    456456     
    457457    Optional. A storage object, which handles the storage and retrieval of your 
    …… 
    500500visiting its URL on your site. Don't allow that. 
    501501 
    502 **New in development version:** By default, :class:`FileField` instances are 
     502.. versionadded:: 1.0 
     503   The ``max_length`` argument was added in this version. 
     504 
     505By default, :class:`FileField` instances are 
    503506created as ``varchar(100)`` columns in your database. As with other fields, you 
    504507can change the maximum length using the :attr:`~CharField.max_length` argument. 
    …… 
    543546(``foo.gif`` and ``bar.gif``). 
    544547 
    545 **New in development version:** By default, :class:`FilePathField` instances are 
     548.. versionadded:: 1.0 
     549   The ``max_length`` argument was added in this version. 
     550 
     551By default, :class:`FilePathField` instances are 
    546552created as ``varchar(100)`` columns in your database. As with other fields, you 
    547553can change the maximum length using the :attr:`~CharField.max_length` argument. 
    …… 
    589595.. _Python Imaging Library: http://www.pythonware.com/products/pil/ 
    590596 
    591 **New in development version:** By default, :class:`ImageField` instances are 
     597.. versionadded:: 1.0 
     598   The ``max_length`` argument was added in this version. 
     599 
     600By default, :class:`ImageField` instances are 
    592601created as ``varchar(100)`` columns in your database. As with other fields, you 
    593602can change the maximum length using the :attr:`~CharField.max_length` argument. 
    …… 
    754763imported from elsewhere. 
    755764 
    756 **New in Django development version:** To refer to models defined in another 
     765.. versionchanged:: 1.0 
     766   Refering models in other applications must include the application label. 
     767 
     768To refer to models defined in another 
    757769application, you must instead explicitly specify the application label. For 
    758770example, if the ``Manufacturer`` model above is defined in another application 

  • django/trunk/docs/ref/models/instances.txt

    r8755 r8843  
    6363~~~~~~~~~~~~~~~~~~~ 
    6464 
    65 **New in Django development version** 
     65.. versionadded:: 1.0 
    6666 
    6767.. attribute:: Model.pk 
    …… 
    173173~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
    174174 
    175 **New in Django development version** 
     175.. versionadded:: 1.0 
    176176 
    177177In some rare circumstances, it's necessary to be able to force the ``save()`` 

  • django/trunk/docs/ref/models/options.txt

    r8757 r8843  
    5656.. attribute:: Options.db_tablespace 
    5757 
    58 **New in Django development version** 
     58.. versionadded:: 1.0 
    5959 
    6060The name of the database tablespace to use for the model. If the backend doesn't 
    …… 
    153153statement). 
    154154 
    155 **New in Django development version** 
     155.. versionadded:: 1.0 
    156156 
    157157For convenience, unique_together can be a single list when dealing with a single 

  • django/trunk/docs/ref/models/querysets.txt

    r8694 r8843  
    377377~~~~~~~~~~ 
    378378 
    379 **New in Django development version** 
     379.. versionadded:: 1.0 
    380380 
    381381Returns an ``EmptyQuerySet`` -- a ``QuerySet`` that always evaluates to 
    …… 
    459459    c = p.hometown       # Requires a database call. 
    460460 
    461 The ``depth`` argument is new in the Django development version. 
     461.. versionadded:: 1.0 
     462   The ``depth`` argument is new in the Django development version. 
    462463 
    463464``extra(select=None, where=None, params=None, tables=None, order_by=None, select_params=None)`` 
    …… 
    519520    subqueries. 
    520521 
    521     **New in Django development version** 
     522    .. versionadded:: 1.0 
     523 
    522524    In some rare cases, you might wish to pass parameters to the SQL fragments 
    523525    in ``extra(select=...)```. For this purpose, use the ``select_params`` 
    …… 
    620622        Entry.objects.extra(where=['headline=%s'], params=['Lennon']) 
    621623 
    622 **New in Django development version** The ``select_params`` argument to 
    623 ``extra()`` is new. Previously, you could attempt to pass parameters for 
    624 ``select`` in the ``params`` argument, but it worked very unreliably. 
    625  
    626624QuerySet methods that do not return QuerySets 
    627625--------------------------------------------- 
    …… 
    854852    SELECT ... WHERE id IS NULL; 
    855853 
    856 **New in Django development version:** The semantics of ``id__exact=None`` have 
    857 changed in the development version. Previously, it was (intentionally) 
    858 converted to ``WHERE id = NULL`` at the SQL level, which would never match 
    859 anything. It has now been changed to behave the same as ``id__isnull=True``. 
     854.. versionchanged:: 1.0 
     855   The semantics of ``id__exact=None`` have 
     856   changed in the development version. Previously, it was (intentionally) 
     857   converted to ``WHERE id = NULL`` at the SQL level, which would never match 
     858   anything. It has now been changed to behave the same as ``id__isnull=True``. 
    860859 
    861860.. admonition:: MySQL comparisons 
    …… 
    11411140~~~~~ 
    11421141 
    1143 **New in Django development version** 
     1142.. versionadded:: 1.0 
    11441143 
    11451144Case-sensitive regular expression match. 
    …… 
    11691168~~~~~~ 
    11701169 
    1171 **New in Django development version** 
     1170.. versionadded:: 1.0 
    11721171 
    11731172Case-insensitive regular expression match. 

  • django/trunk/docs/ref/request-response.txt

    r8733 r8843  
    5050.. attribute:: HttpRequest.encoding 
    5151 
    52     **New in Django development version** 
     52    .. versionadded:: 1.0 
    5353 
    5454    A string representing the current encoding used to decode form submission 
    …… 
    184184.. method:: HttpRequest.get_host() 
    185185 
    186    **New in Django development version** 
     186   .. versionadded:: 1.0 
    187187 
    188188   Returns the originating host of the request using information from the 
    …… 
    203203.. method:: HttpRequest.build_absolute_uri(location) 
    204204 
    205    **New in Django development version** 
     205   .. versionadded:: 1.0 
    206206 
    207207   Returns the absolute URI form of ``location``. If no location is provided, 
    …… 
    221221.. method:: HttpRequest.is_ajax() 
    222222 
    223    **New in Django development version** 
     223   .. versionadded:: 1.0 
    224224 
    225225   Returns ``True`` if the request was made via an ``XMLHttpRequest``, by checking 
    …… 
    449449    ``status`` is the `HTTP Status code`_ for the response. 
    450450 
    451     **(New in Django development version)** ``content_type`` is an alias for 
    452     ``mimetype``. Historically, the parameter was only called ``mimetype``, 
    453     but since this is actually the value included in the HTTP ``Content-Type`` 
    454     header, it can also include the character set encoding, which makes it 
    455     more than just a MIME type specification. If ``mimetype`` is specified 
    456     (not ``None``), that value is used. Otherwise, ``content_type`` is used. If 
    457     neither is given, the ``DEFAULT_CONTENT_TYPE`` setting is used. 
     451    .. versionadded:: 1.0 
     452 
     453    ``content_type`` is an alias for ``mimetype``. Historically, this parameter 
     454    was only called ``mimetype``, but since this is actually the value included 
     455    in the HTTP ``Content-Type`` header, it can also include the character set 
     456    encoding, which makes it more than just a MIME type specification. 
     457    If ``mimetype`` is specified (not ``None``), that value is used. 
     458    Otherwise, ``content_type`` is used. If neither is given, the 
     459    ``DEFAULT_CONTENT_TYPE`` setting is used. 
    458460 
    459461.. method:: HttpResponse.__setitem__(header, value) 
    …… 
    549551.. class:: HttpResponseBadRequest 
    550552 
    551     **New in Django development version.** Acts just like :class:`HttpResponse` 
    552     but uses a 400 status code. 
     553    .. versionadded:: 1.0 
     554 
     555    Acts just like :class:`HttpResponse` but uses a 400 status code. 
    553556 
    554557.. class:: HttpResponseNotFound 

  • django/trunk/docs/ref/settings.txt

    r8640 r8843  
    288288-------------------------- 
    289289 
    290 **New in Django development version** 
     290.. versionadded:: 1.0 
    291291 
    292292Default: ``False`` 
    …… 
    343343------------------ 
    344344 
    345 **New in Django development version** 
     345.. versionadded:: 1.0 
    346346 
    347347Default: ``''`` (Empty string) 
    …… 
    355355------------------------ 
    356356 
    357 **New in Django development version** 
     357.. versionadded:: 1.0 
    358358 
    359359Default: ``''`` (Empty string) 
    …… 
    436436------------- 
    437437 
    438 **New in Django development version** 
     438.. versionadded:: 1.0 
    439439 
    440440Default: ``False`` 
    …… 
    447447------------ 
    448448 
    449 **New in Django development version** 
     449.. versionadded:: 1.0 
    450450 
    451451Default: ``'utf-8'`` 
    …… 
    459459-------------------- 
    460460 
    461 **New in Django development version** 
     461.. versionadded:: 1.0 
    462462 
    463463Default:: 
    …… 
    473473--------------------------- 
    474474 
    475 **New in Django development version** 
     475.. versionadded:: 1.0 
    476476 
    477477Default: ``2621440`` (i.e. 2.5 MB). 
    …… 
    485485-------------------- 
    486486 
    487 **New in Django development version** 
     487.. versionadded:: 1.0 
    488488 
    489489Default: ``None`` 
    …… 
    616616-------------------- 
    617617 
    618 **New in Django development version** 
     618.. versionadded:: 1.0 
    619619 
    620620Default: ``'django_language'`` 
    …… 
    680680------------------ 
    681681 
    682 **New in Django development version** 
     682.. versionadded:: 1.0 
    683683 
    684684Default: ``'/accounts/profile/'`` 
    …… 
    695695--------- 
    696696 
    697 **New in Django development version** 
     697.. versionadded:: 1.0