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
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
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/issue40
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
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_
