mirror of
https://github.com/python/cpython.git
synced 2025-07-23 11:15:24 +00:00
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.
This commit is contained in:
parent
4739997e14
commit
8efda1e7c6
1 changed files with 0 additions and 10 deletions
|
@ -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
|
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)``.
|
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:
|
.. _typebytearray:
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue