RetroSearch Browse

Mon Apr 5 23:03:59 CEST 2010 · https://mail.python.org/pipermail/python-dev/2010-April/099091.html

> Is the requirement just the construction of full tracebacks in the
> event of an exception? Because Cython does that right now. In the
> event of an exception, the Python call frames are constructed as the C
> call stack is unwound. I thought Maciej was suggesting that having
> full Python frames for any Python call was part of the semantics,
> which is what we only do in the case of a profiling run. I'm really
> not trying to belabor the point -- but if there's something Cython
> should be doing and isn't, it's always good to hear about it. (Feel
> free to point me to an appropriate section of the docs ...)

I guess being able to do inspect.currentframe() is a "SHOULD"
requirement for Python implementations. It's clear that it will be
difficult to provide, so portable applications SHOULD NOT rely on it
working correctly.

Regards,
Martin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2010-April/099091.html below:

[Python-Dev] python compiler