Author JDLH
Recipients JDLH, eryksun
Date 2017-02-15.23:10:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487200239.34.0.28446430814.issue29561@psf.upfronthosting.co.za>
In-reply-to
Content
Thank you for the analysis, Eryk Sun.

You wrote, "the interpreter is correctly conveying that it's still tokenizing the input; it hasn't compiled or executed any code." I think one important question for this issue is, what meaning should the choice of prompt convey?  That breaks down into, 1. what meaning does the user believe it conveys, and 2. what meaning does the present behaviour of the code imply?

"it's still tokenizing the input" translates to a meaning, sys.ps1 indicates the interpreter just finished executing and has no input, while sys.ps2 indicates the interpreter is tokenizing input and awaiting a chance to execute.

I think my intuition is, and the bash shell's behaviour says, sys.ps1 indicates the interpreter is ready to start a new statement, and sys.ps2 indicates the interpreter is in the midst of a compound statement.
History
Date User Action Args
2017-02-15 23:10:39JDLHsetrecipients: + JDLH, eryksun
2017-02-15 23:10:39JDLHsetmessageid: <1487200239.34.0.28446430814.issue29561@psf.upfronthosting.co.za>
2017-02-15 23:10:39JDLHlinkissue29561 messages
2017-02-15 23:10:39JDLHcreate