Movatterモバイル変換

[Python-Dev] Accepting PEP 492 (async/await)

• Previous message (by thread):[Python-Dev] PEP 492: async/await in Python; version 5
• Next message (by thread):[Python-Dev] Accepting PEP 492 (async/await)
• Messages sorted by:[ date ][ thread ][ subject ][ author ]

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 thatwe're doing the right thing here. There is only so much effort we can putinto clarifying terminology and explaining coroutines. Somebody shouldwrite a tutorial. (I started to write one, but I ran out of time after justdescribing basic yield.)I've given Yury clear instructions to focus on how to proceed -- he's towork with another core dev on getting the implementation ready in time forbeta 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 meaningto apply to language changes). That is, we reserve the right to change thespecification (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 peripheralissues (e.g. the backward compatibility flags).I now plan to go back to PEP 484 (type hints). Fortunately in that casethere's not much *implementation* that will land (just the typing.pymodule), 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)-------------- next part --------------An HTML attachment was scrubbed...URL: <http://mail.python.org/pipermail/python-dev/attachments/20150505/15c8add8/attachment-0001.html>

• Previous message (by thread):[Python-Dev] PEP 492: async/await in Python; version 5
• Next message (by thread):[Python-Dev] Accepting PEP 492 (async/await)
• Messages sorted by:[ date ][ thread ][ subject ][ author ]