Re: How to get atexit hooks to run in the presence of execv?

Mark Wooding writes: > ro...@panix.com (R. Bernstein) writes: > >> Recently, I added remote debugging via TCP sockets. (Well, also FIFO's >> as well but closing sockets before restarting is what's of concern.) >> >> I noticed that execv in Python 2.5.2 doe

How to get atexit hooks to run in the presence of execv?

As a hobby I've been (re)writing a debugger. One of the commands, "restart", works by calling an execv(). You may need to do this when the program you are debugging is threaded or when one needs to ensure that all program state is reinitialized. Recently, I added remote debugging via TCP sockets.

Re: How do I DRY the following code?

"Patrick Mullen" writes: >> f1(...): >> "Docstring f1" >> c = C() >> return c.f1(...) >> >> f2(...): >> "Docstring f2" >> c = C() >> return c.f2(...) > > Why not just do either this: > C().f2(..) where you need f2 Yes, this is a little better. Thanks! -- http://mail.python.org/mailman/listi

Re: How do I DRY the following code?

Steven D'Aprano writes: > On Mon, 29 Dec 2008 21:13:55 -0500, R. Bernstein wrote: > >> How do I DRY the following code? >> >> class C(): > [snip code] > > Move the common stuff into methods (or possibly external functions). If > you really need to, mak

How do I DRY the following code?

How do I DRY the following code? class C(): def f1(self, arg1, arg2=None, globals=None, locals=None): ... unique stuff #1 ... ... some common stuff #1 ... ret = eval(args, globals, locals) ... more stuff #2 ... return retval def f2(self, arg1, arg2=None, *args,

Re: linecache vs egg - reading line of a file in an egg

Robert Kern writes: > R. Bernstein wrote: >> Does linecache work with source in Python eggs? If not, is it >> contemplated that this is going to be fixed or is there something else >> like linecache that currently works? > > linecache works with eggs and other zippe

linecache vs egg - reading line of a file in an egg

Does linecache work with source in Python eggs? If not, is it contemplated that this is going to be fixed or is there something else like linecache that currently works? Right now, I think pdb and pydb (and probably other debuggers) are broken when they try to trace into code that is part of an eg

Re: Deeper tracebacks?

"Gabriel Genellina" writes: .. > No, last_traceback is the last *printed* traceback in the interactive > interpreter. Well more precisely the traceback that is passed to sys.excepthook() when an unhandled exception occcurs, since the hook that might not decide to print anything ;-) > Use the t

Re: pydb 1.24

J Kenneth King writes: > > I watched the demo video, look forward to working with it. Any links to > that emacs front-end being used in the video? > > Cheers and thanks! In short, the emacs code is bundled in with the tar and should be installed when you run "make install" However if you inst

Custom debugger trace hooks

A colleague recently asked this: Is there a cleaner way to dump a trace/track of running a python script. With Pydb I made work-around with import pydb pydb.debugger(dbg_cmds=['bt', 'l', 's']*300 + ['c']) So now I have a dump of 300 steps with backtraces, so I can easily compar

Re: sys.settrace 'call' event behavior

On Jun 21, 8:47 am, Michal Kwiatkowski <[EMAIL PROTECTED]> wrote: > I'm building a tool to trace all function calls usingsys.settrace > function from the standard library. One of the awkward behaviors of > this facility is that the class definitions are reported as 'call' > events.[1] Since I don't

Re: Deeper tracebacks?

