homepage

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 pitrou
Recipients Jimbofbx, loewis, pitrou, tim.golden
Date 2012年08月25日.00:22:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1345854159.08.0.82526605625.issue15779@psf.upfronthosting.co.za>
In-reply-to
Content
> Looks to me like python grabs an outgoing port number via unrandom means
Python does not grab an outgoing port number, its lets the OS choose one (via connect()). The only thing to watch out for would be whether you let many connections open (perhaps there's a per-process limit that is reached).
> Which, if I'm understanding the code correctly, returns the source
> address used to make the connection in this instance.
getaddrinfo() does not do that. It is simply a wrapper around the C runtime library's getaddrinfo(), for which you can find information on the Web (for both the Windows and POSIX versions of it).
> If windows is responsible for giving the bad port number, I would argue
> that Python still needs to account for the problem since this is obviously 
> a major issue if it happens to someone.
It might be a major issue for whoever encounters the issue but, as Martin said, Python cannot do anything else than bubble up the exception for you to handle.
Since this seems to be a fairly involved Windows issue (rather than a Python bug), I suggest you ask for help on a help forum with Windows experts.
History
Date User Action Args
2012年08月25日 00:22:40pitrousetrecipients: + pitrou, loewis, tim.golden, Jimbofbx
2012年08月25日 00:22:39pitrousetmessageid: <1345854159.08.0.82526605625.issue15779@psf.upfronthosting.co.za>
2012年08月25日 00:22:38pitroulinkissue15779 messages
2012年08月25日 00:22:38pitroucreate

AltStyle によって変換されたページ (->オリジナル) /