[Python-Dev] (Looking for) A Retrospective on the Move to Python 3
Antoine Pitrou
solipsis at pitrou.net
Sat Apr 28 11:50:02 EDT 2018
More information about the Python-Dev mailing list
Sat Apr 28 11:50:02 EDT 2018
- Previous message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
- Next message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 27 Apr 2018 14:13:32 +0200 Victor Stinner <vstinner at redhat.com> wrote: > > I don't think that having Python X.Y which introduces backward > incompatible changes is an issue by itself. We did it multiple times > during the Python 3 cycle: my PEP 446 (non-inheritable file > descriptors) and PEP 475 (retry syscalls interrupted by signals, PEP > co-written with Charles-François Natali) introduced backward > incompatible changes in Python 3.4 and 3.5. You're comparing apples and oranges. PEP 446 and PEP 475 are only noticeable by programmers of low-level system and I/O routines (*I* haven't noticed them, for example, though I did quite a bit of network programming with Python), while the changes introduced by Python 3 affect pretty much everyone, even people who only write small simple scripts. Regards Antoine.
- Previous message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
- Next message (by thread): [Python-Dev] (Looking for) A Retrospective on the Move to Python 3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list