[issue32643] Make Task._step, Task._wakeup and Future._schedule_callback methods private

Change by Yury Selivanov : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue32643] Make Task._step, Task._wakeup and Future._schedule_callback methods private

Yury Selivanov added the comment: New changeset 22feeb88b473b288950cdb2f6c5d28692274b5f9 by Yury Selivanov in branch 'master': bpo-32643: Drop support for a few private Task and Future APIs. (#5293)

[issue32643] Make Task._step, Task._wakeup and Future._schedule_callback methods private

Change by Chris Jerdonek : -- nosy: +chris.jerdonek ___ Python tracker ___ ___

[issue32643] Make Task._step, Task._wakeup and Future._schedule_callback methods private

Change by Yury Selivanov : -- keywords: +patch pull_requests: +5140 stage: -> patch review ___ Python tracker ___

[issue32643] Make Task._step, Task._wakeup and Future._schedule_callback methods private

New submission from Yury Selivanov : I propose to drop support for overloading Task._step, Task._wakeup, and Future._schedule_callbacks. This makes the implementation easier for us to maintain and optimize. It also makes it easier for alternative asyncio event loops and