test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #8539: fixed PEP references. Thanks, carljm. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@8552 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Jacob Kaplan-Moss 2008-08-25 19:28:57 +00:00
parent f964a6e472
commit a169884505
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/internals/contributing.txt
View File

@ -411,7 +411,7 @@ Coding style
Please follow these coding standards when writing code for inclusion in Django:
* Unless otherwise specified, follow :pep:8.
* Unless otherwise specified, follow :pep:`8`.
You could use a tool like `pep8.py`_ to check for some problems in this
area, but remember that PEP 8 is only a guide, so respect the style of

2
docs/topics/db/models.txt
View File

@ -733,7 +733,7 @@ the resulting rows. For example::
:class:`connection <django.db.backends.DatabaseWrapper>` and
:class:`<django.db.backends.CursorWrapper>` mostly implement the standard Python
DB-API -- see :pep:249 -- with the addition of Django's :ref:`transaction
DB-API -- see :pep:`249` -- with the addition of Django's :ref:`transaction
handling <topics-db-transactions>`. If you're not familiar with the Python
DB-API, note that the SQL statement in :meth:`cursor.execute()
<django.db.backends.CursorWrapper.execute>` uses placeholders, ``"%s"``, rather