Tried "pip install bpython" on Windows 7, but I get an ImportError: No module named _curses.
[1] http://docs.bpython-interpreter.org/windows.html [2] https://bitbucket.org/bobf/bpython/src/0f88fb19ee697096511d5...
21–30 of 41 posts
Tried "pip install bpython" on Windows 7, but I get an ImportError: No module named _curses.
[1] http://docs.bpython-interpreter.org/windows.html [2] https://bitbucket.org/bobf/bpython/src/0f88fb19ee697096511d5...
Quick warning: Bpython crashes if you need to resize the terminal on OS X. And because it truncates the output to what can fit on the screen, it's essentially unusable for things with a long output. (Because if you need to scroll or resize the window to see the full output, it will crash.) It's amazingly good for most things, but occasionally I need to switch back to the default interpreter.
Also bpython has a pager (F9), so it's definitely fine for long output. The interpreter also will write all output to stdout on quit, so you can do what you'd like then too.
I can't say I ever use the vanilla interpreter anymore other than when testing a bpython bug.
Quick warning: Bpython crashes if you need to resize the terminal on OS X. And because it truncates the output to what can fit on the screen, it's essentially unusable for things with a long output. (Because if you need to scroll or resize the window to see the full output, it will crash.) It's amazingly good for most things, but occasionally I need to switch back to the default interpreter.
I can't say I've ever experienced this. I'll certainly try to reproduce when I get home. Also bpython has a pager (F9), so it's definitely fine for long output. The interpreter also will write all output to stdout on quit, so you can do what you'd like then too. I can't say I ever use the vanilla interpreter anymore other than when testing a bpython bug.
I see BPython has a list of alternative pretty interpreters listed on its page. iPython (that I know of) and DreamPie (that I don 't know of). http://bpython-interpreter.org/alternatives/ Can anyone say how they all compare to each other?
as to bpython vs ipython, last tested it out, bpython still lacked a core feature that ipython has, which is a shell-style history. I can't mention how often I am thinking "hmmm, did'nt I write something like that before", and search backward to find something I wrote a half year ago, or say yesterday...
Earlier quoted context omitted.
I can't say I've ever experienced this. I'll certainly try to reproduce when I get home. Also bpython has a pager (F9), so it's definitely fine for long output. The interpreter also will write all output to stdout on quit, so you can do what you'd like then too. I can't say I ever use the vanilla interpreter anymore other than when testing a bpython bug.
I just got this when doing print 10xx10000. Sometimes it crashes the first time I resize the terminal, sometimes I need to resize it a few times quickly. If you send me a note I can email you the error I get when it crashes.
Otherwise I'll play around a bit.
Earlier quoted context omitted.
I don't know what %edit does, but if I guess that it has something to do with an editor, I use this in my dotfiles: https://github.com/Julian/dotfiles/blob/master/.pythonrc#L55 which is perfectly REPL agnostic. I prefer bpython over iPython for a bunch of reasons that I can't easily elaborate on from here on my mobile, but is definitely suggest people try them both out.
That's pretty nifty - thanks. EDIT: Also, I have used bpython, but since I use python more on the data side as opposed to web (or something not data) IPython along with everything else make it too good to not use.
Tried "pip install bpython" on Windows 7, but I get an ImportError: No module named _curses.
I'm finding it extremely buggy. For example - pressing F8 when no code has been entered yet causes a TypeError. I will post this on the mailing list but considering it's an old (~4yrs?) project I'm surprised such issues haven't been fixed.
Quick warning: Bpython crashes if you need to resize the terminal on OS X. And because it truncates the output to what can fit on the screen, it's essentially unusable for things with a long output. (Because if you need to scroll or resize the window to see the full output, it will crash.) It's amazingly good for most things, but occasionally I need to switch back to the default interpreter.
[1] https://bitbucket.org/bobf/bpython/issue/65/curses-error-on-...