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 vstinner
Recipients Jack Zhou, neologix, python-dev, serhiy.storchaka, twouters, vstinner
Date 2016-04-09.12:33:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwaW90r1OKAfJ_6ftRv0fkiXUJPNDJ3L9oCj4r_u19kuwA@mail.gmail.com>
In-reply-to <1460197593.31.0.676648399867.issue26716@psf.upfronthosting.co.za>
Content
Serhiy Storchaka added the comment:
> It looks to me that interrupting fcntl can be used for implementing
blocking lock with a timeout. If automatically retry fcntl() on EINTR, this
will break such code.

If the signal handler doesn't raise an exception, the code is not reliable.
It's a common complain about the PEP 475.

If the signal handler raises an exception, it's work on Python 2.7 and on
Python 3.5 with my patch.
History
Date User Action Args
2016-04-09 12:33:43vstinnersetrecipients: + vstinner, twouters, neologix, python-dev, serhiy.storchaka, Jack Zhou
2016-04-09 12:33:42vstinnerlinkissue26716 messages
2016-04-09 12:33:42vstinnercreate