Message236774
| Author | steve.dower |
|---|---|
| Recipients | larry, serhiy.storchaka, steve.dower, tim.golden, vstinner, zach.ware |
| Date | 2015-02-27.16:08:53 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1425053333.61.0.628238148599.issue23524@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
#4804 has most of the prior discussion, but here's some code that will cause the process to terminate: import os os.close(3) The instant termination rather than OSError is why _PyVerify_fd exists at all, and that's only there because when the behaviour was disabled globally users complained (#3545 and #4804). You are correct that _PyVerify_fd is used in more places where it should be updated (specifically _io/fileio.c and fileutils.c). It only makes sense where it's protecting a call into a CRT function though, so not all of these places should be changed. I'll make updates. This is why I beg for reviews - I know that I'll miss things :) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015-02-27 16:08:53 | steve.dower | set | recipients: + steve.dower, vstinner, larry, tim.golden, zach.ware, serhiy.storchaka |
| 2015-02-27 16:08:53 | steve.dower | set | messageid: <1425053333.61.0.628238148599.issue23524@psf.upfronthosting.co.za> |
| 2015-02-27 16:08:53 | steve.dower | link | issue23524 messages |
| 2015-02-27 16:08:53 | steve.dower | create | |