News for hackers. Stuff that matters.

A comment on Migrating to Python 3 with pleasure. Parent comment

Re:Migrating to Python 3 with pleasure by rtpg on Sunday February 04, 2018 @07:02PM (#16305666)
CPython interates in this fashion since 3.6, but it is not part of the Python spec.

Might be a bit contentious but it's not supposed to be relied upon

[ Parent | on HN ]
Re:Migrating to Python 3 with pleasure by thijsvandien on Sunday February 04, 2018 @07:14PM (#16305704)
It was recently decided that as of 3.7 it will be.

(Source: https://mail.python.org/pipermail/python-dev/2017-December/1...)

[ Parent | on HN ]
Re:Migrating to Python 3 with pleasure by dbcurtis on Sunday February 04, 2018 @11:40PM (#16306635)
Hmmmmmm.... that makes it hard for other implementations. CPython isn't the whole of the Python world. Requirements like that can be problematic for implementations like Micropython, for instance.
[ Parent | on HN ]
Re:Migrating to Python 3 with pleasure by sametmax on Monday February 05, 2018 @01:25AM (#16307003)
They asked people from the Jython, pypy and uPython community if it was ok before doing so.
[ Parent | on HN ]
Re:Migrating to Python 3 with pleasure by jsmeaton on Monday February 05, 2018 @12:04AM (#16306719)
The entire reason they decided to make it a standard rather than keep it as an implementation detail is to make things better for users. It’s not about just looking after cpython.
[ Parent | on HN ]
Re:Migrating to Python 3 with pleasure by lozenge on Monday February 05, 2018 @04:41AM (#16307715)
I suspect the reasoning was with CPython dominating, people would eventually make this assumption in their code, perhaps unintentionally, and reduce compatibility. Better to make it official.
[ Parent | on HN ]
Re:Migrating to Python 3 with pleasure by crdoconnor on Monday February 05, 2018 @04:50AM (#16307754)
The headache that having non-deterministic code causes more than makes up for that.

Among other things this makes writing tests much easier.

[ Parent | on HN ]