Message 84255 - Python tracker

➜

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	mallyvai
Recipients	georg.brandl, jnoller, mallyvai
Date	2009-03-27.06:58:59
SpamBayes Score	1.0588171e-07
Marked as misclassified	No
Message-id	<1238137148.14.0.116021983523.issue5573@psf.upfronthosting.co.za>
In-reply-to

Content
On second thought, it seems like it shouldn't make sense. This forces a destructive check. Suppose we do child.poll() and then child.recv() but it's legitimate data; that data will be removed from the queue even if we just wanted to check if the pipe was alive. This seems like it shouldn't have to happen. I'm unfamiliar with the lower level workings of sockets; is this destructive checking behavior forced by the socket internals? Is it standard?

On second thought, it seems like it shouldn't make sense. This forces a
destructive check. Suppose we do child.poll() and then child.recv() but
it's legitimate data; that data will be removed from the queue even if
we just wanted to check if the pipe was alive. This seems like it
shouldn't have to happen.

I'm unfamiliar with the lower level workings of sockets; is this
destructive checking behavior forced by the socket internals? Is it
standard?

History
Date	User	Action	Args
2009-03-27 06:59:08	mallyvai	set	recipients: + mallyvai, georg.brandl, jnoller
2009-03-27 06:59:08	mallyvai	set	messageid: <1238137148.14.0.116021983523.issue5573@psf.upfronthosting.co.za>
2009-03-27 06:59:06	mallyvai	link	issue5573 messages
2009-03-27 06:59:06	mallyvai	create