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 pablogsal
Recipients FFY00, p-ganssle, pablogsal, steven.daprano, theacodes, tlalexander, veky
Date 2021-07-12.14:03:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1626098592.69.0.0151792871776.issue44603@roundup.psfhosted.org>
In-reply-to
Content
> would be in the REPL layer by special-casing `exit`

Unfortunately, there is no REPL *layer* as my previous comments mentioned.

There is a few details that change for interactive mode but fundamentally the pipeline is the same as reading from a file, except that the file is stdin and it has some special logic in the parser to do that in a lazy way and fail fast. But there is no semantic information that separates REPL for non-REPL.
History
Date User Action Args
2021-07-12 14:03:12pablogsalsetrecipients: + pablogsal, steven.daprano, veky, p-ganssle, FFY00, theacodes, tlalexander
2021-07-12 14:03:12pablogsalsetmessageid: <1626098592.69.0.0151792871776.issue44603@roundup.psfhosted.org>
2021-07-12 14:03:12pablogsallinkissue44603 messages
2021-07-12 14:03:12pablogsalcreate