[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

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

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Andrew Svetlov added the comment: New changeset 861a9aaf0f517623c58ca4eb5588804b2632fcba by Miss Islington (bot) in branch '3.10': bpo-46278: fix typo introduced in GH-30427 (GH-30430) (GH-30431) https://github.com/python/cpython/commit/861a9aaf0f517623c58ca4eb5588804b2632fcba -- _

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

miss-islington added the comment: New changeset cb0683128b8f413e0f16293752014902d4de4984 by Miss Islington (bot) in branch '3.9': bpo-46278: fix typo introduced in GH-30427 (GH-30430) https://github.com/python/cpython/commit/cb0683128b8f413e0f16293752014902d4de4984 -- _

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by miss-islington : -- pull_requests: +28638 pull_request: https://github.com/python/cpython/pull/30432 ___ Python tracker ___ __

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

miss-islington added the comment: New changeset b50e5e916a05df65ab6a255af7624b751e0fe9d1 by Kumar Aditya in branch 'main': bpo-46278: fix typo introduced in GH-30427 (GH-30430) https://github.com/python/cpython/commit/b50e5e916a05df65ab6a255af7624b751e0fe9d1 --

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by miss-islington : -- pull_requests: +28637 pull_request: https://github.com/python/cpython/pull/30431 ___ Python tracker ___ __

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by miss-islington : -- pull_requests: +28636 pull_request: https://github.com/python/cpython/pull/30429 ___ Python tracker ___ __

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by miss-islington : -- nosy: +miss-islington nosy_count: 3.0 -> 4.0 pull_requests: +28635 pull_request: https://github.com/python/cpython/pull/30428 ___ Python tracker _

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by Kumar Aditya : -- pull_requests: +28634 pull_request: https://github.com/python/cpython/pull/30430 ___ Python tracker ___

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Kumar Aditya added the comment: The PR introduced a typo in the method signature see https://github.com/python/cpython/pull/30427#discussion_r779497305 -- nosy: +kumaraditya303 ___ Python tracker __

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

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

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by Andrew Svetlov : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

Change by Andrew Svetlov : -- components: +asyncio nosy: +yselivanov versions: +Python 3.10, Python 3.11, Python 3.9 ___ Python tracker ___

[issue46278] AbstractEventLoop.call_* should reflect the 'context' argument

New submission from Andrew Svetlov : Actual implementations of asyncio event loops (both Unix and Windows) support contextvars and accept `context` argument in `loop.call_*()` methods. Abstract event loop definition doesn't it. It is not a bug but a signature incompatibility that can embarras