This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author amaury.forgeotdarc
Recipients amaury.forgeotdarc, fabioz
Date 2008-08-18.21:43:31
SpamBayes Score 2.2379975e-06
Marked as misclassified No
Message-id <1219095813.86.0.54885960003.issue3494@psf.upfronthosting.co.za>
In-reply-to
Content
> 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)
History
Date User Action Args
2008-08-18 21:43:34amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, fabioz
2008-08-18 21:43:33amaury.forgeotdarcsetmessageid: <1219095813.86.0.54885960003.issue3494@psf.upfronthosting.co.za>
2008-08-18 21:43:32amaury.forgeotdarclinkissue3494 messages
2008-08-18 21:43:31amaury.forgeotdarccreate