From: Alex Waygood Date: Sun, 8 May 2022 13:23:22 +0000 (+0100) Subject: gh-92417: `stdtypes` docs: delete discussion of Python 2 differences (GH-92423) X-Git-Tag: v3.12.0a1~1646 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=8efda1e7c6343b1671d93837bf2c146e4cf77bbf;p=thirdparty%2FPython%2Fcpython.git gh-92417: `stdtypes` docs: delete discussion of Python 2 differences (GH-92423) Given that 2.7 has now been end-of-life for two and a half years, I don't think we need such a detailed explanation here anymore of the differences between Python 2 and Python 3. --- diff --git a/Doc/library/stdtypes.rst b/Doc/library/stdtypes.rst index 44447400c29b..065afb8ae603 100644 --- a/Doc/library/stdtypes.rst +++ b/Doc/library/stdtypes.rst @@ -2573,16 +2573,6 @@ The representation of bytes objects uses the literal format (``b'...'``) since it is often more useful than e.g. ``bytes([46, 46, 46])``. You can always convert a bytes object into a list of integers using ``list(b)``. -.. note:: - For Python 2.x users: In the Python 2.x series, a variety of implicit - conversions between 8-bit strings (the closest thing 2.x offers to a - built-in binary data type) and Unicode strings were permitted. This was a - backwards compatibility workaround to account for the fact that Python - originally only supported 8-bit text, and Unicode text was a later - addition. In Python 3.x, those implicit conversions are gone - conversions - between 8-bit binary data and Unicode text must be explicit, and bytes and - string objects will always compare unequal. - .. _typebytearray: