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

Oleg Iarygin report at bugs.python.org
Tue Nov 9 14:55:56 EST 2021


New submission from Oleg Iarygin <oleg at arhadthedev.net>:

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 projects that are interlinking
Python's documentation can properly locate socket.socket as a type.

----------
assignee: docs at python
components: Documentation
messages: 406045
nosy: arhadthedev, docs at python, xuhdev
priority: normal
pull_requests: 27751
severity: normal
status: open
title: socket.socket should be a class instead of a function
versions: Python 3.10, Python 3.11, Python 3.6, Python 3.7, Python 3.8, Python 3.9

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue45772>
_______________________________________


More information about the Python-bugs-list mailing list