Jacob Walls

Thanks for the contribution @zasca!

Thanks for the report, we always appreciate people providing the crash template. We may in the future mark this as a duplicate of #8842.

#8842 has to do with recursion errors during AST build/transform, which we should handle in astroid. I'll let this issue be the top-level duplicate for catching RecursionError during inference, which...

From what I can tell it's very close: - some unresolved documentation comments - docs check is failing - TODO statements about yield and asyncwith Happy to give the whole...

> Not sure if I need to change this here Good call, let's not block your work on that. If it hasn't been fixed on main yet, please open an...

#9587 was a duplicate for `g()` in https://github.com/pylint-dev/pylint/issues/8893#issuecomment-1654728749.

Thanks for the report. Tentatively assigning to me, as I'd like to see if we can remove the HTTP brain entirely by just adding support for `@_simple_enum` instead.

There are several places where we could try to trap RecursionError and reraise it as a fatal (but ignorable) message. 1. Inference system 2. Performing astroid transforms (this issue)

`pylance` doesn't crash, but it does admit it can't parse. We can do something similar. ``` Maximum parse depth exceeded; break expression into smaller sub-expressions: Pylance ```

Thanks for the report, we always like to address crashes when we can reproduce them. Unfortunately, with a fresh venv, and with the pylint/astroid/python versions reported, and with as many...