[issue41396] pystate.c:_PyCrossInterpreterData_Release() does not clear py exception on error
New submission from Tomasz Pytel : The call to _PyInterpreterState_LookUpID() may generate a Python exception but it is not explicitly cleared on error and no indicator is returned to signal failure. This can lead to a "a function returned a result with an error set" fatal error, and does in fact do so in a case I encountered in Modules/_xxsubinterpreters.c:channel_destroy(). -- components: Interpreter Core messages: 374270 nosy: Tomasz Pytel priority: normal severity: normal status: open title: pystate.c:_PyCrossInterpreterData_Release() does not clear py exception on error type: behavior versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue41396> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41079] _PyAsyncGenWrappedValue_Type is never Readied
New submission from Tomasz Pytel : A call is never made to PyType_Ready(&_PyAsyncGenWrappedValue_Type) on initialization unlike for all other Python type objects I can see. Does not seem to have any negative effects at the moment except to mess up my Python type instrumentation. May turn into a bug in the future if all types are assumed readied, is this intended behavior? -- components: Interpreter Core messages: 372099 nosy: Tomasz Pytel priority: normal severity: normal status: open title: _PyAsyncGenWrappedValue_Type is never Readied type: behavior versions: Python 3.9 ___ Python tracker <https://bugs.python.org/issue41079> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40779] incorrect end column for single argument generator function call AST
Tomasz Pytel added the comment: I am on 3.8.1 and you are right this is the same as #39235 so please disregard. -- ___ Python tracker <https://bugs.python.org/issue40779> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40779] incorrect end column for single argument generator function call AST
New submission from Tomasz Pytel : When calling a function with a single argument which is an unparenthesized generator expression the end column for the AST node is incorrect, it is one greater than the start of the function call parentheses where I assume it should be one past the closing parentheses. This call: func(i for i in range(3)) Generates the following node for the generator expression (line:col_offset -> end_line:end_col_offset): <_ast.GeneratorExp object at 0x7f3ba61f78c0> .. 1:4 -> 1:5 -- components: Interpreter Core messages: 369982 nosy: Tomasz Pytel priority: normal severity: normal status: open title: incorrect end column for single argument generator function call AST versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue40779> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue40502] PyNode_New() does not initialize n->n_col_offset
New submission from Tomasz Pytel : I found this by accident by compiling empty strings since I use column information from the AST tree, if not initialized I get a starting column of -842150451. The easy fix is to initialize n->n_col_offset = 0; in Parser/node.c:PyNode_New(). -- components: Interpreter Core messages: 368074 nosy: Tomasz Pytel priority: normal severity: normal status: open title: PyNode_New() does not initialize n->n_col_offset versions: Python 3.9 ___ Python tracker <https://bugs.python.org/issue40502> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
