Message78767
| Author |
kristjan.jonsson |
| Recipients |
amaury.forgeotdarc, kristjan.jonsson, mhammond |
| Date |
2009年01月02日.09:45:16 |
| SpamBayes Score |
1.3613817e-08 |
| Marked as misclassified |
No |
| Message-id |
<930F189C8A437347B80DF2C156F7EC7F04D1702FD6@exchis.ccp.ad.local> |
| In-reply-to |
<1230887830.55.0.601904720526.issue4804@psf.upfronthosting.co.za> |
| Content |
Yes, this is the biggest reason why this is required.
This, and and os.closerange().
I have browsed the CRT source and I find no way to determine if a fd is actually valid, before calling any of the functions that check for it.
Reintroducing the assertion will prevent a debug build python from passing the testsuite.
Much as I think this is useful (turning on the crt tests helped me find a couple of python bugs recently) it unfortunately needs to be off because of os.close(). All other troublesome cases (strftime(), open()) have workarounds.
Kristján |
|