➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients Ben.Darnell, Yury.Selivanov, asvetlov, gvanrossum, larry, martin.panter, ncoghlan, python-dev, r.david.murray, scoder, vstinner, yselivanov
Date 2015-07-03.23:07:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7eMrD-F7iTxZwnJPGNtETmXSW1pNrmzBbwVjjptuoFSYw@mail.gmail.com>
In-reply-to <1435963823.96.0.0100655910794.issue24400@psf.upfronthosting.co.za>
Content 
My hypothetical "operator.getfuture()" would be a functional spelling of
"what an await expression does to retrieve a future from an awaitable
object".

Whether that's actually useful is an open question, hence deferring the
idea to 3.6 at the earliest :)
History
Date User Action Args
2015-07-03 23:07:24ncoghlansetrecipients: + ncoghlan, gvanrossum, scoder, vstinner, larry, r.david.murray, asvetlov, Yury.Selivanov, python-dev, Ben.Darnell, martin.panter, yselivanov
2015-07-03 23:07:24ncoghlanlinkissue24400 messages
2015-07-03 23:07:24ncoghlancreate