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 serhiy.storchaka
Recipients Jack Zhou, neologix, python-dev, serhiy.storchaka, twouters, vstinner
Date 2016-04-12.19:04:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1460487888.7.0.578787247761.issue26716@psf.upfronthosting.co.za>
In-reply-to
Content
I just don't know whether the patch will break existing code that relies on current behavior. If EINTR handling in other functions was not backported to older versions, I think this is good argument against fixing this issue in 3.5.

Could you write tests with signal handlers raising and not raising an exception?
History
Date User Action Args
2016-04-12 19:04:48serhiy.storchakasetrecipients: + serhiy.storchaka, twouters, vstinner, neologix, python-dev, Jack Zhou
2016-04-12 19:04:48serhiy.storchakasetmessageid: <1460487888.7.0.578787247761.issue26716@psf.upfronthosting.co.za>
2016-04-12 19:04:48serhiy.storchakalinkissue26716 messages
2016-04-12 19:04:48serhiy.storchakacreate