Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
bpo-45772: socket.socket should be a class instead of a function#23960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This PR is stale because it has been open for 30 days with no activity. |
Could someone review this, please? This should be quite quick to review. |
This PR is stale because it has been open for 30 days with no activity. |
marsfan commentedNov 9, 2021
I have been running into this same issue. It would be really nice to see this fixed. |
I created an entry for this pull request on bugs.python.org because most of people are there. Actually, that's the very reason why authors should do it by themselves. |
arhadthedev commentedNov 9, 2021 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
In addition, status checks in the bottom of this GitHub page state the following:
So you need to change a title of this issue to Edit: the bot replaced |
Currently `socket.socket` is documented as a function, but it is reallya class (and thus has function-like usage to construct an object). Thiscorrection would ensure that Python projects that are interlinkingPython's documentation can properly locate `socket.socket` as a type.
Thanks@arhadthedev , I've updated the PR. |
@marsfan add your supporting comment on the issue, with explanation if possible. |
Misc/NEWS.d/next/Documentation/2021-11-09-13-10-55.bpo-45772.EdrM3t.rst OutdatedShow resolvedHide resolved
Uh oh!
There was an error while loading.Please reload this page.
bedevere-bot commentedNov 13, 2021
GH-29542 is a backport of this pull request to the3.10 branch. |
…honGH-23960)* bpo-45772: socket.socket should be a class instead of a functionCurrently `socket.socket` is documented as a function, but it is reallya class (and thus has function-like usage to construct an object). Thiscorrection would ensure that Python projects that are interlinkingPython's documentation can properly locate `socket.socket` as a type.(cherry picked from commit4c792f3)Co-authored-by: Hong Xu <hong@topbug.net>
…honGH-23960)* bpo-45772: socket.socket should be a class instead of a functionCurrently `socket.socket` is documented as a function, but it is reallya class (and thus has function-like usage to construct an object). Thiscorrection would ensure that Python projects that are interlinkingPython's documentation can properly locate `socket.socket` as a type.(cherry picked from commit4c792f3)Co-authored-by: Hong Xu <hong@topbug.net>
bedevere-bot commentedNov 13, 2021
GH-29543 is a backport of this pull request to the3.9 branch. |
bedevere-bot commentedNov 13, 2021
GH-29544 is a backport of this pull request to the3.8 branch. |
…honGH-23960)* bpo-45772: socket.socket should be a class instead of a functionCurrently `socket.socket` is documented as a function, but it is reallya class (and thus has function-like usage to construct an object). Thiscorrection would ensure that Python projects that are interlinkingPython's documentation can properly locate `socket.socket` as a type.(cherry picked from commit4c792f3)Co-authored-by: Hong Xu <hong@topbug.net>
…on (GH-23960) (GH-29542)* [bpo-45772](): socket.socket should be a class instead of a functionCurrently `socket.socket` is documented as a function, but it is reallya class (and thus has function-like usage to construct an object). Thiscorrection would ensure that Python projects that are interlinkingPython's documentation can properly locate `socket.socket` as a type.(cherry picked from commit4c792f3)Co-authored-by: Hong Xu <hong@topbug.net>Automerge-Triggered-By: GH:asvetlov
GH-23960) (GH-29543)* [bpo-45772](): socket.socket should be a class instead of a functionCurrently `socket.socket` is documented as a function, but it is reallya class (and thus has function-like usage to construct an object). Thiscorrection would ensure that Python projects that are interlinkingPython's documentation can properly locate `socket.socket` as a type.(cherry picked from commit4c792f3)Co-authored-by: Hong Xu <hong@topbug.net>Automerge-Triggered-By: GH:asvetlov
…honGH-23960)* bpo-45772: socket.socket should be a class instead of a functionCurrently `socket.socket` is documented as a function, but it is reallya class (and thus has function-like usage to construct an object). Thiscorrection would ensure that Python projects that are interlinkingPython's documentation can properly locate `socket.socket` as a type.
…honGH-23960)* bpo-45772: socket.socket should be a class instead of a functionCurrently `socket.socket` is documented as a function, but it is reallya class (and thus has function-like usage to construct an object). Thiscorrection would ensure that Python projects that are interlinkingPython's documentation can properly locate `socket.socket` as a type.
Uh oh!
There was an error while loading.Please reload this page.
Currently
socket.socketis documented as a function, but it is reallya 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.socketas a type.https://bugs.python.org/issue45772