This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author isandler
Recipients
Date 2006-06-25.16:25:57
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=971153

...1.Why?bdb.py prints informations about breakpoints to
stdout in bpprint function....

I am not sure printing to stdout in bpprint was a good
decision! Really, if bdb is intended to be a low-level
debugging module, it should not print anything to stdout...

..I included new patch.What's your opinion?...

A couple of comments:
 1) the latest pdb's output goes through redirection. The
patch does not..
 2) Is it really necessary to restrict pdb's run() to
strings? Being able to pass a code object seems like a
useful thing (I know that pdb docs explicitly say that the
1st arg must be a string)
 3) finally, I guess I am not sure about the general
approach to argument type checking in stdlib. 
(is it really pdb's business to check run() arguments? E.g
if bdb's run() supports other types (say, UserString or
file), pdb's type checking would have to change)...


I guess, I am  -0 on this patch..
History
Date User Action Args
2007-08-23 15:48:23adminlinkissue1472257 messages
2007-08-23 15:48:23admincreate