Skip to content
Browse files

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

git-svn-id: http://code.djangoproject.com/svn/django/trunk@8552 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent f964a6e commit a16988450531aeae9c70e7035311426a91f6d5b9 @jacobian jacobian committed
Showing with 2 additions and 2 deletions.
  1. +1 −1 docs/internals/contributing.txt
  2. +1 −1 docs/topics/db/models.txt
View
2 docs/internals/contributing.txt
@@ -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
View
2 docs/topics/db/models.txt
@@ -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

0 comments on commit a169884

Please sign in to comment.
Something went wrong with that request. Please try again.