Message169081
| Author |
Jimbofbx |
| Recipients |
Jimbofbx, loewis |
| Date |
2012年08月24日.20:36:16 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1345840577.19.0.266880110172.issue15779@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
That makes no sense. Why does:
s = socket.socket()
s.bind(('',50007))
s.listen(1);
s.close();
fix the issue then?
Re-opening, this issue should be understood because having such an operation randomly fail is unacceptable for a production system. How does python choose a port to open a connection on? If windows reports the wrong error then shouldn't python try a different port number anyways (considering I have no control over what port Python chooses to open a connection on)? |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年08月24日 20:36:17 | Jimbofbx | set | recipients:
+ Jimbofbx, loewis |
| 2012年08月24日 20:36:17 | Jimbofbx | set | messageid: <1345840577.19.0.266880110172.issue15779@psf.upfronthosting.co.za> |
| 2012年08月24日 20:36:16 | Jimbofbx | link | issue15779 messages |
| 2012年08月24日 20:36:16 | Jimbofbx | create |
|