←back to thread

PEP 762 – REPL-acing the default REPL

(peps.python.org)
89 points Numerlor | 2 comments | 14 Oct 24 19:25 UTC | HN request time: 0.001s | source
Show context
klreslx ◴[15 Oct 24 18:31 UTC] No.41851609[source]▶
I don't see the point. People who want Jupyter or an IDE know where to find it. Other people who want the basic REPL and mostly use editors anyway are annoyed.

Well, perhaps the usual suspects can get another infoworld self-promotion article out of it.

replies(5): >>41851731 #>>41851796 #>>41852422 #>>41852924 #>>41853980 #
1. Numerlor ◴[15 Oct 24 19:51 UTC] No.41852422[source]▶
From my experience working with the default repl in e.g. a docker container is extremely frustrating comparing to ipython, and I don't want to be installing ipython and its multitude of dependencies everywhere
replies(1): >>41854017 #
2. zahlman ◴[15 Oct 24 23:05 UTC] No.41854017[source]▶
I've never actually used these industrial-strength "containers" before, but I had understood that they're supposed to be primarily for deployment, or at least some automated testing step in a big CI system. Why would the REPL come into play for these use cases?