Everybody,
In order to save myself a major headache I'm hereby accepting PEP 492.
I've been following Yury's efforts carefully and I am fully confident that we're doing the right thing here. There is only so much effort we can put into clarifying terminology and explaining coroutines. Somebody should write a tutorial. (I started to write one, but I ran out of time after just describing basic yield.)
I've given Yury clear instructions to focus on how to proceed -- he's to work with another core dev on getting the implementation ready in time for beta 1 (scheduled for May 24, but I think the target date should be May 19).
The acceptance is provisional in the PEP 411 sense (stretching its meaning to apply to language changes). That is, we reserve the right to change the specification (or even withdraw it, in a worst-case scenario) until 3.6, although I expect we won't need to do this except for some peripheral issues (e.g. the backward compatibility flags).
I now plan to go back to PEP 484 (type hints). Fortunately in that case there's not much *implementation* that will land (just the typing.py module), but there's still a lot of language in the PEP that needs updating (check the PEP 484 tracker https://github.com/ambv/typehinting/issues).
I totally forgot to publicly congratulate Yury on this PEP. He's put a huge effort into writing the PEP and the implementation and managing the discussion, first on python-ideas, later on python-dev. Congrats, Yury! And thanks for your efforts. Godspeed.
On Tue, May 5, 2015 at 4:53 PM, Guido van Rossum guido@python.org wrote:
Everybody,
In order to save myself a major headache I'm hereby accepting PEP 492.
I've been following Yury's efforts carefully and I am fully confident that we're doing the right thing here. There is only so much effort we can put into clarifying terminology and explaining coroutines. Somebody should write a tutorial. (I started to write one, but I ran out of time after just describing basic yield.)
I've given Yury clear instructions to focus on how to proceed -- he's to work with another core dev on getting the implementation ready in time for beta 1 (scheduled for May 24, but I think the target date should be May 19).
The acceptance is provisional in the PEP 411 sense (stretching its meaning to apply to language changes). That is, we reserve the right to change the specification (or even withdraw it, in a worst-case scenario) until 3.6, although I expect we won't need to do this except for some peripheral issues (e.g. the backward compatibility flags).
I now plan to go back to PEP 484 (type hints). Fortunately in that case there's not much *implementation* that will land (just the typing.py module), but there's still a lot of language in the PEP that needs updating (check the PEP 484 tracker https://github.com/ambv/typehinting/issues).
-- --Guido van Rossum (python.org/~guido)
On 6 May 2015 at 00:58, Guido van Rossum guido@python.org wrote:
I totally forgot to publicly congratulate Yury on this PEP. He's put a huge effort into writing the PEP and the implementation and managing the discussion, first on python-ideas, later on python-dev. Congrats, Yury! And thanks for your efforts. Godspeed.
Agreed, congratulations! There's been a lot of debate on this PEP, and Yury has done a great job of responding where needed and keeping things on track, which can't have been easy. Thanks for all the work.
Paul.
Congrats, Yury!
On Wed, May 6, 2015 at 11:07 AM, Paul Moore p.f.moore@gmail.com wrote:
On 6 May 2015 at 00:58, Guido van Rossum guido@python.org wrote:
I totally forgot to publicly congratulate Yury on this PEP. He's put a huge effort into writing the PEP and the implementation and managing the discussion, first on python-ideas, later on python-dev. Congrats, Yury! And thanks for your efforts. Godspeed.
Agreed, congratulations! There's been a lot of debate on this PEP, and Yury has done a great job of responding where needed and keeping things on track, which can't have been easy. Thanks for all the work.
Paul. _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/andrew.svetlov%40gmail.co...
Thank you Yuri for the all process (PEP+code+handle debate).
It's the first time I follow the genesis of a PEP, from the idea to the acceptation, it was very instructive to me.
-- Ludovic Gasc (GMLudo) http://www.gmludo.eu/
2015-05-06 1:58 GMT+02:00 Guido van Rossum guido@python.org:
I totally forgot to publicly congratulate Yury on this PEP. He's put a huge effort into writing the PEP and the implementation and managing the discussion, first on python-ideas, later on python-dev. Congrats, Yury! And thanks for your efforts. Godspeed.
On Tue, May 5, 2015 at 4:53 PM, Guido van Rossum guido@python.org wrote:
Everybody,
In order to save myself a major headache I'm hereby accepting PEP 492.
I've been following Yury's efforts carefully and I am fully confident that we're doing the right thing here. There is only so much effort we can put into clarifying terminology and explaining coroutines. Somebody should write a tutorial. (I started to write one, but I ran out of time after just describing basic yield.)
I've given Yury clear instructions to focus on how to proceed -- he's to work with another core dev on getting the implementation ready in time for beta 1 (scheduled for May 24, but I think the target date should be May 19).
The acceptance is provisional in the PEP 411 sense (stretching its meaning to apply to language changes). That is, we reserve the right to change the specification (or even withdraw it, in a worst-case scenario) until 3.6, although I expect we won't need to do this except for some peripheral issues (e.g. the backward compatibility flags).
I now plan to go back to PEP 484 (type hints). Fortunately in that case there's not much *implementation* that will land (just the typing.py module), but there's still a lot of language in the PEP that needs updating (check the PEP 484 tracker https://github.com/ambv/typehinting/issues).
-- --Guido van Rossum (python.org/~guido)
-- --Guido van Rossum (python.org/~guido)
Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/gmludo%40gmail.com
On 2015-05-05 7:53 PM, Guido van Rossum wrote:
Everybody,
In order to save myself a major headache I'm hereby accepting PEP 492.
I've been following Yury's efforts carefully and I am fully confident that we're doing the right thing here. There is only so much effort we can put into clarifying terminology and explaining coroutines. Somebody should write a tutorial. (I started to write one, but I ran out of time after just describing basic yield.)
Thank you, Guido! Yury
Hi,
2015-05-06 1:53 GMT+02:00 Guido van Rossum guido@python.org:
In order to save myself a major headache I'm hereby accepting PEP 492.
Great! Congrats Yury.
I've given Yury clear instructions to focus on how to proceed -- he's to work with another core dev on getting the implementation ready in time for beta 1 (scheduled for May 24, but I think the target date should be May 19).
The implementation takes place at: https://bugs.python.org/issue24017
Yury works at https://github.com/1st1/cpython in git branches.
I already sent a first review. But I don't feel able to review the change on the grammar, parser or things like that.
Victor
On 05/05/2015 04:53 PM, Guido van Rossum wrote:
I've given Yury clear instructions to focus on how to proceed -- he's to work with another core dev on getting the implementation ready in time for beta 1 (scheduled for May 24, but I think the target date should be May 19).
Released on Sunday May 24 means it'll be tagged on Saturday May 23. Please take care that it be checked in by then.
Your friendly neighborhood release manager,
//arry/
-
Andrew Svetlov -
Ethan Furman -
Guido van Rossum -
Larry Hastings -
Ludovic Gasc -
Paul Moore -
Victor Stinner -
Yury Selivanov