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 Mark.Shannon
Recipients Mark.Shannon, lukasz.langa, scoder, serhiy.storchaka, v2m, yselivanov
Date 2020-09-21.10:50:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

Why was the PR merged with a new API function `PyGen_Send`?

I explicitly said that any new API function should *not* start with `PyGen`, nor should any function rely on generators and async "coroutines" sharing the same memory layout.

If you disagree with me, please say why, don't just merge the PR.

The name `PyGen` is misleading as it can handle coroutines as well as generators.
There is no performance advantage to only handling these two types.
Worse, it requires that a `PyCoroObject` can always be cast to a `PyGenObject`, preventing better layout of either object in the future.

Would you revert the PR, please.
Date User Action Args
2020-09-21 10:50:10Mark.Shannonsetrecipients: + Mark.Shannon, scoder, lukasz.langa, serhiy.storchaka, yselivanov, v2m
2020-09-21 10:50:10Mark.Shannonsetmessageid: <>
2020-09-21 10:50:10Mark.Shannonlinkissue41756 messages
2020-09-21 10:50:09Mark.Shannoncreate