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 Mark.Shannon
Recipients Guido.van.Rossum, Mark.Shannon, gvanrossum, iritkatriel, methane, rhettinger, serhiy.storchaka, terry.reedy
Date 2021-09-29.10:04:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1632909893.2.0.814323024925.issue36521@roundup.psfhosted.org>
In-reply-to
Content
There is a clear disadvantage in moving the docstring from the function's code object to the enclosing code object:

Docstrings are rarely looked at (relative to other operations on functions). Inner functions and comprehensions are created many times for the same code object, and their docstring are (almost) never inspected.

Given that, the obvious enhancement is to create docstrings lazily to reduce the overhead of creating a function.

This change would prevent that enhancement.
History
Date User Action Args
2021-09-29 10:04:53Mark.Shannonsetrecipients: + Mark.Shannon, gvanrossum, rhettinger, terry.reedy, methane, serhiy.storchaka, Guido.van.Rossum, iritkatriel
2021-09-29 10:04:53Mark.Shannonsetmessageid: <1632909893.2.0.814323024925.issue36521@roundup.psfhosted.org>
2021-09-29 10:04:53Mark.Shannonlinkissue36521 messages
2021-09-29 10:04:53Mark.Shannoncreate