This looks interesting and I will definitely play with it, fortunately it's already in the Arch repositories. I must admit I immediately clicked "FAQ" expecting

This looks interesting and I will definitely play with it, fortunately it's already in the Arch repositories. I must admit I immediately clicked "FAQ" expecting the first entry to be "How this project is different from ipython", since that's the obvious alternative that everyone has already heard of, but I didn't see anything. Perhaps oddly, the reason why I almost always use the default Python shell is the following: ipython -c ";" 0.68s user 0.08s system 96% cpu 0.783 total bpython -c "" 0.72s user 0.08s system 99% cpu 0.800 total pypy3 -c "" 0.11s user 0.06s system 91% cpu 0.188 total python -c "" 0.03s user 0.00s system 98% cpu 0.035 total I realize of course that this is stupid and irrational, that the time it takes to launch the interpreter is entirely negligible compared to the amount of time I'll spend working in it (e.g. wasting time having to insert spaces manually instead of having auto-indent), but there's something painful enough about the 0.8 second start time (on an SSD no less!) of these fancy interpreters that I almost always find myself going for standard Python.