[2.0.x] Refs #29086 -- Doc'd how to detect bytestring mistakes.

Backport of c10cb9716f8fd7398a8206cd8b33ed2f03065f85 from master

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