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 aliles
Recipients aliles, asvetlov, cjw296, eric.araujo, kristjan.jonsson, ncoghlan
Date 2012-12-08.21:44:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CANmusTKgJQLCEc_SaeXYFtpjdTb3F1P+1ZAC4TZK_bHCA9zpKg@mail.gmail.com>
In-reply-to <1354979980.72.0.932711619444.issue7741@psf.upfronthosting.co.za>
Content
Should a new issue be created to decouple "print after every call" from the
single vs multiple statement condition that is a blocker for this issue? Or
can it be resolved here?

On Sunday, 9 December 2012, Nick Coghlan wrote:

>
> Nick Coghlan added the comment:
>
> OK, after a long detour that delved deep into codeop and the vagaries of
> PyCF_DONT_IMPLY_DEDENT (due to a problem that turned out to be due to a
> missing "\n" in a test case I added), my main conclusion is:
>
> Coupling the "single vs multiple statement" decision to the "implicit
> print after every call" decision is *really* annoying. The latter should be
> its own flag *or else* also implied by the "DONT_IMPLY_DEDENT" flag that is
> already passed to the compiler by codeop.
>
> If *that* gets fixed, then the code module could simply switch over to
> compiling in exec mode always, without any side effects on the implicit
> display of expression results.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org <javascript:;>>
> <http://bugs.python.org/issue7741>
> _______________________________________
>
History
Date User Action Args
2012-12-08 21:44:56alilessetrecipients: + aliles, ncoghlan, kristjan.jonsson, cjw296, eric.araujo, asvetlov
2012-12-08 21:44:56alileslinkissue7741 messages
2012-12-08 21:44:56alilescreate