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, tholzer, vstinner |
| Date | 2014年05月20日.05:41:32 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAH_1eM2RD_D+AnDfPUMc5r-Ut4R2uoN98kyyLmbht+PVJb7Pyg@mail.gmail.com> |
| In-reply-to | <1400555581.89.0.479622645828.issue20611@psf.upfronthosting.co.za> |
| Content | |
|---|---|
As said in a previous comment, we don't want to have EINTR handling code everywhere. The right way to do this is to handle it at the syscall level. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014年05月20日 05:41:33 | neologix | set | recipients: + neologix, gregory.p.smith, pitrou, vstinner, flox, tholzer |
| 2014年05月20日 05:41:32 | neologix | link | issue20611 messages |
| 2014年05月20日 05:41:32 | neologix | create | |