[Python-Dev] pdb mini-sprint report and questions (original) (raw)
Georg Brandl g.brandl at gmx.net
Sat Jul 31 01:07:47 CEST 2010
- Previous message: [Python-Dev] pdb mini-sprint report and questions
- Next message: [Python-Dev] pdb mini-sprint report and questions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 31.07.2010 01:01, schrieb Guido van Rossum:
On Fri, Jul 30, 2010 at 3:45 PM, Georg Brandl <g.brandl at gmx.net> wrote:
to warm up for tomorrow's 3.2alpha1 release, I did a mini-sprint on pdb issues today. I'm pleased to report that 14 issues could be closed, and pdb got a range of small new features, such as commands on the command line, "until " or "longlist" showing all the code for the current function (the latter courtesy of Antonio Cuni's pdb++).
One issue that's not yet closed is #7245, which adds a (very nice IMO) feature: when you press Ctrl-C while the program being debugged runs, you will not get a traceback but execution is suspended, and you can debug from the current point of execution -- just like in gdb. However, there were apparently issues with some of the buildbots when the patch was applied for a short time. I also don't know how and if it works on Windows, so I'd need some helpful people testing it. Another question is about a feature of pdb++ that I personally would like, but imagine would make others unhappy: one-letter abbreviations of commands such as c(ontinue) or l(ist) are also often-used variable names, so they are frequently typed without the required "!" or "print" that would distinguish them from the command, and the command is actually executed. The feature in question would default to printing the variable in cases where one exists -- handy enough or too inconsistent? Warning: 'p' is not the same as 'print'. 'p' is a built-in command that prints the expression's repr(). 'print' OTOH falls back through the interpreter and executes a print statement or function, which prints the str().
Not in py3k -- 'print' is an alias for 'p' there, otherwise 'print x' would be a syntax error.
For me personally, the problem this feature tries to address is never a problem (of course I am probably unique as far as pdb users go :-) so I'd like a way to turn it off.
Also, are there any other features you would like to see? One feature of pdb++ that is general enough and has no dependencies would be watch expressions... Cool.
I take it you'd like to see them? ;)
Georg
-- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out.
- Previous message: [Python-Dev] pdb mini-sprint report and questions
- Next message: [Python-Dev] pdb mini-sprint report and questions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]