David Rogers <[email protected]> writes: > Thank you very much for creating PuDB. I don't work in Python often, but I > sometimes need to create small scripts for work. > > Your PuDB is just what I was looking for. The ability to debug visually > without a large investment in setting up and learning a specialized > development environment.
Glad to hear you're finding pudb useful. > I do have a couple of suggestions: > > * At the root level of execution, the Variables window shows the imports. > I think an option to hide these would be great. Do you mean imported symbols? (i.e. from "from something import *"?) Or module names? > * When you expand a complicated class/variable and scroll down, you > can lose track of the parent. It would be useful to have a key that > would scroll the variables and take you back to the parent. That's a good idea. I'd be happy to take a patch. > * I did (after a time) figure out how to get back from the variables > window to the source code. But I think it would be nice to have an > instant key for the source window like V,S,and B work for those > windows. Maybe C for Code? Implemented in git, but no bar with an underscore "C" to retain good use of vertical space. (but the key is shown in the help window) Andreas
pgpcfvFqMkCXq.pgp
Description: PGP signature
_______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