brooklineTom <[EMAIL PROTECTED]> writes: > I want my exception handler to report the method that originally > raised an exception, at the deepest level in the call-tree. Let give > an example. > > import sys, traceback > class SomeClass: > def error(self): > """Raises an AttributeError

Re: trace module and doctest

On Nov 22 2007, 4:31 pm, [EMAIL PROTECTED] (John J. Lee) wrote: > [EMAIL PROTECTED] writes: > > I am trying to use thetracemodulewith the --count flag to test for > > statement coverage in my doctests. Thetracecoverage listing is very > > weird, marking many statements as unexecuted which were cle

pydb 1.24

This release is to clear out some old issues. It contains some bugfixes, document corrections, and enhancements. Tests were revised for Python 2.6 and Python without readline installed. A bug involving invoking from ipython was fixed. The "frame" command is a little more like gdb's. Exceptions are

Re: handling uncaught exceptions with pdb?

"Diez B. Roggisch" <[EMAIL PROTECTED]> writes: > R. Bernstein schrieb: >> Paul Rubin <http://[EMAIL PROTECTED]> writes: >> >>> I think I've asked about this before, but is there a way to set up >>> Python to handle uncaught excep

Re: handling uncaught exceptions with pdb?

Paul Rubin writes: > I think I've asked about this before, but is there a way to set up > Python to handle uncaught exceptions with pdb? I know about setting > sys.except_hook to something that calls pdb, but this is normally done > at the outer level of a program, and

Re: pdb bug and questions

Stef Mientki <[EMAIL PROTECTED]> writes: > From: Stef Mientki <[EMAIL PROTECTED]> > Subject: Re: pdb bug and questions > Newsgroups: comp.lang.python > To: "python-list@python.org" > Date: Fri, 05 Sep 2008 22:06:19 +0200 > > R. Bernstein wrote:

Re: pdb bug and questions

Stef Mientki <[EMAIL PROTECTED]> writes: > hello, > > I'm trying to embed a debugger into an editor. > I'm only interested in high level debugging. > The first question is what debugger is the best for my purpose ? > (pdb, pydb, rpdb2, smart debugger, extended debugger ? > > Second question, in no

Re: pdb bug and questions

castironpi <[EMAIL PROTECTED]> writes: > On Sep 4, 4:22 pm, Stef Mientki <[EMAIL PROTECTED]> wrote: >> hello, >> >> I'm trying to embed a debugger into an editor. >> I'm only interested in high level debugging. >> The first question is what debugger is the best for my purpose ? >> (pdb, pydb, rpdb

Re: Debugging of a long running process under Windows

Tim Golden <[EMAIL PROTECTED]> writes: > R. Bernstein wrote: >> I don't know how well Microsoft Windows allows for sending a process a >> signal in Python, but if the Python signal module works reasonably >> well on Microsoft Windows, then reread >> http:

Re: Debugging of a long running process under Windows

I don't know how well Microsoft Windows allows for sending a process a signal in Python, but if the Python signal module works reasonably well on Microsoft Windows, then reread http://bashdb.sourceforge.net/pydb/pydb/lib/node38.html Should you not want to use or can't use pydb, or want to do this

Re: handling unexpected exceptions in pdb

Simon Bierbaum <[EMAIL PROTECTED]> writes: > Hi all, > > I'm in an interactive session in pdb, debugging my code using > pdb.runcall. Somewhere, an exception is raised and lands uncaught on > stdout. Is there any way of picking up this exception and at least > read the full message, or even access

Re: Debuggers

TheSaint <[EMAIL PROTECTED]> writes: > On 19:21, venerdì 13 giugno 2008 R. Bernstein wrote: > >> I'm not completely sure what you mean, but I gather that in >> post-mortem debugging you'd like to inspect local variables defined at the >> place of error. >

Re: Debuggers

TheSaint <[EMAIL PROTECTED]> writes: > Hi, > > while testing my program I found some strange happening with pdb and pydb. > > I like pydb because let me restart the program and nicer features, but if > errors pop up, then it will forget all variables (globals and locals gone). I'm not completely

Re: pydb remote debugging/cmd.Cmd over socket?

"Diez B. Roggisch" <[EMAIL PROTECTED]> writes: > Hi, > > I'm fiddling around with pydb. Installation and usage are fine. What I > especially like is the fact that you can attach a signal such that you drop > into debugging mode on demand. > > But this is of limited use to me in situations where a

Possibly pydb 1.23 release around May 30

A release of pydb (1.23) is currently scheduled for around May 30th. If you can and want to help make sure the release is okay, you can try out what is currently in CVS: http://sourceforge.net/cvs/?group_id=61395 I've put an interim tar at http://bashdb.sf.net/pydb-1.23cvs.tar.gz Changes in

Re: Running an interactive interpreter inside a python

castironpi <[EMAIL PROTECTED]> writes: > On May 15, 6:26 am, [EMAIL PROTECTED] (R. Bernstein) wrote: >> "Alan J. Salmoni" <[EMAIL PROTECTED]> writes: >> >> > I'm not sure if this is exactly what you're after, but try looking >>

Re: Running an interactive interpreter inside a python

d come from a stackframe f_globals. It might be possible to save and restore __main__.__dict__ before and after the call to interact(). Probably would have been cooler to design interact() to take a globals parameter, same as eval does. > > On May 15, 11:31 am, [EMAIL PROTECTED] (R.

Running an interactive interpreter inside a python

The next release of pydb will have the ability to go into ipython from inside the debugger. Sort of like how in ruby-debug you can go into irb :-) For ipython, this can be done pretty simply; there is an IPShellEmbed method which returns something you can call. But how could one do the same for th

Re: using pdb and catching exception

Just checked to see how Ruby deals with this. Both languages allow one to register a trace functon to catch "events" like call, line, return, exception, etc. Ruby however register an event before the raise takes place. It might be cool for some good person to go through the process of making a for

Re: how to change current working directory while using pdb within emacs

duyanning <[EMAIL PROTECTED]> writes: > I have written a pyhton script that will process data file in current > working directory. > My script is in an different directory to data file. > When I debug this script using pdb within emacs, emacs will change the > current working directory to the dire

Re: Emacs and pdb after upgrading to Ubuntu Feisty

levander <[EMAIL PROTECTED]> writes: > I've been using pdb under emacs on an Ubuntu box to debug python > programs. I just upgraded from Ubuntu Edgy to Feisty and this combo > has stopped working. Python is at 2.5.1 now, and emacs is at 21.41.1. If I had to take a guess the big change would be

Re: Help controlling CDROM from python

If you want an OS neutral way one may be able to use pycdio from the Cheese shop. It requires libcdio to be installed and that sometimes the case if you have a free media player (like vlc or xine, or mplayer) installed. I don't really use it all that often so I can't vouch for how good it is. (Al

Re: Debugging SocketServer.ThreadingTCPServer

"Stuart D. Gathman" <[EMAIL PROTECTED]> writes: > On Tue, 16 Jan 2007 09:11:38 -0500, Jean-Paul Calderone wrote: > > > On Tue, 16 Jan 2007 00:23:35 -0500, "Stuart D. Gathman" > > <[EMAIL PROTECTED]> wrote: > >>I have a ThreadingTCPServer application (pygossip, part of > >>http://sourceforge.net/p

Re: Possible bug in Python 2.5? (Was Re: pdb in python2.5)

"Rotem" <[EMAIL PROTECTED]> writes: > Hi, > > I noticed that pydb.pm() also fails in python2.5 when invoked on that > same example (seems like also trying to access a nonexistent > attribute/variable). > > Is this known to you as well/was it fixed? Doesn't do that for me for Python 2.5 on both

Possible bug in Python 2.5? (Was Re: pdb in python2.5)

, for now in pydb CVS, I've worked around this by checking. [EMAIL PROTECTED] (R. Bernstein) writes: > "Rotem" <[EMAIL PROTECTED]> writes: > > > Hi, > > > > Maybe I'm repeating a previous post (please correct me if I am). > > > >

Re: pdb in python2.5

"Rotem" <[EMAIL PROTECTED]> writes: > Hi, > > Maybe I'm repeating a previous post (please correct me if I am). > > I've tried the following code in python 2.5 (r25:51908, Oct 6 2006, > 15:22:41) > example: > > from __future__ import with_statement > import threading > > def f(): > l = thr

Re: Tracing the execution of scripts?

Fulvio <[EMAIL PROTECTED]> writes: > *** > Your mail has been scanned by InterScan MSS. > *** Delighted to know that. > > On Friday 27 October 2006 17:31, R. Bernstein wrote: > > pydb (http://bashdb.sf.net/pydb) has a both the ab

Re: Tracing the execution of scripts?

pydb (http://bashdb.sf.net/pydb) has a both the ability to trace lines as they are executed as well as an --output option to have this sent to a file rather than stdout. If your program has threads it would be good to use the --threading option. (The best threading support is if your program uses t

Re: Debugging

Fulvio <[EMAIL PROTECTED]> writes: > The previous post I might have missed some explaination on my proceeding. I'd > say that I'm testing a small program under pdb control > (python /usr/lib/python2.4/pdb.py ./myprog.py). So pdb will load myprog and > stop the first line code. > Once I'm at the

Re: Debugging

Fulvio <[EMAIL PROTECTED]> writes: > *** > Your mail has been scanned by InterScan MSS. > *** > > > Hello, > > I'm trying out a small utility and my method uses PDB for debugging. I tried > to read some information regarding the commands of PDB but are r

Set -Werror *inside* Python (Was Re: Can pdb be set to break on warnings?)

This seems like very useful information. In the documentation I've been maintaining for the extended python debugger (http://bashdb.sf.net/pydb) I've added this as a little footnote: http://bashdb.sourceforge.net/pydb/pydb/lib/pydb-invocation.html#foot1113 However since pydb allows for options on

Re: How to use pdb?

[EMAIL PROTECTED] writes: > R. Bernstein wrote: > > Perhaps what you are looking for is: > > python /usr/lib/python2.4/pdb.py Myprogram.py > > I tried this and it did not work. pdb did not load the file so it > could be debugged. lol. Yes, if you are not in the same d

Re: How to use pdb?

[EMAIL PROTECTED] writes: > I am trying to figure out how to use the pdb module to debug Python > programs, and I'm having difficulties. I am pretty familiar with GDB > which seems to be similar, If you are pretty familiar with gdb, try http://bashdb.sourceforge.net/pydb. It is a great deal mor

Re: automatic debugger?

[EMAIL PROTECTED] writes: > hi > is there something like an automatic debugger module available in > python? Say if i enable this auto debugger, it is able to run thru the > whole python program, print variable values at each point, or print > calls to functions..etc...just like the pdb module, bu

Re: continue out of a loop in pdb

Here's the revision I just made for pydb's documentation (in CVS). I welcome suggestions for improvement. set_trace([cmdfile=None]) Enter the debugger before the statement which follows (in execution) the set_trace() statement. This hard-codes a call to the debugger at a given point

Re: continue out of a loop in pdb

"Diez B. Roggisch" <[EMAIL PROTECTED]> writes: > > the code works with no problem, I am playing around with the pdb, i.e > > > > from pdb import * > > set_trace() for i in range(1,50): > > print i > > print "tired of this" > > print "I am out" > > > > [EMA

Re: continue out of a loop in pdb

Gary Wessle <[EMAIL PROTECTED]> writes: > Hi > > using the debugger, I happen to be on a line inside a loop, after > looping few times with "n" and wanting to get out of the loop to the > next line, I set a break point on a line after the loop structure and > hit c, that does not continue out of

Re: advice on this little script

"BartlebyScrivener" <[EMAIL PROTECTED]> writes: > There are several of these writing quotes, all good in their own way, And from Hamlet: brevity is the soul of wit. -- http://mail.python.org/mailman/listinfo/python-list

Re: debug CGI with complex forms

"Sullivan WxPyQtKinter" <[EMAIL PROTECTED]> writes: > When the form in one HTML is very complex with a lot of fields(input, > button,radio,checkbox etc.), setting the environment is quite > burdernsome, so I usually change the stdout and stderr of the submit > processing script to a file object to

Re: How to debug python code?

Dennis Lee Bieber <[EMAIL PROTECTED]> writes: > On 30 Mar 2006 21:18:50 -0800, [EMAIL PROTECTED] declaimed the > following in comp.lang.python: > > > hi, > >I am new to Python programming.I am not getting exactly pdb.Can > > anyone tell me effective way to debug python code? > > I

Re: How to debug python code?

[EMAIL PROTECTED] writes: > hi, >I am new to Python programming.I am not getting exactly pdb.Can > anyone tell me effective way to debug python code? >Please give me any example. >Looking for responce. >Thank You. > Sushant Well, I guess (in addition to the other

[ANN] pycdio 0.11

pycdio is an OO Python interface to libcdio. The libcdio package contains a library for CD-ROM and CD image access. Applications wishing to be oblivious of the OS- and device-dependent properties of a CD-ROM or of the specific details of various CD-image formats may benefit from using this library

ANN: Extended Python debugger 1.14

Download from http://sourceforge.net/project/showfiles.php?group_id=61395&package_id=175827 On-line documentation is at http://bashdb.sourceforge.net/pydb/pydb/lib/index.html Changes since 1.12 * Add MAN page (from Debian) * Bump revision to 0.12 to 1.13 to be compatible with Debian pydb package.

Re: using breakpoints in a normal interactive session

of the debugger and when it is left via "quit" the instance is destroyed. (In the case of pydb.set_trace() the issue never comes up because the program is terminated on exit.) [EMAIL PROTECTED] (R. Bernstein) writes: > Here's what I was able to do using the Extended

Re: using breakpoints in a normal interactive session

[EMAIL PROTECTED] writes: > Is there a way to temporarily halt execution of a script (without using > a debugger) and have it put you in an interactive session where you > have access to the locals? Here's what I was able to do using the Extended Python debugger. http://bashdb.sourceforge.net/p

ANN: Extended Python debugger 0.12

This third release of an improved debugger also probably about as great as the last release. Download from http://sourceforge.net/project/showfiles.php?group_id=61395&package_id=175827 On-line documentation is at http://bashdb.sourceforge.net/pydb/pydb/lib/index.html Along with this release is a

ANN: (slightly) extended Python debugger 0.11

The second public release of the extended Python debugger is now available from sourceforge: http://sourceforge.net/project/showfiles.php?group_id=61395&package_id=175827 For this release documentation has been added. That is also available online at: http://bashdb.sourceforge.net/pydb/pydb/lib/i

Re: How to handle two-level option processing with optparse

Magnus Lycka informs: > [in response to my comment]: > > I see how I missed this. Neither disable_.. or enable_.. have document > > strings. And neither seem to described in the optparser section (6.21) > > of the Python Library (http://docs.python.org/lib/module-optparse.html). > > http://docs.py

Re: How to handle two-level option processing with optparse

Steve Holden <[EMAIL PROTECTED]> writes: > Well you are just as capable ... Yes, I guess you are right. Done. Couldn't find how to suggest an addition to the Python Cookbook (other than some generic O'Reilly email), so I've put a submission to: http://aspn.activestate.com/ASPN/Cookbook/Python/ -

Re: How to handle two-level option processing with optparse

Giovanni Bajo suggests: > If you call OptionParser.disable_interspersed_args() on your parser, > it will stop parsing at the first positional argument, leaving other > options unparsed. Wow - that was a quick answer! Thanks - it works great! I see how I missed this. Neither disable_.. or enable_

How to handle two-level option processing with optparse

optparse is way cool, far superior and cleaner than other options processing libraries I've used. In the next release of the Python debugger revision, I'd like to add debugger options: --help and POSIX-shell style line trace (similar to "set -x") being two of the obvious ones. So I'm wondering ho

[ANN] pycdio 0.10 - Python to CD reading and control (via libcdio)

pycdio is a Python interface to the CD Input and Control library (libcdio). You can get the source at the same place as libcdio: ftp://ftp.gnu.org:/pub/gnu/libcdio/pycdio-0.10.tar.gz The pycdio and libcdio libraries encapsulate CD-ROM reading and control. Python programs wishing to be oblivious

Re: Getting better traceback info on exec and execfile - introspection?

Fernando Perez <[EMAIL PROTECTED]> writes: > So any regexp-matching based approach here is likely to be fairly brittle, > unless you restrict your tool to the standard python interpreter, and you > get some guarantee that it will always tag interactive code with > ''. Meant to mention for what it'

Re: Getting better traceback info on exec and execfile - introspection?

Fernando Perez <[EMAIL PROTECTED]> writes: > I thought a little about this. One possibility ... Thanks. A sibling thread has the code I'm currently using. > Oh, that's because you're using %run, so your code is in complete control. > What I meant about a restriction ... Okay. > If you are int

Re: Getting better traceback info on exec and execfile - introspection?

"Ziga Seilnacht" <[EMAIL PROTECTED]> writes: > You should check the getFrameInfo function in zope.interface package: > http://svn.zope.org/Zope3/trunk/src/zope/interface/advice.py?rev=25177&view=markup Thanks! Just looked at that. The logic in the relevant part (if I've extracted this correctly):

Re: Getting better traceback info on exec and execfile - introspection?

Fernando Perez <[EMAIL PROTECTED]> writes: > R. Bernstein wrote: ... > > However the frame information for exec or execfile looks like this: > > File "", line 1, in ? > > That comes from how the code object was compiled: ... > So any regexp-matching ba

Re: Getting better traceback info on exec and execfile - introspection?

I suggested: > And suppose instead of '' I'd like to give the value or the > leading prefix of the value instead of the unhelpful word ''? > How would one do that? Again, one way is to go into the outer frame > get the source line (if that exists), parse that and interpolate > argument to exec(file

Getting better traceback info on exec and execfile - introspection?

In doing the extension to the python debugger which I have here: http://sourceforge.net/project/showfiles.php?group_id=61395&package_id=175827 I came across one little thing that it would be nice to get done better. I notice on stack traces and tracebacks, an exec or execfile command appears as

setup.py vs autoconf install/uninstall,

In making a release of the recent changes to pdb.py announce here: http://groups.google.com/group/comp.lang.python/browse_thread/thread/b4cb720ed359a733/fbd9f8fef9693e58#fbd9f8fef9693e58 I tried using setup.py. I think it's great that setup.py tries to obviate the need for "Make" by just doing ev

Re: pdb.py - why is this debugger different from all other debuggers?

Tino Lange <[EMAIL PROTECTED]> writes: > R. Bernstein wrote: > To summarize, I think most of us readers here like your changes or at least > didn't shout loud enough against it ;-) Okay. I'll gladly accept whatever positive interpretation someone wants to offer. :-)

ANN: (slightly) extended Python debugger

I've put out the first release of an expanded version of the Python debugger. For now it is under the bashdb project on sourceforge: http://sourceforge.net/project/showfiles.php?group_id=61395 I've tried this only on 3 machines and each had a different version of Python: OSX using python versio

Re: pdb.py - why is this debugger different from all other debuggers?

Mike Meyer <[EMAIL PROTECTED]> writes: > But if I had to choose between being > able to play with objects interactively or being able to step through > code, I'll take the interactive interpreter every time. Why would you have to choose? You've created a straw-man argument. No one has previously

Re: pdb.py - why is this debugger different from all other debuggers?

Mike Meyer <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] writes: > Actually, you're not talking about changing the paradigm. You're > talking about minor tweaks to the command set. I am sorry if this was a bit of an exaggeration. Whatever. > I don't use pdb a lot either - and I write a *lot* o

Re: pdb.py - why is this debugger different from all other debuggers?

[EMAIL PROTECTED] writes: > I was disappointed not to see any replies to this. > I use pdb a lot because most of my debugging needs > are simple, and I don't need/want the overhead or > complications of a heavy duty gui debugger. > > I used ddd only little many many years ago, but > compatibility

Re: pdb.py - why is this debugger different from all other debuggers?

Fernando Perez <[EMAIL PROTECTED]> suggests: > You may want to try out ipython (the current release candidate from > http://ipython.scipy.org/dist/testing/, which has many improvements on this > front). The %pdb magic will trigger automatic activation of pdb at any > uncaught exception, and '%run

pdb.py - why is this debugger different from all other debuggers?

Okay, a bit of an exaggeration. Recently, I've been using Python more seriously, and in using the debugger I think one of the first things I noticed was that there is no "restart" ("R" in perldb) or "run" (gdb) command. I was pleasantly pleased discover how easy though it was patch pdb.py and pd