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 EliRibble
Recipients EliRibble, serhiy.storchaka
Date 2018-02-08.20:24:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1518121463.16.0.467229070634.issue32799@psf.upfronthosting.co.za>
In-reply-to
Content
To my knowledge, no, we don't use any python extensions. Unless extensions can be installed via pip, in which case I would need to audit our many dependencies to determine if any of them ultimately pull in any extensions as part of a pip install.

I can't provide a minimal script, no, we don't reproduce it deterministically. Like I said, our application runs all the time and we appear to have about ~200 instances where the problem has been caught by our uncaught exception handling system. The repro of the bug does not appear to have a set correlation with exercise of a particular feature or a particular application state. Given the exception is a thin wrapper around linux syscalls, my guess is something like select(), it's likely the issue has to do with transient network communication problems.
History
Date User Action Args
2018-02-08 20:24:23EliRibblesetrecipients: + EliRibble, serhiy.storchaka
2018-02-08 20:24:23EliRibblesetmessageid: <1518121463.16.0.467229070634.issue32799@psf.upfronthosting.co.za>
2018-02-08 20:24:23EliRibblelinkissue32799 messages
2018-02-08 20:24:23EliRibblecreate