diff options
| author | Tim Graham <timograham@gmail.com> | 2018-01-30 19:58:16 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-01-30 19:58:16 -0500 |
| commit | c10cb9716f8fd7398a8206cd8b33ed2f03065f85 (patch) | |
| tree | 7623749c04fdcb08443341c171028a7e79e59876 /docs/releases/2.0.txt | |
| parent | fbc3c29e7cc5b3a3f62f1700af6ba474f05d59eb (diff) | |
Refs #29086 -- Doc'd how to detect bytestring mistakes.
Diffstat (limited to 'docs/releases/2.0.txt')
| -rw-r--r-- | docs/releases/2.0.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/releases/2.0.txt b/docs/releases/2.0.txt index aac9ee429d..2a6b188c06 100644 --- a/docs/releases/2.0.txt +++ b/docs/releases/2.0.txt @@ -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 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 -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 coerce the ``args`` and ``kwargs`` it receives, prior to their placement in |