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.15:27:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1626103660.19.0.125655420788.issue44603@roundup.psfhosted.org>
In-reply-to
Content
> Are there any downsides to doing it this way? It seems tightly scoped and with minimal overhead.

We also need to support quit(), if we go this route.

It makes parsing in the REPL a bit slower because it needs to check for this at every command and is a bit "floating" in the middle of the parser and the compiler (but that's a consequence that we don't have any defined layer for this). We also need to check that this also works with piping input.

Other than that, only arguments based on the purity of the language, but I think having this working is far more important.
History
Date User Action Args
2021-07-12 15:27:40pablogsalsetrecipients: + pablogsal, steven.daprano, veky, p-ganssle, FFY00, theacodes, tlalexander
2021-07-12 15:27:40pablogsalsetmessageid: <1626103660.19.0.125655420788.issue44603@roundup.psfhosted.org>
2021-07-12 15:27:40pablogsallinkissue44603 messages
2021-07-12 15:27:40pablogsalcreate