New submission from Armin Rigo: It's not possible to write a settrace() or setprofile() function that remains active if we're about to run out of stack. If we are, we get a RuntimeError when the function is called. The RuntimeError is normally propagated, but in case it is eaten (e.g. see example) then the program continues to run normally --- but the trace/profile function is disabled from now on.
---------- files: test9.py messages: 232305 nosy: arigo priority: normal severity: normal status: open title: RuntimeError: settrace/setprofile function gets lost type: behavior Added file: http://bugs.python.org/file37386/test9.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23012> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
