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 | gregory.p.smith, mcjeff, vstinner |
| Date | 2015年04月04日.21:54:23 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAMpsgwauwk727+_8HCR+xhWFMUO2dWapurH64ZjJFhPv=5AbuQ@mail.gmail.com> |
| In-reply-to | <1428165461.13.0.555530591164.issue23863@psf.upfronthosting.co.za> |
| Content | |
|---|---|
I have a very good news for you: this issue and more generally all EINTR issues will be solved in Python 3.5. See the PEP 475. I'm not really interested to fix Python 2.7. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015年04月04日 21:54:23 | vstinner | set | recipients: + vstinner, gregory.p.smith, mcjeff |
| 2015年04月04日 21:54:23 | vstinner | link | issue23863 messages |
| 2015年04月04日 21:54:23 | vstinner | create | |