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

Refs #29086 -- Doc'd how to detect bytestring mistakes.

This commit is contained in:
Tim Graham 2018-01-30 19:58:16 -05:00 committed by GitHub
parent fbc3c29e7c
commit c10cb9716f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/releases/2.0.txt
View File

@ -349,7 +349,8 @@ bytestrings and unicode strings. Now that Python 2 support is dropped,
bytestrings should only be encountered around input/output boundaries (handling bytestrings should only be encountered around input/output boundaries (handling
of binary fields or HTTP streams, for example). You might have to update your of binary fields or HTTP streams, for example). You might have to update your
code to limit bytestring usage to a minimum, as Django no longer accepts code to limit bytestring usage to a minimum, as Django no longer accepts
bytestrings in certain code paths. bytestrings in certain code paths. Python's :option:`-b` option may help detect
that mistake in your code.
For example, ``reverse()`` now uses ``str()`` instead of ``force_text()`` to For example, ``reverse()`` now uses ``str()`` instead of ``force_text()`` to
coerce the ``args`` and ``kwargs`` it receives, prior to their placement in coerce the ``args`` and ``kwargs`` it receives, prior to their placement in