[Python-Dev] trace module options.
All, I've been looking at the trace module, and although it looks useful, I'm surprised that there aren't a couple of features that I would have thought would be fairly basic. So, does trace support (for the --trace option): - indentation tracking stacklevel (where each function is prefixed by tabs equal to the number of stacklevels deep in the program) - output to something other than sys.stdout (eg. output to a file specified either by environmental variable or by parameter). - mult-threaded programs going to multiple output handles, especially in light of the above - fully qualified python modules in path: (eg: /path/to/module/my_module.py(1): print "HERE" instead of my_module.py(1): print "HERE". Ultimately, I'd like to be able to look at two runs of a program and be able to pinpoint the very first difference between thembased on the output of their trace runs. As it stands, I really can't do this. Of course I could program the above, but I was hoping to avoid duplicated effort if someone has already programmed options like this.. Ed ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] trace module options.
> On-topic would have been a disussion of which of these features would > be useful for the trace module to be built-in, how to best provide them, > along with an offer to produce a patch. Ok, fair enough - which of the features listed (indentation matching stacklevel, output to a file (or files wrt threading, fully qualified output) should be builtin, which should be options, which should be left out, and based on the above, would a patch like this be accepted? Ed (ps - I'll also take it to python-list) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] command line attachable debugger
all, I'I was wondering if there was a command line python debugger that was able to attach to an existing process. I'd very much like to be able to debug over a ssh session using screen. Ed (ps - and yes, I know about winpdb, etc... that is not exactly what I'm looking for..) ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] command line attachable debugger
> Winpdb is *exactly* what you asked for, so if it's not what you're looking > for you'll need to be more specific about what you want that it doesn't > do... > > James > Fair enough, I was assuming that winpdb didn't have a command line interface, but I was mistaken (rpdb2). In any case, I would argue that attach functionality is something that should be put into the core, along with pdb, as a standard. What if I want to use pudb? or pydb? or the interface which goes with perl? There should be a standard mechanism for debuggers to talk to a python process; not one-offs for each debugger, probably at the level of the python executable (the same way that gcc lets gdb attach with a pid.. Ed ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
