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 larry
Recipients gvanrossum, larry, ncoghlan, pitrou, serhiy.storchaka, skrah
Date 2014-01-07.12:06:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1389096416.22.0.990075827139.issue19723@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine just suggested that, if we used this "accumulator" thing, we'd want a convention for where the generated text should go.  I actually have an answer for that: near the end, below the implementations of the module / class methods, but above the methoddef/type structures and the module init function.

My reasoning: when I navigate CPython C files implementing a module or a type, when I know what entry point I want I just search for its name.  When I don't know what I want, I jump to the end, then scroll up until I find the name in the init function or the structures.  So I wouldn't want the code at the very end; that would screw up that navigation mode.
History
Date User Action Args
2014-01-07 12:06:56larrysetrecipients: + larry, gvanrossum, ncoghlan, pitrou, skrah, serhiy.storchaka
2014-01-07 12:06:56larrysetmessageid: <1389096416.22.0.990075827139.issue19723@psf.upfronthosting.co.za>
2014-01-07 12:06:56larrylinkissue19723 messages
2014-01-07 12:06:55larrycreate