[issue45772] socket.socket should be a class instead of a function

miss-islington added the comment: New changeset b952f60213c60f89a50e4538783a18ced64ca91f by Miss Islington (bot) in branch '3.9': [3.9] bpo-45772: socket.socket should be a class instead of a function (GH-23960) (GH-29543)

[issue45772] socket.socket should be a class instead of a function

miss-islington added the comment: New changeset 3f15792d60011639d9b170d8a76c6db7f6e83665 by Miss Islington (bot) in branch '3.10': [3.10] bpo-45772: socket.socket should be a class instead of a function (GH-23960) (GH-29542)

[issue45772] socket.socket should be a class instead of a function

Change by Oleg Iarygin : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue45772] socket.socket should be a class instead of a function

Change by miss-islington : -- keywords: +patch nosy: +miss-islington nosy_count: 6.0 -> 7.0 pull_requests: +27790 pull_request: https://github.com/python/cpython/pull/29542 ___ Python tracker

[issue45772] socket.socket should be a class instead of a function

Change by miss-islington : -- pull_requests: +27791 pull_request: https://github.com/python/cpython/pull/29543 ___ Python tracker ___

[issue45772] socket.socket should be a class instead of a function

Change by miss-islington : -- pull_requests: +27792 pull_request: https://github.com/python/cpython/pull/29544 ___ Python tracker ___

[issue45772] socket.socket should be a class instead of a function

Andrew Svetlov added the comment: New changeset 4c792f39e688b11c7c19e411ed4f76a7baa44638 by Hong Xu in branch 'main': bpo-45772: socket.socket should be a class instead of a function (GH-23960) https://github.com/python/cpython/commit/4c792f39e688b11c7c19e411ed4f76a7baa44638 --

[issue45772] socket.socket should be a class instead of a function

Terry J. Reedy added the comment: Filter, map, and zip are documented as functions to allow other interpreters to implement them as such, with generator functions. That does not apply here, but maybe there is another reason for socket being called a 'function. Antoine, git blame credits

[issue45772] socket.socket should be a class instead of a function

New submission from Oleg Iarygin : Found a twice stale bpo-less but useful pull request 23960, so publish it here: > Currently socket.socket is documented as a function, but it is really a class (and thus has function-like usage to construct an object). This correction would ensure that Python