Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: > but if the code that's being debugged > spawned other threads (which is pretty common), it would be pointless,
No, the problem specifically lies in the implementation of listdir(). This function is not supposed to commonly spawn threads... this can only happen with a sys.settrace function (or a very special Py_FileSystemDefaultEncoding) > And I think that setting the errno to 0 in the debugger every time would > make other things misbehave, as in each python call it'd clear it I don't think so. errno is (should be) only used shortly after the C system call which modified it. There is no room for the trace function to run. Remember that the python stack is often displayed on every debugging step, and this modifies errno more than once (to get the source file content) _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3494> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
