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.

classification
Title: Wrong signature for SSLSocket.recvfrom and SSLSocket.sendto
Type: behavior Stage: resolved
Components: Versions: Python 3.1, Python 3.2
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: pitrou
Priority: normal Keywords:

Created on 2010-09-14 13:09 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (3)
msg116397 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-09-14 13:09
SSLSocket.recvfrom includes an `addr` argument in its signature, but socket.recvfrom doesn't take such an argument. It should be removed.
(obviously, this method is neither tested nor used in the real-world...)

In 2.7, this is taken care of by the patch in issue9729.
msg116399 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-09-14 13:39
Similar problem for sendto() (again, see issue9729).
socket.sendto() has an interesting signature (the middle `flags` argument is optional, not the following `addr`...).
msg116403 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2010-09-14 14:47
Fixed in r84807 (3.x) and r84809 (3.1).
History
Date User Action Args
2022-04-11 14:57:06adminsetgithub: 54062
2010-09-14 14:47:43pitrousetstatus: open -> closed
resolution: fixed
messages: + msg116403

stage: needs patch -> resolved
2010-09-14 13:39:14pitrousetmessages: + msg116399
title: Wrong signature for SSLSocket.recvfrom -> Wrong signature for SSLSocket.recvfrom and SSLSocket.sendto
2010-09-14 13:09:42pitroucreate