summaryrefslogtreecommitdiff
path: root/docs/ref/unicode.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/ref/unicode.txt')
-rw-r--r--docs/ref/unicode.txt28
1 files changed, 14 insertions, 14 deletions
diff --git a/docs/ref/unicode.txt b/docs/ref/unicode.txt
index bd5bdc96a9..e5074285e4 100644
--- a/docs/ref/unicode.txt
+++ b/docs/ref/unicode.txt
@@ -47,26 +47,26 @@ You can use Unicode strings, or you can use normal strings (sometimes called
.. versionchanged:: 1.5
-In Python 3, the logic is reversed, that is normal strings are Unicode, and
-when you want to specifically create a bytestring, you have to prefix the
-string with a 'b'. As we are doing in Django code from version 1.5,
-we recommend that you import ``unicode_literals`` from the __future__ library
-in your code. Then, when you specifically want to create a bytestring literal,
-prefix the string with 'b'.
+ In Python 3, the logic is reversed, that is normal strings are Unicode, and
+ when you want to specifically create a bytestring, you have to prefix the
+ string with a 'b'. As we are doing in Django code from version 1.5,
+ we recommend that you import ``unicode_literals`` from the __future__ library
+ in your code. Then, when you specifically want to create a bytestring literal,
+ prefix the string with 'b'.
-Python 2 legacy::
+ Python 2 legacy::
- my_string = "This is a bytestring"
- my_unicode = u"This is an Unicode string"
+ my_string = "This is a bytestring"
+ my_unicode = u"This is an Unicode string"
-Python 2 with unicode literals or Python 3::
+ Python 2 with unicode literals or Python 3::
- from __future__ import unicode_literals
+ from __future__ import unicode_literals
- my_string = b"This is a bytestring"
- my_unicode = "This is an Unicode string"
+ my_string = b"This is a bytestring"
+ my_unicode = "This is an Unicode string"
-See also :doc:`Python 3 compatibility </topics/python3>`.
+ See also :doc:`Python 3 compatibility </topics/python3>`.
.. warning::