[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2020-01-05 Thread Jason R. Coombs
Change by Jason R. Coombs : -- keywords: +patch pull_requests: +17273 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/17851 ___ Python tracker

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2018-12-16 Thread Jason R. Coombs
Jason R. Coombs added the comment: I believe this issue is a duplicate of 17561, which I stumbled onto today. -- resolution: -> duplicate superseder: -> Add socket.create_server_sock() convenience function ___ Python tracker

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2017-01-27 Thread Antoine Pitrou
Antoine Pitrou added the comment: Related though with a different strategy: Tornado's bind_sockets() routine: https://github.com/tornadoweb/tornado/blob/master/tornado/netutil.py#L114-L138 -- ___ Python tracker

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2017-01-27 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2017-01-26 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- versions: +Python 3.7 -Python 3.6 ___ Python tracker ___ ___

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2017-01-25 Thread Gregory P. Smith
Changes by Gregory P. Smith : -- nosy: +gregory.p.smith ___ Python tracker ___ ___

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2016-03-07 Thread Jason R. Coombs
Jason R. Coombs added the comment: No reason not to put it in the socket module. I was thinking originally that the socket module was C only, but on further reflection, it could easily be one of the "additional facilities implemented in Python". Great suggestion. --

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

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

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2015-11-19 Thread Jason R. Coombs
New submission from Jason R. Coombs: When binding to a socket for creating a service, the socket API provides a mechanism for selecting only IPv4 or IPv6, but the simple operation of binding to all interfaces in a dual-stack environment is not easy, as is revealed in issue20215 and

[issue25667] Supply dual-stack (IPv4/IPv6) socket bind routine

2015-11-19 Thread R. David Murray
R. David Murray added the comment: I don't think it should require a PEP, it looks like a fairly straightforward small enhancement. What is the reason to not put it in the socket module? -- nosy: +r.david.murray stage: -> needs patch type: -> enhancement