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

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
nosy: +pitrou

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Antoine Pitrou]

Changes by Antoine Pitrou :


--
versions: +Python 3.7 -Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Gregory P. Smith]

Changes by Gregory P. Smith :


--
nosy: +gregory.p.smith

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Josh Lee]

Changes by Josh Lee :


--
nosy: +jleedev

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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 issue24209, but also in third-party packages. I ran into this 
during the implementation of aiosmtpd 
(https://gitlab.com/python-smtpd-hackers/aiosmtpd). As a long time maintainer 
of CherryPy, I've enjoyed the [dual stack 
support](https://bitbucket.org/cherrypy/cherrypy/src/536a9cb66e91de92502e766b2b0cf53d1cb5cb4a/cherrypy/wsgiserver/wsgiserver2.py?at=default&fileviewer=file-view-default#wsgiserver2.py-2007:2020)
 there.

I propose the Python stdlib provide a routine to facilitate this need more 
generally, and then invoke that implementation to address these other use-cases.

As it is a new feature, a backports package should be created to supply the 
same functionality for older Pythons.

Would this effort require a PEP? Is there a good place for such a routine 
(maybe socketserver)? Any other thoughts?

--
components: Library (Lib)
messages: 254895
nosy: jason.coombs
priority: normal
severity: normal
status: open
title: Supply dual-stack (IPv4/IPv6) socket bind routine
versions: Python 3.6

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com