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 terry.reedy
Recipients FFY00, asmeurer, eric.araujo, gregory.p.smith, jack__d, mark.dickinson, p-ganssle, pablogsal, steven.daprano, terry.reedy, theacodes, tlalexander, veky
Date 2021-07-17.03:32:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1626492763.78.0.868052534837.issue44603@roundup.psfhosted.org>
In-reply-to
Content
This has been proposed and rejected before.  So I think a pydev discussion and steering council decision would be needed to change.

The current rule in interactive mode is that typing an expression statement echoes the representation of the resulting object.  The proposal is make a rather startling exception to the rule.  The premise is that "the program knows what I meant".

However, that is a too-successful illusion.  'The program' has no idea what one meant other than to print the repr(ob).  Some coredevs had the idea to *guess* what was meant and to give two functions an exceptional representation with a message that would be correct when the guess is correct.

In the other hand, special-casing 'quit\n' and 'exit\n' could be seen as analogous to special-casing '^Z\n'.  And the patch restricts the special casing, without complicated code, to exactly those sequences of keystrokes.
History
Date User Action Args
2021-07-17 03:32:43terry.reedysetrecipients: + terry.reedy, gregory.p.smith, mark.dickinson, eric.araujo, steven.daprano, veky, p-ganssle, pablogsal, asmeurer, FFY00, theacodes, jack__d, tlalexander
2021-07-17 03:32:43terry.reedysetmessageid: <1626492763.78.0.868052534837.issue44603@roundup.psfhosted.org>
2021-07-17 03:32:43terry.reedylinkissue44603 messages
2021-07-17 03:32:43terry.reedycreate