Message401003
| 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:20 | gvanrossum | set | recipients: + gvanrossum, rhettinger, terry.reedy, methane, serhiy.storchaka, Guido.van.Rossum, iritkatriel |
| 2021-09-03 16:28:20 | gvanrossum | set | messageid: <1630686500.35.0.749854416206.issue36521@roundup.psfhosted.org> |
| 2021-09-03 16:28:20 | gvanrossum | link | issue36521 messages |
| 2021-09-03 16:28:20 | gvanrossum | create | |