Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: Two things may prevent the exception from being seen:
- First, the async exception is not immediate; it is checked every 100 bytecodes (=sys.getcheckinterval()). When testing from the interactive prompt, try something like "for x in range(100): pass". - Then, chances are that the exceptions is actually raised, but silently swallowed somewhere by the interpreter: for example, if the exception is raised from inside a __getattr__ function of some object, when called by hasattr(). SetAsyncExc does not seem very reliable... ---------- nosy: +amaury.forgeotdarc _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1779233> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
