compare the following:

```
if False: 'foo'(1)
```


$ python3.9
Python 3.9.0a5 (default, Mar 23 2020, 23:11:30) 
[GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ast
>>> ast.parse(b"if False: 'foo'(1)")
<ast.Module object at 0x7ff87a03cca0>
>>> if False: 'foo'(1)
... 
<stdin>:1: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?


even with `PYTHONWARNINGS=error` no warning / error is raised

This is probably because that these warnings raised during code generation, rather then AST Validation / generation.

It is not a bug. Execution includes more stages than ast.parse().

I would really like to be able to trigger all warnings consistently and statically without executing the code.

This is useful (for instance) for this simple script which validates the ast: https://github.com/pre-commit/pre-commit-hooks/blob/master/pre_commit_hooks/check_ast.py

when run with PYTHONWARNINGS=error I get nice error reports for things such as invalid escape sequence, but I do not get them for string-call which I would like to

This does seem like a bug and prematurely closed, I'm a bit disappointed in the current resolution

> This does seem like a bug and prematurely closed, I'm a bit disappointed in the current resolution

I would love to see it moved as a new step in the execution pipeline that we cane extend easily and use externally (like PyAST_Validate). But I'm not sure if the burden worths the gain. Though, for the current version it would be very simple to implement such checks (3-4) with a simple NodeVisitor. Just an example (should be pretty close to output, not exact): https://github.com/isidentical/astvalidate/blob/master/astvalidate/validators/syntatical.py

Compilation includes the following stages:

1. Tokenizing.
2. Creating CST (concrete syntax tree).
3. Creating AST (abstract syntax tree).
4. Optimizing AST.
5. Building symtable.
6. Generating bytecode.
7. Optimizing bytecode.

ast.parse() only includes stages 1-3. Many warnings and errors can be raised at stages 5 and 6 (for example errors for "break" outside of a loop and "unlocal" at module level). If you want to get all warnings and errors, use compile().