Ticket #5955: doc_fixes.diff
| File doc_fixes.diff, 4.3 kB (added by SmileyChris, 1 year ago) |
|---|
-
tutorial01.txt
old new 47 47 denied" when you try to run ``django-admin.py startproject``. This 48 48 is because, on Unix-based systems like OS X, a file must be marked 49 49 as "executable" before it can be run as a program. To do this, open 50 Terminal.app and navigate (using the ` cd` command) to the directory50 Terminal.app and navigate (using the ``cd`` command) to the directory 51 51 where ``django-admin.py`` is installed, then run the command 52 52 ``chmod +x django-admin.py``. 53 53 -
url_dispatch.txt
old new 237 237 ------- 238 238 239 239 A function that takes a full Python import path to another URLconf that should 240 be "included" in this place. See _`Including other URLconfs`below.240 be "included" in this place. See `Including other URLconfs`_ below. 241 241 242 242 Notes on capturing text in URLs 243 243 =============================== -
release_notes_0.96.txt
old new 44 44 DATABASE_ENGINE = "mysql_old" 45 45 46 46 However, we strongly encourage MySQL users to upgrade to a more recent 47 version of ` MySQLdb` as soon as possible, The "mysql_old" backend is47 version of ``MySQLdb`` as soon as possible, The "mysql_old" backend is 48 48 provided only to ease this transition, and is considered deprecated; 49 49 aside from any necessary security fixes, it will not be actively 50 50 maintained, and it will be removed in a future release of Django. -
model-api.txt
old new 50 50 Some technical notes: 51 51 52 52 * The name of the table, ``myapp_person``, is automatically derived from 53 some model metadata but can be overridden. See _`Table names`below.53 some model metadata but can be overridden. See `Table names`_ below. 54 54 * An ``id`` field is added automatically, but this behavior can be 55 55 overriden. See `Automatic primary key fields`_ below. 56 56 * The ``CREATE TABLE`` SQL in this example is formatted using PostgreSQL … … 1664 1664 1665 1665 Adding extra ``Manager`` methods is the preferred way to add "table-level" 1666 1666 functionality to your models. (For "row-level" functionality -- i.e., functions 1667 that act on a single instance of a model object -- use _`Model methods`, not1667 that act on a single instance of a model object -- use `Model methods`_, not 1668 1668 custom ``Manager`` methods.) 1669 1669 1670 1670 A custom ``Manager`` method can return anything you want. It doesn't have to -
authentication.txt
old new 170 170 171 171 If no password is provided, ``set_unusable_password()`` will be called. 172 172 173 See _`Creating users`for example usage.173 See `Creating users`_ for example usage. 174 174 175 175 * ``make_random_password(length=10, allowed_chars='abcdefghjkmnpqrstuvwxyzABCDEFGHJKLMNPQRSTUVWXYZ23456789')`` 176 176 Returns a random password with the given length and given string of -
django-admin.txt
old new 651 651 that it doesn't matter whether the options come before or after the fixture 652 652 arguments.) 653 653 654 To run on 1.2.3.4:7000 with a ` test` fixture::654 To run on 1.2.3.4:7000 with a ``test`` fixture:: 655 655 656 656 django-admin.py testserver --addrport 1.2.3.4:7000 test 657 657 -
templates_python.txt
old new 1136 1136 template that is filled with details from the current object. (In the admin's 1137 1137 case, this is the ``submit_row`` tag.) 1138 1138 1139 These sorts of tags are called `inclusion tags`.1139 These sorts of tags are called inclusion tags. 1140 1140 1141 1141 Writing inclusion tags is probably best demonstrated by example. Let's write a 1142 1142 tag that outputs a list of choices for a given ``Poll`` object, such as was
