Django

Code

Changeset 1898

Show
Ignore:
Timestamp:
01/10/06 18:11:29 (3 years ago)
Author:
adrian
Message:

Removed 'Only in Django development version' messages from the docs, because frozen docs for version 0.90 are now available

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • django/trunk/docs/authentication.txt

    r1773 r1898  
    171171--------- 
    172172 
    173 **This only applies to the Django development version.** Previous versions, 
    174 such as Django 0.90, used simple MD5 hashes without password salts. 
     173Previous versions, such as Django 0.90, used simple MD5 hashes without password 
     174salts. 
    175175 
    176176The ``password`` field of a ``User`` object is a string in this format:: 
     
    315315is not anonymous. 
    316316 
    317 **New in the Django development version**: ``user_passes_test()`` takes an 
    318 optional ``login_url`` argument, which lets you specify the URL for your login 
    319 page (``/accounts/login/`` by default). 
     317``user_passes_test()`` takes an optional ``login_url`` argument, which lets you 
     318specify the URL for your login page (``/accounts/login/`` by default). 
    320319 
    321320Example in Python 2.3 syntax:: 
  • django/trunk/docs/cache.txt

    r1815 r1898  
    4949                                    this is multi-process- and thread-safe. 
    5050 
    51     dummy:///                       **New in Django development version.** 
    52                                     Doesn't actually cache; just implements the 
     51    dummy:///                       Doesn't actually cache; just implements the 
    5352                                    cache backend interface and doesn't do 
    5453                                    anything. This is an easy way to turn off 
  • django/trunk/docs/db-api.txt

    r1871 r1898  
    223223---------- 
    224224 
    225 **New in Django development version.** 
    226  
    227225By default, multiple lookups are "AND"ed together. If you'd like to use ``OR`` 
    228226statements in your queries, use the ``complex`` lookup type. 
  • django/trunk/docs/django-admin.txt

    r1518 r1898  
    5555address and password. 
    5656 
    57 **New in Django development version:** You can specify 
    58 ``username email password`` on the command line, for convenient use in shell 
    59 scripts. Example:: 
     57You can specify ``username email password`` on the command line, for convenient 
     58use in shell scripts. Example:: 
    6059 
    6160    django-admin.py createsuperuser john john@example.com mypassword 
  • django/trunk/docs/email.txt

    r1798 r1898  
    119119=========================== 
    120120 
    121 **New in Django development version.** 
    122  
    123121`Header injection`_ is a security exploit in which an attacker inserts extra 
    124122e-mail headers to control the "To:" and "From:" in e-mail messages that your 
  • django/trunk/docs/generic_views.txt

    r1773 r1898  
    130130                             template's context. 
    131131 
    132     ``processors``           **New in Django development version.** A tuple of 
    133                              processors to apply to the ``DjangoContext`` of 
    134                              this view's template. See the `DjangoContext docs`_ 
     132    ``processors``           A tuple of processors to apply to the 
     133                             ``DjangoContext`` of this view's template. See the 
     134                             `DjangoContext docs`_ 
    135135    =======================  ================================================== 
    136136 
     
    151151                                 Defaults to 15. 
    152152 
    153         ``allow_empty``          **New in Django development version.** 
    154                                  If ``False`` and there are no objects to display, 
     153        ``allow_empty``          If ``False`` and there are no objects to display, 
    155154                                 the view will raise a 404 instead of displaying 
    156155                                 an empty index page. ``False`` is default. 
  • django/trunk/docs/request_response.txt

    r1868 r1898  
    152152      a mutable ``QueryDict`` (one that was created via ``copy()``). 
    153153 
    154     * ``__contains__(key)`` -- **New in Django development version.** Returns 
    155       ``True`` if the given key is set. This lets you do, e.g., 
    156       ``if "foo" in request.GET``. 
     154    * ``__contains__(key)`` -- Returns ``True`` if the given key is set. This 
     155      lets you do, e.g., ``if "foo" in request.GET``. 
    157156 
    158157    * ``get(key, default)`` -- Uses the same logic as ``__getitem__()`` above, 
     
    362361 
    363362``HttpResponsePermanentRedirect`` 
    364     **New in Django development version.*** 
    365  
    366363    Like ``HttpResponseRedirect``, but it returns a permanent redirect (HTTP 
    367364    status code 301) instead of a "found" redirect (status code 302). 
  • django/trunk/docs/sessions.txt

    r1793 r1898  
    3636 
    3737    * ``__contains__(key)`` 
    38       **New in Django development version.** Example: ``'fav_color' in request.session`` 
     38      Example: ``'fav_color' in request.session`` 
    3939 
    4040    * ``__getitem__(key)`` 
     
    183183    request.session['foo']['bar'] = 'baz' 
    184184 
    185 **Only available in Django development version.** To change this default 
    186 behavior, set the ``SESSION_SAVE_EVERY_REQUEST`` setting  to ``True``. If 
    187 ``SESSION_SAVE_EVERY_REQUEST`` is ``True``, Django will save the session to the 
    188 database on every single request. 
     185To change this default behavior, set the ``SESSION_SAVE_EVERY_REQUEST`` setting 
     186to ``True``. If ``SESSION_SAVE_EVERY_REQUEST`` is ``True``, Django will save 
     187the session to the database on every single request. 
    189188 
    190189Note that the session cookie is only sent when a session has been created or 
     
    219218------------------- 
    220219 
    221 Default: ``'sessionid'`` (**Django development version.** Previous default was 
    222 ``'hotclub'``, which was deemed too pornish.) 
     220Default: ``'sessionid'`` 
    223221 
    224222The name of the cookie to use for sessions. This can be whatever you want. 
     
    228226 
    229227Default: ``False`` 
    230  
    231 **Only available in Django development version.** 
    232228 
    233229Whether to save the session data on every request. If this is ``False`` 
  • django/trunk/docs/settings.txt

    r1808 r1898  
    526526------------------- 
    527527 
    528 Default: ``'sessionid'`` (**Django development version.** Previous default was 
    529 ``'hotclub'``, which was deemed too pornish.) 
     528Default: ``'sessionid'`` 
    530529 
    531530The name of the cookie to use for sessions. This can be whatever you want. 
     
    557556    "django.core.context_processors.i18n") 
    558557 
    559 **Only available in Django development version.** 
    560  
    561558A tuple of callables that are used to populate the context in ``DjangoContext``. 
    562559These callables take a request object as their argument and return a dictionary 
     
    567564 
    568565Default: ``False`` 
    569  
    570 **Only available in Django development version.** 
    571566 
    572567A boolean that turns on/off template debug mode. If this is ``True``, the fancy 
  • django/trunk/docs/templates_python.txt

    r1871 r1898  
    277277        }, [ip_address_processor]) 
    278278 
    279 Note: The concept of template-context processors is new in the Django 
    280 development version. In Django 0.90, ``DjangoContext`` automatically populates 
    281 the context with all of the values explained below, but it's not possible to 
    282 add and remove processors. 
    283  
    284279Here's what each of the default processors does: 
    285280 
     
    535530------------------------------- 
    536531 
    537 **This section applies to the Django development version.** 
    538  
    539532Custom filters are just Python functions that take one or two arguments: 
    540533 
     
    595588Writing custom template tags 
    596589---------------------------- 
    597  
    598 **This section applies to the Django development version.** 
    599590 
    600591Tags are more complex than filters, because tags can do anything. 
  • django/trunk/docs/templates.txt

    r1525 r1898  
    279279area in your admin to find the list of custom libraries in your installation. 
    280280 
    281 **New in Django development version:** The ``{% load %}`` tag can take multiple 
    282 library names, separated by spaces. Example:: 
     281The ``{% load %}`` tag can take multiple library names, separated by spaces. 
     282Example:: 
    283283 
    284284    {% load comments i18n %} 
     
    500500include 
    501501~~~~~~~ 
    502  
    503 **Only available in Django development version.** 
    504502 
    505503Loads a template and renders it with the current context. This is a way of 
  • django/trunk/docs/url_dispatch.txt

    r1813 r1898  
    5252======= 
    5353 
    54 **This syntax is new in the Django development version.** See "Named groups" 
    55 below if you're using Django 0.90. 
    56  
    5754Here's a sample URLconf:: 
    5855 
     
    111108arguments to a view. 
    112109 
    113 (Note that support for non-named regex groups is a new feature in the Django 
    114 development version. Django 0.90 requires named groups.) 
    115  
    116110In Python regular expressions, the syntax for named regular-expression groups 
    117111is ``(?P<name>pattern)``, where ``name`` is the name of the group and