[issue47167] Allow overriding future-task compliance check in asyncio

Yury Selivanov added the comment: Sorry, I don't like the committed change and I think it should be reverted. Futures and Tasks have a documented `get_loop()` method which simply should be called by Task machinery, without the need to expose (and document) private methods. --

[issue47167] Allow overriding future-task compliance check in asyncio

Andrew Svetlov added the comment: New changeset d4bb38f82bf18b00db3129031ce4969b6f0caab9 by Andrew Svetlov in branch 'main': bpo-47167: Allow overriding a future compliance check in asyncio.Task (GH-32197) https://github.com/python/cpython/commit/d4bb38f82bf18b00db3129031ce4969b6f0caab9

[issue47167] Allow overriding future-task compliance check in asyncio

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

[issue47167] Allow overriding future-task compliance check in asyncio

Change by Andrew Svetlov : -- keywords: +patch pull_requests: +30273 stage: -> patch review pull_request: https://github.com/python/cpython/pull/32197 ___ Python tracker ___

[issue47167] Allow overriding future-task compliance check in asyncio

New submission from Andrew Svetlov : Now asyncio.Task has a strict hardcoded check for futures processes on task's step. Sometimes third-party library [1] wants to replace it with custom logic. Currently it is impossible without implementing the full asyncio.Task replacement from scratch.