[issue28920] Dangerous usage of "O" format string in _asynciomodule.c

Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue28920] Dangerous usage of "O" format string in _asynciomodule.c

Roundup Robot added the comment: New changeset f2745b64d8b7 by Victor Stinner in branch '3.6': _asyncio uses _PyObject_CallMethodIdObjArgs() https://hg.python.org/cpython/rev/f2745b64d8b7 -- nosy: +python-dev ___ Python tracker

[issue28920] Dangerous usage of "O" format string in _asynciomodule.c

STINNER Victor added the comment: Minimum patch for Python 3.6: only modify calls using the "O" format. -- keywords: +patch Added file: http://bugs.python.org/file45815/_asyncio.patch ___ Python tracker ___

[issue28920] Dangerous usage of "O" format string in _asynciomodule.c

STINNER Victor added the comment: The issue was in fixed in Python 3.7 with a change made for optimization, not directly to fix this issue: changeset: 105547:b29c719d5992 tag: tip user:Victor Stinner date:Fri Dec 09 14:24:02 2016 +0100 files: Modules/_asynciomod

[issue28920] Dangerous usage of "O" format string in _asynciomodule.c

STINNER Victor added the comment: Previous similar bug in generators: issue #21209. -- ___ Python tracker ___ ___ Python-bugs-list mai

[issue28920] Dangerous usage of "O" format string in _asynciomodule.c

New submission from STINNER Victor: The new _asyncio module of Python 3.6 uses the _PyObject_CallMethodId() function to call functions. This function has a weird behaviour when using the format string "O": if the object is a tuple, the tuple is unpacked. _PyObject_CallMethodId(obj, &PyId_meth,