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 | neologix |
|---|---|
| Recipients | flox, gregory.p.smith, neologix, pitrou, vstinner |
| Date | 2014年02月13日.05:13:36 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAH_1eM25f9iknk_pPpOAgu7yxh58n-vydGOaTezCaa_sGQMDoA@mail.gmail.com> |
| In-reply-to | <1392218347.62.0.107141952348.issue20611@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> It seems that the EINTR should be caught by the standard library in all cases: > http://bugs.python.org/issue1628205 Yes, it should. > But it's not the case for the "socket.create_connection" method (verified in 3.3 and 2.7 source code). It's not the case for *almost all* syscalls. See http://bugs.python.org/issue18885 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014年02月13日 05:13:36 | neologix | set | recipients: + neologix, gregory.p.smith, pitrou, vstinner, flox |
| 2014年02月13日 05:13:36 | neologix | link | issue20611 messages |
| 2014年02月13日 05:13:36 | neologix | create | |