You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The experimental python branch has been merged to master. It currently supports some python language features but is far from complete. This issue is supposed to track open todos for the python implementation.
The content you are editing has changed. Please copy your edits and refresh the page.
Several nodes are unhandled in the Python frontend. This Issue is here to track whether we can and have implemented the parser node and what the current Ideas as on how we map these nodes to the current graph(existing nodes or a new node):
The content you are editing has changed. Please copy your edits and refresh the page.
This doesn't work because the Pass dependencies don't allow it.
constant propagation ((multi) value evaluator)
What is expected here? Basic concepts are available (i.e., +, -, etc.) If we need some specific information in a special scenario, we should probably extract this to another evaluator
Field initializes
What should we do here? This needs a more precise description
Slices (DFG)
Task description too imprecise
Match
Basic support/implementation in #1801 . Many of the cases are missing.
The experimental python branch has been merged to master. It currently supports some python language features but is far from complete. This issue is supposed to track open todos for the python implementation.
Tasks
.pyi
) #1640type_comments
#1649async
functions #1651Python.AST.type_ignore
seems not implemented #1843Several nodes are unhandled in the Python frontend. This Issue is here to track whether we can and have implemented the parser node and what the current Ideas as on how we map these nodes to the current graph(existing nodes or a new node):
Tasks (StatementHandler)
global
keyword #1712nonlocal
keyword #1713Raise
in python #1710try
with all things #1704With
#1711orElse
branch all constructs, e.g. for-loops #1718The text was updated successfully, but these errors were encountered: