Message87392
| Author |
mark.dickinson |
| Recipients |
MrJean1, alanmcintyre, donmez, facundobatista, giampaolo.rodola, josiahcarlson, mark.dickinson, r.david.murray |
| Date |
2009年05月07日.19:10:09 |
| SpamBayes Score |
6.4130836e-06 |
| Marked as misclassified |
No |
| Message-id |
<1241723410.99.0.392829501008.issue5798@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Josiah, that solution isn't working for me; it looks as though there's
a deeper weirdness: what I'm seeing is that on OS X, in e.g.
test_emptyline, we end up calling the readwrite function in asyncore.py
with flags = POLLIN | POLLPRI | POLLHUP. The first thing that gets
called is obj.handle.read_event, and bizarrely it seems to be the
read_event call that has the effect of closing the socket. So the
socket's already closed by the time we get to obj.handle_expt_event and
the same error as before occurs.
I'm still trying to figure out why. |
|