This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients Oren Milman, serhiy.storchaka
Date 2017-03-17.06:43:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1489732997.44.0.201686346308.issue29832@psf.upfronthosting.co.za>
In-reply-to
Content
getsockaddrarg() is an internal C function in the socket module implementation used in a number of socket methods (bind(), connect(), connect_ex(), sendto(), sendmsg()) for creating C structure sock_addr_t from Python tuple. Error messages raised when pass incorrect socket address argument to these function contain the name "getsockaddrarg" despite the fact that it is not directly exposed at Python level, nor the name of standard C function.

>>> import socket
>>> s = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
>>> s.bind(42)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: getsockaddrarg: AF_INET address must be tuple, not int
>>> s.bind(())
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: getsockaddrarg() takes exactly 2 arguments (0 given)

I think that error messages shouldn't refer to non-existing function "getsockaddrarg()".

This issue is a part of more general issue28261.
History
Date User Action Args
2017-03-17 06:43:17serhiy.storchakasetrecipients: + serhiy.storchaka, Oren Milman
2017-03-17 06:43:17serhiy.storchakasetmessageid: <1489732997.44.0.201686346308.issue29832@psf.upfronthosting.co.za>
2017-03-17 06:43:17serhiy.storchakalinkissue29832 messages
2017-03-17 06:43:16serhiy.storchakacreate