Message246152
| Author |
ncoghlan |
| Recipients |
Ben.Darnell, Yury.Selivanov, asvetlov, gvanrossum, martin.panter, ncoghlan, python-dev, r.david.murray, scoder, vstinner, yselivanov |
| Date |
2015年07月03日.08:46:53 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1435913213.5.0.976354741947.issue24400@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Sorry, I forgot to state my main conclusion in comparing the consequences of adding "inspect.isawaitable" vs adding an API specifically for checking "isn't Awaitable, but can be used in an await expression":
I think we should add "inspect.isawaitable()", and have it pass for *anything* that can be used in an await expression (whether that's by implementing the Awaitable protocol, or due to special casing at the interpreter level). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2015年07月03日 08:46:53 | ncoghlan | set | recipients:
+ ncoghlan, gvanrossum, scoder, vstinner, r.david.murray, asvetlov, Yury.Selivanov, python-dev, Ben.Darnell, martin.panter, yselivanov |
| 2015年07月03日 08:46:53 | ncoghlan | set | messageid: <1435913213.5.0.976354741947.issue24400@psf.upfronthosting.co.za> |
| 2015年07月03日 08:46:53 | ncoghlan | link | issue24400 messages |
| 2015年07月03日 08:46:53 | ncoghlan | create |
|