Author minrk
Recipients Mark.Shannon, benjamin.peterson, flherne, georg.brandl, inada.naoki, lukasz.langa, minrk, ned.deily, rhettinger, serhiy.storchaka, vstinner
Date 2018-05-25.09:59:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527242368.43.0.682650639539.issue32911@psf.upfronthosting.co.za>
In-reply-to
Content
In the A/B vote, I cast mine for B, for what it is worth, but it is not strongly held.

From the IPython side, I don't view our particular issue as a major regression for users. The only affected case for us is interactively typed string literals in single statement cells not displaying themselves as results. Since the same string is necessarily already displayed in the input, this isn't a huge deal. This is pretty rare (maybe folks do this while investigating unicode issues?) and we can handle it by recompiling empty modules with 'single' instead of the usual 'exec' that we use because most IPython inputs are multi-statement cells coming from things like notebooks. It's relevant to note that *any* logic in the cell, e.g. `"%i" % 1` or additional statements have no issues.

The proposed 'muliline' or 'interactive' compile mode would suit IPython very well, since that's what we really want - single * N, not actually a module, and this is illustrated by the way we do execution: compile with exec, then iterate through module.body and run the nodes one at a time.
History
Date User Action Args
2018-05-25 09:59:28minrksetrecipients: + minrk, georg.brandl, rhettinger, vstinner, benjamin.peterson, ned.deily, inada.naoki, lukasz.langa, Mark.Shannon, serhiy.storchaka, flherne
2018-05-25 09:59:28minrksetmessageid: <1527242368.43.0.682650639539.issue32911@psf.upfronthosting.co.za>
2018-05-25 09:59:28minrklinkissue32911 messages
2018-05-25 09:59:28minrkcreate