GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||
GeezerVison is showing github.com — gh-82406: document duck-type nature of inspect.is*function by graingert · Pull Request #94987 · python/cpython Conversation
|
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Documentation build overview
8 files changed ·
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
Consider different wording, not "duck-type functions".
Maybe function-like objects? I've seen that a couple times in the docs. If we go the duck-type path, maybe link to the glossary (:term:`duck-typing`)?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Bartosz Sławecki <[email protected]>
Review feedback: use "function-like objects" and link the duck-typing glossary term rather than saying "duck-type functions". This matches the wording already used in the NEWS entry for pythongh-84753.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
@encukou, what do you think?
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
As a tightly scoped PR, this makes sense.
"function-like objects now return True" technically isn't true, but the same wording is in the notes above and below.
"Duck-typed function-like objects" is vague, but if we wanted precision, that should go in the main prose, not in a versionchanged note.
I could do without the comments in inspect.py, but they're not harmful.
I removed the NEWS entry though; we don't add those for docs.
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Thanks @graingert for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks @graingert for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks @graingert for the PR, and @encukou for merging it 🌮🎉.. I'm working now to backport this PR to: 3.15. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-156880 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-156881 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
GH-156882 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
…94987) (#156881) Document when these functions started checking code flags for "duck-typed" function-like objects. (cherry picked from commit 1059e80) Co-authored-by: Thomas Grainger <[email protected]>
…94987) (#156880) Document when these functions started checking code flags for "duck-typed" function-like objects. (cherry picked from commit 1059e80) Co-authored-by: Thomas Grainger <[email protected]>
…onGH-94987) Document when these functions started checking code flags for "duck-typed" function-like objects.
…94987) (GH-156882) Document when these functions started checking code flags for "duck-typed" function-like objects. (cherry picked from commit 1059e80) Co-authored-by: Thomas Grainger <[email protected]>
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.