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 r.david.murray
Recipients fxkr, r.david.murray
Date 2015-08-20.15:24:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440084253.03.0.827762245971.issue24902@psf.upfronthosting.co.za>
In-reply-to
Content
I do it in a number of test suites (you pass in localhost and port 0, then parse the output to find out what port got used).  I'm sure other people do it as well.  The parens could be dropped.  I don't think it is really redundant, as the two ways of presenting the info hit different parts of my brain: one is the part that looks at things from a networking perspective (ports and IPs) and the other that looks at it from a web perspective (urls).
History
Date User Action Args
2015-08-20 15:24:13r.david.murraysetrecipients: + r.david.murray, fxkr
2015-08-20 15:24:13r.david.murraysetmessageid: <1440084253.03.0.827762245971.issue24902@psf.upfronthosting.co.za>
2015-08-20 15:24:13r.david.murraylinkissue24902 messages
2015-08-20 15:24:12r.david.murraycreate