STINNER Victor added the comment:
I concur with Yury that there is not enough users and use cases needing this
feature, so it doesn't deserve to pay the maintenance burden in the standard
library. Start with a project on PyPI.
--
resolution: -> rejected
stage: -> resolved
status:
Brian Haley added the comment:
Any chance this will get accepted? I actually have a use case in Openstack
where we might get a protocol number and want to save the name along with it.
Right now we're looking at using libc getprotoent() directly which isn't that
pretty. Thanks!
Will Booth added the comment:
Allow users to translate protocol numbers from IPv4/IPv6 headers to a friendly
human readable string.
Just filling a gap in the API. There might be a PyPI package out there similar
to socket. However, it's complementary function,'getprotobyname', already exist
New submission from Will Booth:
Add an old method from netdb to python for a best-effort, centerized look up.
For the function to work, /etc/protocols would also need to be present. If the
protocol doesn't exist OSError is raised.
Patch attached.
--
components: Extension Modules
Changes by Will Booth m3rz3r...@gmail.com:
--
versions: +Python 3.5 -Python 3.6
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24809
___
___
Yury Selivanov added the comment:
What are the use cases?
If it's (Rarely used.) (as docstring indicates), then, perhaps, a package on
PyPI is a better solution.
--
nosy: +haypo, yselivanov
versions: +Python 3.6 -Python 3.5
___
Python tracker
