Re:Pudb – A full-screen, console-based Python debugger
by greenyoda on Sunday September 29, 2013 @07:16PM
(#6466965)
Pudb depends on the "termios" module (POSIX style tty control), whose doc says it's only available under Unix.[1] Does anyone know if there's a way to make it run on Windows (native Windows command prompt, not Cygwin)?
Re:Pudb – A full-screen, console-based Python debugger
by a3n on Monday September 30, 2013 @01:10AM
(#6467909)
Or ssh (putty or your favorite windows ssh) into a vagrant box and use PuDB or whatever you like.
I'm beginning to see vagrant as cygwin's competition. Not quite a killer, because you can't run windows progs from vagrant/linux like you can from cygwin, but for most cygwin scenarios vagrant with a real *nix is much nicer.
Best of both worlds, ssh into vagrant from cygwin.
Re:Pudb – A full-screen, console-based Python debugger
by teddyh on Monday September 30, 2013 @05:31AM
(#6468575)
"Curses" actually refers to "curses". "ncurses" is new curses. From Wikipedia:
“[…] ncurses is a free software emulation (clone) of the System V Release 4.0 (SVr4) curses, which was itself an enhancement over the discontinued classic 4.4 BSD curses.”
Re:Pudb – A full-screen, console-based Python debugger
by shruubi on Sunday September 29, 2013 @08:13PM
(#6467123)
Just tried this out, and I must say, this is really freakin' cool! Simple controls, intuitive layout. I don't feel like I'm fighting the debugger to get it do to what I want anymore.
Re:Pudb – A full-screen, console-based Python debugger
by publicfig on Sunday September 29, 2013 @07:50PM
(#6467057)
Cant wait to try this out in my workflow, but I really wish this was available through PIP. PDB has served me well, but having some if this information intuitively shown will be incredibly helpful.
Re:Pudb – A full-screen, console-based Python debugger
by StavrosK on Sunday September 29, 2013 @07:04PM
(#6466915)
I have recently tried PuDB, and, I have to say, it is pretty damn nice. Never again will I use pdb/ipdb for debugging, now I can actually debug like a human being!
[1] http://docs.python.org/2/library/termios.html
I'm beginning to see vagrant as cygwin's competition. Not quite a killer, because you can't run windows progs from vagrant/linux like you can from cygwin, but for most cygwin scenarios vagrant with a real *nix is much nicer.
Best of both worlds, ssh into vagrant from cygwin.
this allows me to set up the debugger in some code on my dev box and run winpdb on my own box.
[1] A reference to ncurses.
[2] The book: http://web.mit.edu/~simsong/www/ugh.pdf
[3] ... as in why make a UI for a constrained primitive interface such as a console....
(The book was published in 1994.)
“[…] ncurses is a free software emulation (clone) of the System V Release 4.0 (SVr4) curses, which was itself an enhancement over the discontinued classic 4.4 BSD curses.”
[1] http://pybee.org/bugjar/