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 gvanrossum
Recipients Guido.van.Rossum, gvanrossum, iritkatriel, methane, rhettinger, serhiy.storchaka, terry.reedy
Date 2021-09-03.16:28:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1630686500.35.0.749854416206.issue36521@roundup.psfhosted.org>
In-reply-to
Content
I am still not convinced that it's a good idea to put the docstring in the surrounding code object. I'd like to be able to see it when I introspect a code object, not just when introspecting a function object (I may be analyzing code only, and it's hard to connect the code object with the NEW_FUNCTION opcode in the parent code object -- you have to scan the bytecode, which is fragile.)
History
Date User Action Args
2021-09-03 16:28:20gvanrossumsetrecipients: + gvanrossum, rhettinger, terry.reedy, methane, serhiy.storchaka, Guido.van.Rossum, iritkatriel
2021-09-03 16:28:20gvanrossumsetmessageid: <1630686500.35.0.749854416206.issue36521@roundup.psfhosted.org>
2021-09-03 16:28:20gvanrossumlinkissue36521 messages
2021-09-03 16:28:20gvanrossumcreate