[issue18905] pydoc -p 0 says the server is available at localhost:0

2014-11-27 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ _

[issue18905] pydoc -p 0 says the server is available at localhost:0

2014-11-27 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Thank you for your patch Wieland. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue18905] pydoc -p 0 says the server is available at localhost:0

2014-11-27 Thread Roundup Robot
Roundup Robot added the comment: New changeset ac7f3161aa53 by Serhiy Storchaka in branch '2.7': Issue #18905: "pydoc -p 0" now outputs actually used port. Based on patch by https://hg.python.org/cpython/rev/ac7f3161aa53 -- nosy: +python-dev ___ Pyth

[issue18905] pydoc -p 0 says the server is available at localhost:0

2014-11-18 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: With the patch resolved address 127.0.0.1 is printed instead of localhost. self.address[0] can be used to match current behavior of 2.7 and 3.x. And why not just initialize the url attribute in server_activate()? -- assignee: -> serhiy.storchaka nos

[issue18905] pydoc -p 0 says the server is available at localhost:0

2013-09-07 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue18905] pydoc -p 0 says the server is available at localhost:0

2013-09-02 Thread Wieland Hoffmann
New submission from Wieland Hoffmann: In Python 3 one can use `pydoc -p 0` to start a pydoc HTTP server on an arbitrary unused port. This works (somewhat) in Python 2 as well, except that pydoc doesn't tell you which port it's listening on. Applying the attached patch makes pydoc print the cor