A new Python REPL #111201
Description
Activity
If you want to help with this endeavour, please mention it here so we can coordinate everyone!
I have a initial version that we can start building upon, I will create a PR shortly.
Reacted by Lysandros NikolaouI learned about this from the "core.py" podcast and it sounds like a great idea! I'd be happy help with this effort :)
- added a commit that references this issue
on Oct 31, 2023 Fallback to the previous tokenizer-based REPL if the terminal is not a tty (and for backwards compat reasons)
Do you mean not using _pyrepl? Can _pyrepl be used without readline nor tty?
Can _pyrepl be used without readline nor tty?
It needs at least a tty yes. Readline can be lifted but I am not sure yet
- added a commit that references this issue
on Apr 27, 2024 I would like to see a new REPL (read, evaluate, print, loop) for the Python interpreter if the interpreter goes by a different name. Two other major Python interpreters also exist, and they already use other names ("bpython" and "ipython"). I would recommend forking the current REPL and renaming the interpreter with the new REPL to "zpython" instead. Also, I would like to see a built-in "clear()" function in the REPL as I already encounter with the "exit()" function and other REPL-specific functions.
- added a commit that references this issue
on May 5, 2024 Big feature without PEP?
116 remaining items
- added 6 commits that reference this issue
on Jul 17, 2024 - added a commit that references this issue
on Sep 6, 2024 I think we can close this and handle the rest of the bugs in individual issues. Feel free to re-open if you feel otherwise.
Reacted by Victor StinnerReacted by Alex WaygoodThanks to all the participants, this is amazing! I really enjoy its increased portability!
Reacted by Alex WaygoodI absolutely love this change! I was using 3.12 and was thinking about making the change myself when I found this. Thank you all for your dedication!
This issue will track all the different steps to bootstrap a new Python REPL with many new features. The target of this issue is that we can reach a point where new contributions can be made easily to the REPL once is written in pure Python. This issue only coveres the initial ground work to reach this status.
Tasks to be done:
Linked PRs