summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>2008-12-03 04:18:17 (GMT)
committerGuido van Rossum <guido@python.org>2008-12-03 04:18:17 (GMT)
commitb768d4f759bf8677fac8f6eae4f720be02dc6d78 (patch)
treefd4b31c338ce75a6a243e46bccfbe0632335625c
parentfedd14051b4f48cd3b49ccf8d2feab832908f55d (diff)
downloadcpython-b768d4f759bf8677fac8f6eae4f720be02dc6d78.zip
cpython-b768d4f759bf8677fac8f6eae4f720be02dc6d78.tar.gz
cpython-b768d4f759bf8677fac8f6eae4f720be02dc6d78.tar.bz2
Fix bad markup.
-rw-r--r--Doc/whatsnew/3.0.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/whatsnew/3.0.rst b/Doc/whatsnew/3.0.rst
index c195f53..2c2e168 100644
--- a/Doc/whatsnew/3.0.rst
+++ b/Doc/whatsnew/3.0.rst
@@ -221,10 +221,10 @@ changed.
hold text is :class:`str`, the type used to hold data is
:class:`bytes`. The biggest difference with the 2.x situation is
that any attempt to mix text and data in Python 3.0 raises
- :ext:`TypeError`, whereas if you were to mix Unicode and 8-bit
+ :exc:`TypeError`, whereas if you were to mix Unicode and 8-bit
strings in Python 2.x, it would work if the 8-bit string happened to
contain only 7-bit (ASCII) bytes, but you would get
- :ext:`UnicodeDecodeError` if it contained non-ASCII values. This
+ :exc:`UnicodeDecodeError` if it contained non-ASCII values. This
value-specific behavior has caused numerous sad faces over the
years.