scoder

This is unlikely to work or to be useful because Cython will probably enable API usages that the current build environment cannot provide. I think it's reasonable to reject this...

> it's an optimization hint and not an order This. The directive allows us to avoid bounds checks where possible. If we need it for correctness, then we can't avoid...

> what assumptions should be made under `CYTHON_ASSUME_SAFE_MACROS`? It means that (certain) macros cannot fail, specifically macros like `Py*_GET_ITEM()` and some others that use simple inlined code. There's a separate...

You could try if enabling profiling support fixes this.

Cython already has Python tracing support which you could enable and use. Write your own profiling or tracing function and have it print the names of the functions that it...

https://stackoverflow.com/questions/8315389/how-do-i-print-functions-as-they-are-called Stack traces might also "just work" when profiling is enabled, since Cython uses frames for it. If not, then enabling them with a new directive probably isn't difficult.

This also claims to support Cython: https://pypi.org/project/hunter/

Interesting. Might be a CPython issue then, if the inittab mechanism cannot handle this. Given that there's something broken that we cannot immediately solve ourselves, it seems ok to put...

Quite possible. The `Grammar` file hasn't been kept up to date for a while, and also was never really completed. It's mostly a modified version of CPython's own grammar (as...

BTW, any future grammar generated parser for Cython should probably be based on CPython's PEG parser generator rather than the current one. See [PEP-617](https://www.python.org/dev/peps/pep-0617/), [pegen](https://github.com/gvanrossum/pegen) and the new [PEG parser...