➜

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 kristjan.jonsson
Recipients kristjan.jonsson
Date 2012-09-23.08:34:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1348389246.53.0.0663792895343.issue16003@psf.upfronthosting.co.za>
In-reply-to
Content 
If thread creation fails, for any reason, a ThreadError is returned with the error "can't start new thread".
No attempt is made to diagnose the issue.
In fact, for example, if we are out of resources, pthread_new() would have returned EAGAIN.  This should perhaps rather be classified as an OSError so that users can catch this and diagnose it.  ThreadError seems to be used otherwise exclusively to indicate problems with locking.

Can this be turned into an informative OSError, or is it to platform dependant for any sensible structured error handlng to be implemented?
History
Date User Action Args
2012-09-23 08:34:06kristjan.jonssonsetrecipients: + kristjan.jonsson
2012-09-23 08:34:06kristjan.jonssonsetmessageid: <1348389246.53.0.0663792895343.issue16003@psf.upfronthosting.co.za>
2012-09-23 08:34:05kristjan.jonssonlinkissue16003 messages
2012-09-23 08:34:04kristjan.jonssoncreate