[issue25459] EAGAIN errors in Python logging module

Vinay Sajip added the comment: I will close this as not a bug. If you have custom signal handling which interacts with logging in an undesirable way, you will need to subclass the handler. The use case isn't common enough to be addressed in the base handler, IMO. -- resolution: -> no

[issue25459] EAGAIN errors in Python logging module

Henrique Andrade added the comment: Vinay, apologies for the long time you took me to respond (the notification was stuck in my Spam folder, thanks Gmail!). Indeed, both of your comments are spot on. In my particular case, I ended up implementing what your first suggestion alludes to (a retry cap

[issue25459] EAGAIN errors in Python logging module

Vinay Sajip added the comment: The problem with your suggested fix is that if you keep getting EAGAIN, the handler will appear to hang. If you want to suggest that maybe we limit the number of tries, then what number of retries would you pick, and why? Also, a caller might want to know about E

[issue25459] EAGAIN errors in Python logging module

Changes by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue25459] EAGAIN errors in Python logging module

Henrique Andrade added the comment: The stream in this case (where I hit the bug) is just the console, but I suspect the same issue will affect other streams too. A key piece of information is that this is probably triggered by having a custom SIGPIPE handler, which my particular application has

[issue25459] EAGAIN errors in Python logging module

STINNER Victor added the comment: What is the type of the stream? Is is a pipe or a regular file? Or a socket? Can you please format the patch as an unified patch please? -- nosy: +haypo ___ Python tracker ___

[issue25459] EAGAIN errors in Python logging module

New submission from Henrique Andrade: There is a particular bug we hit when using the Python logging module very consistently under the particular settings in which we run one of our applications. We are using Python 2.7.10 on RHEL7/RHEL6/Ubuntu14.04. Anyways, here is the symptom: Traceback