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 exarkun
Recipients brian.curtin, exarkun, giampaolo.rodola, paul.moore, pitrou, r.david.murray, tim.golden, trent, vinay.sajip
Date 2010-05-03.15:08:41
SpamBayes Score 0.0001885205
Marked as misclassified No
Message-id <1272899323.62.0.940000955304.issue8576@psf.upfronthosting.co.za>
In-reply-to
Content
> I'm not sure if I agree that find_unused_port() should be removed though; it does serve a purpose in very rare corner cases.

It can serve a purpose in any number of cases.  My point is that it's *always* unreliable, though.  Any time you have any API that you want to test that requires a pre-allocated port number, you're going to have intermittent failures.  Such APIs are broken and should be fixed where possible and avoided otherwise.
History
Date User Action Args
2010-05-03 15:08:43exarkunsetrecipients: + exarkun, paul.moore, vinay.sajip, pitrou, giampaolo.rodola, tim.golden, trent, r.david.murray, brian.curtin
2010-05-03 15:08:43exarkunsetmessageid: <1272899323.62.0.940000955304.issue8576@psf.upfronthosting.co.za>
2010-05-03 15:08:42exarkunlinkissue8576 messages
2010-05-03 15:08:42exarkuncreate