[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

2016-05-16 Thread Berker Peksag
Berker Peksag added the comment: Agreed with Martin. -- nosy: +berker.peksag -Daniel Griffin priority: normal -> low resolution: -> rejected stage: needs patch -> resolved status: pending -> closed ___ Python tracker

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

2016-05-14 Thread Martin Panter
Changes by Martin Panter : -- status: open -> pending type: crash -> enhancement versions: -Python 2.7 ___ Python tracker ___

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

2016-05-14 Thread Martin Panter
Changes by Martin Panter : Removed file: http://bugs.python.org/file42848/sync_node.xml ___ Python tracker ___

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

2016-05-14 Thread Daniel Griffin
Changes by Daniel Griffin : Added file: http://bugs.python.org/file42848/sync_node.xml ___ Python tracker ___

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

2016-05-14 Thread Daniel Griffin
Changes by Daniel Griffin : -- nosy: +Daniel Griffin status: pending -> open type: enhancement -> crash versions: +Python 2.7 ___ Python tracker

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

2016-05-14 Thread Martin Panter
Martin Panter added the comment: Currently pydoc only binds to IPv4 localhost, not the “any-address” 0.0.0.0. See Issue 22421 and Issue 672656. Apart from satisfying Hans’s expectation, what is the benefit of running pydoc on IPv6? I guess it would be possible to bind two sockets, one to IPv4

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

2016-04-04 Thread Martin Panter
Martin Panter added the comment: I understand Windows XP isn’t so important these days. So maybe we just need to disable IPV6_V6ONLY. (Unless we want this for 2.7 maybe?) -- stage: -> needs patch versions: +Python 3.6 -Python 3.3 ___ Python tracker

[issue3213] "pydoc -p" should listen to [::] if IPv6 is supported

2016-04-04 Thread Josh Lee
Changes by Josh Lee : -- nosy: +jleedev ___ Python tracker ___ ___ Python-bugs-list mailing

[issue3213] pydoc -p should listen to [::] if IPv6 is supported

2015-02-08 Thread Martin Panter
Changes by Martin Panter vadmium...@gmail.com: -- nosy: +vadmium ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3213 ___ ___ Python-bugs-list

[issue3213] pydoc -p should listen to [::] if IPv6 is supported

2012-02-20 Thread Éric Araujo
Changes by Éric Araujo mer...@netwok.org: -- type: behavior - enhancement versions: +Python 3.3 -Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3213

[issue3213] pydoc -p should listen to [::] if IPv6 is supported

2010-06-09 Thread Terry J. Reedy
Changes by Terry J. Reedy tjre...@udel.edu: -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3213 ___

[issue3213] pydoc -p should listen to [::] if IPv6 is supported

2008-06-26 Thread Hans Ulrich Niedermann
New submission from Hans Ulrich Niedermann [EMAIL PROTECTED]: According to pydoc --help, pydoc -p port Start an HTTP server on the given port on the local machine. The IP address pydoc binds to is not specified, thus I would expect it to either bind to the local address or to the wildcard

[issue3213] pydoc -p should listen to [::] if IPv6 is supported

2008-06-26 Thread Martin v. Löwis
Martin v. Löwis [EMAIL PROTECTED] added the comment: That will break on systems where AF_INET6 doesn't default to dual-stacked sockets and mapped v4 addresses (e.g. Windows); to make it work correctly, you'll also have to disable the IPV6_V6ONLY option, which then breaks on systems which don't