[Python-Dev] python compiler
"Martin v. Löwis"
martin at v.loewis.de
Mon Apr 5 23:03:59 CEST 2010
More information about the Python-Dev mailing list
Mon Apr 5 23:03:59 CEST 2010
- Previous message: [Python-Dev] python compiler
- Next message: [Python-Dev] python compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 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
- Previous message: [Python-Dev] python compiler
- Next message: [Python-Dev] python compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list