Message 82356 - 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	gregory.p.smith
Recipients	gregory.p.smith, loewis, techtonik
Date	2009-02-17.19:18:43
SpamBayes Score	0.00073351635
Marked as misclassified	No
Message-id	<1234898359.61.0.834915262754.issue5293@psf.upfronthosting.co.za>
In-reply-to

Content
You can't use a connect() call for the purpose of waiting for your network to be up. This has nothing to do with Python. This is how all network APIs work regardless of OS and language. The "timeout" is due to the network stack being unable to find the remote host (read up on ARP) and eventually returning an error. You need to deal with that in your own code.

You can't use a connect() call for the purpose of waiting for your 
network to be up.  This has nothing to do with Python.  This is how all 
network APIs work regardless of OS and language.

The "timeout" is due to the network stack being unable to find the 
remote host (read up on ARP) and eventually returning an error.  You 
need to deal with that in your own code.

History
Date	User	Action	Args
2009-02-17 19:19:19	gregory.p.smith	set	recipients: + gregory.p.smith, loewis, techtonik
2009-02-17 19:19:19	gregory.p.smith	set	messageid: <1234898359.61.0.834915262754.issue5293@psf.upfronthosting.co.za>
2009-02-17 19:18:44	gregory.p.smith	link	issue5293 messages
2009-02-17 19:18:43	gregory.p.smith	create