On Mon, Apr 5, 2010 at 3:03 PM, "Martin v. Löwis" <mar...@v.loewis.de> wrote: >> 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 >
According to docs sys._getframe() is a impl-specific thing, however sys.exc_info() presenting correct interface of it's 3rd result (a traceback) is not. That's at least how I read those docs. Cheers, fijal _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
