Message118960
| Author |
loewis |
| Recipients |
doko, exarkun, lekma, loewis, nvetoshkin, pitrou |
| Date |
2010年10月17日.18:24:57 |
| SpamBayes Score |
4.2747533e-07 |
| Marked as misclassified |
No |
| Message-id |
<4CBB3F75.4010006@v.loewis.de> |
| In-reply-to |
<1287156857.53.0.171830407591.issue10115@psf.upfronthosting.co.za> |
| Content |
> That's another possibility, in which case we would first remove the
> current accept4-calling code in order to fix the buildbot failure.
In Python, the lowest layer facing the operating system always directly
exposes the API as-is, without reinterpreting the user's request. Not
following this principle leads exactly to this kind of problem.
So I think .accept() should only call accept(2), and accept4() should
only be called if explicitly requested by the application.
Exposing it as .accept4(flags) is certainly the most straight-forward
way of doing it, but I could also live with .accept(flags) (i.e.
call accept4 if flags are being passed, hoping that no other system
comes up with another accept extension that has a different integer
argument). |
|