innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed typos in docs/topics/python3.txt

This commit is contained in:
Nik Nyby 2015-06-09 09:36:19 -04:00 committed by Tim Graham
parent 9f825b9e28
commit f67127e0af
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/topics/python3.txt
View File

@ -8,7 +8,7 @@ compatibility layer.
.. _six: http://pythonhosted.org/six/ .. _six: http://pythonhosted.org/six/
This document is primarily targeted at authors of pluggable application This document is primarily targeted at authors of pluggable applications
who want to support both Python 2 and 3. It also describes guidelines that who want to support both Python 2 and 3. It also describes guidelines that
apply to Django's code. apply to Django's code.
@ -149,7 +149,7 @@ result with the system encoding. Conversely, the
In Python 3, there's simply :meth:`~object.__str__`, which must return ``str`` In Python 3, there's simply :meth:`~object.__str__`, which must return ``str``
(text). (text).
(It is also possible to define :meth:`~object.__bytes__`, but Django application (It is also possible to define :meth:`~object.__bytes__`, but Django applications
have little use for that method, because they hardly ever deal with ``bytes``.) have little use for that method, because they hardly ever deal with ``bytes``.)
Django provides a simple way to define :meth:`~object.__str__` and Django provides a simple way to define :meth:`~object.__str__` and
@ -208,7 +208,7 @@ Coding guidelines
================= =================
The following guidelines are enforced in Django's source code. They're also The following guidelines are enforced in Django's source code. They're also
recommended for third-party application who follow the same porting strategy. recommended for third-party applications that follow the same porting strategy.
Syntax requirements Syntax requirements
------------------- -------------------