RetroSearch Browse

Sat Apr 28 11:50:02 EDT 2018 · https://mail.python.org/pipermail/python-dev/2018-April/153239.html

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.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2018-April/153239.html below:

[Python-Dev] (Looking for) A Retrospective on the Move to Python 3