This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author peteroupc
Recipients docs@python, peteroupc
Date 2020-01-19.23:03:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1579475037.48.0.632958566945.issue39391@roundup.psfhosted.org>
In-reply-to
Content
It appears that if a method has default parameters set to functions, as in this example:

    def f1():
        pass

    def f2(a, b=f1):
        pass

The resulting Pydoc output produces a different, nondeterministic rendering for the f2 method each time it generates the documentation, such as `m1(a, b=<function f1 at 0x7f4ff67f8950>)` or `m1(a, b=<function f1 at 0x7f4ff67f8950>)`.  And this is problematic for version control systems, among other things, especially since this is not a meaningful change to the documentation.

One solution may be to write, say, `m1(a, b=f1)` instead.
History
Date User Action Args
2020-01-19 23:03:57peteroupcsetrecipients: + peteroupc, docs@python
2020-01-19 23:03:57peteroupcsetmessageid: <1579475037.48.0.632958566945.issue39391@roundup.psfhosted.org>
2020-01-19 23:03:57peteroupclinkissue39391 messages
2020-01-19 23:03:57peteroupccreate