Message 152503 - 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	giampaolo.rodola
Recipients	adamhj, giampaolo.rodola
Date	2012-02-03.13:18:09
SpamBayes Score	0.012050697
Marked as misclassified	No
Message-id	<1328275090.46.0.532785822047.issue13928@psf.upfronthosting.co.za>
In-reply-to

Content
> why is a not connected connection writable? A non connected socket must be writable in order to connect. > if we call dispatcher.connect() immediately after .connect(), > socket error 10057 may be raised, Not sure what you mean here. Why would you call connect() twice?

> why is a not connected connection writable? 

A non connected socket must be writable in order to connect.

> if we call dispatcher.connect() immediately after .connect(), 
> socket error 10057 may be raised, 

Not sure what you mean here. Why would you call connect() twice?

History
Date	User	Action	Args
2012-02-03 13:18:10	giampaolo.rodola	set	recipients: + giampaolo.rodola, adamhj
2012-02-03 13:18:10	giampaolo.rodola	set	messageid: <1328275090.46.0.532785822047.issue13928@psf.upfronthosting.co.za>
2012-02-03 13:18:09	giampaolo.rodola	link	issue13928 messages
2012-02-03 13:18:09	giampaolo.rodola	create