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 | yselivanov |
|---|---|
| Recipients | bennoleslie, ethan.furman, fwierzbicki, larry, martin.panter, ncoghlan, scoder, yselivanov |
| Date | 2015年06月24日.17:06:11 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1435165571.19.0.154288945243.issue24450@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Larry, what's your opinion on this? cr_await is a new thing (trivial on the C level) on a new type, it shouldn't break anything. gi_yieldfrom is identical to cr_await. Can we add this to 3.5? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015年06月24日 17:06:11 | yselivanov | set | recipients: + yselivanov, ncoghlan, scoder, larry, fwierzbicki, ethan.furman, martin.panter, bennoleslie |
| 2015年06月24日 17:06:11 | yselivanov | set | messageid: <1435165571.19.0.154288945243.issue24450@psf.upfronthosting.co.za> |
| 2015年06月24日 17:06:11 | yselivanov | link | issue24450 messages |
| 2015年06月24日 17:06:11 | yselivanov | create | |