8000 [3.9] gh-92417: `stdtypes` docs: delete discussion of Python 2 differ… · hello-adam/cpython@f3731db · GitHub
[go: up one dir, main page]

Skip to content

Commit f3731db

Browse files
miss-islingtonhello-adam
authored andcommitted
[3.9] pythongh-92417: stdtypes docs: delete discussion of Python 2 differences (pythonGH-92423) (pythonGH-92474)
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. (cherry picked from commit 8efda1e) Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> Automerge-Triggered-By: GH:serhiy-storchaka
1 parent 7bb91b9 commit f3731db

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

Doc/library/stdtypes.rst

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2502,16 +2502,6 @@ The representation of bytes objects uses the literal format (``b'...'``)
25022502
since it is often more useful than e.g. ``bytes([46, 46, 46])``. You can
25032503
always convert a bytes object into a li 84D7 st of integers using ``list(b)``.
25042504

2505-
.. note::
2506-
For Python 2.x users: In the Python 2.x series, a variety of implicit
2507-
conversions between 8-bit strings (the closest thing 2.x offers to a
2508-
built-in binary data type) and Unicode strings were permitted. This was a
2509-
backwards compatibility workaround to account for the fact that Python
2510-
originally only supported 8-bit text, and Unicode text was a later
2511-
addition. In Python 3.x, those implicit conversions are gone - conversions
2512-
between 8-bit binary data and Unicode text must be explicit, and bytes and
2513-
string objects will always compare unequal.
2514-
25152505

25162506
.. _typebytearray:
25172507

0 commit comments

Comments
 (0)
0