Message245552
| Author | ncoghlan |
|---|---|
| Recipients | Ben.Darnell, Yury.Selivanov, asvetlov, gvanrossum, martin.panter, ncoghlan, scoder, vstinner, yselivanov |
| Date | 2015-06-20.08:03:29 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1434787409.59.0.0563805960118.issue24400@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Based on that last comment, I realised there's something else @types.coroutine should now do: delegate both the existing gi_* attributes *and* the new cr_* attributes to the underlying generator.
That should allow all of the poking around in code object flags to be encapsulated entirely in the types module, as the 3 kinds of object would subsequently be distinguishable by their attributes:
gi_running: generator-iterator or generator-as-coroutine
cr_running: native coroutine or generator-as-coroutine
both: generator-as-coroutine |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-06-20 08:03:29 | ncoghlan | set | recipients: + ncoghlan, gvanrossum, scoder, vstinner, asvetlov, Yury.Selivanov, Ben.Darnell, martin.panter, yselivanov |
| 2015-06-20 08:03:29 | ncoghlan | set | messageid: <1434787409.59.0.0563805960118.issue24400@psf.upfronthosting.co.za> |
| 2015-06-20 08:03:29 | ncoghlan | link | issue24400 messages |
| 2015-06-20 08:03:29 | ncoghlan | create | |