gh-155013: Reword a reference to partial object in functools - #155036
Conversation
Rather than referring to a `` :func:`!partial` object``, use a reference to the definition of a "partial object", provided as a part of the functools docs. This results in two linked references from `functools.partial` docs to `partial object`, as there is another one at the top of the docstring. However, the doc is sufficiently long that this second link is likely to be beneficial to a reader.
Documentation build overview
|
Co-authored-by: Stan Ulbrych <stan@python.org>
|
Thanks @sirosen for the PR, and @StanFromIreland for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15. |
|
GH-155093 is a backport of this pull request to the 3.15 branch. |
|
Sorry, @sirosen and @StanFromIreland, I could not cleanly backport this to |
|
GH-155094 is a backport of this pull request to the 3.14 branch. |
|
I ran I don't think any further action is needed, but I wanted to note it, in case anyone sees this and wonders about the missing backport. |
|
Hey Stephen, JFYI so you don't waste your time, if someone removes the backport label it's generally because they've decided it's not applicable. |
…unctools.partial()` doc (pythonGH-155036) (python#155094) (cherry picked from commit 204feba) Co-authored-by: Stephen Rosen <sirosen@globus.org> Co-authored-by: Stan Ulbrych <stan@python.org>
Rather than referring to a
:func:`!partial` object, use a reference to the definition of a "partial object", provided as a part of the functools docs.This results in two linked references from
functools.partialdocs topartial object, as there is another one at the top of the docstring.However, the doc is sufficiently long that this second link is likely to be beneficial to a reader.
functools.partial()refers topartial()where it should refer topartial object#155013