Re: ddd and python

Thank you and thanks for this excellent software.

A quick test shows vast improvement. I did 
install pydb and am using that with ddd.

This version even overcomes the problem of having 
space characters in the file path. Embedded 
spaces appeared to mess up ddd when I issued the 
"Edit" command. It then looked for source in 
meaningless places, having to do with where 
spaces " " occurred in the directory path. It now 
appears fixed on this OS X system.

Thanks again!

-Tony

>Just tried it on GNU/Linux with software listed below and it worked.
>
>There's been a bit of work on improving pydb, getting it more in line
>with the current python debugger pdb, and making it more like gdb.
>
>See http://bashdb.sourceforge.net/pydb for information. This should
>replace the pydb found in ddd which hasn't been maintained for about 6
>years.
>
>And in conjunction with the pydb improvements, there has been work in
>updating ddd to handle the new features.
>
>The changes are in the "pydb" branch of the ddd source tree, and a
>"test" release of ddd incorporates this which you can get at:
>
>   http://sourceforge.net/project/showfiles.php?group_id=61395
>
>But having said this, I should mention a couple of known problems. The
>last release of pydb (and current releases of pdb in Python and
>probably the pydb of ddd), have all had problems tracking the source.
>One problem, and I'm not sure I forget the details of the
>characterization, is when the Python program is run outside of the
>directory it resides in. And this situation also effects tracing
>through imports, especially "import x.y as z". The current pydb
>sources in CVS address this somewhat, and in the next release there
>will be a gdb "directories" command which will allow you to set a
>source lookup path.
>
>Another problem but only with the released ddd-3.12-test5 and pydb
>1.16 is the "cont"(inue) button is shown greyed out. The problem here
>is that I've removed "cont" as 3nd alternative for "continue": both
>"c" and "continue" work, and you can issue "c" or "continue" in the
>debugger command line area. I've just committed the fix to ddd for
>this. (Again, only in the pydb branch).
>
>
>Tony Mannucci writes:
>  > I've been using ddd with pydb for python and find
>  > it does not load the source or place breadkpoint
>  > symbols in the source. Neither is the source line
>  > indicated. Has anyone had success with this? I
>  > will try it on a LInux system when I get the
>  > chance. I am using OS X, Tiger (10.4).
>  >
>  > Other than that, it seems to work.
>  >
>  > ddd -version
>  > GNU DDD 3.3.11 (powerpc-apple-darwin8.6.0)
>  > Copyright (C) 1995-1999 Technische Universität Braunschweig, Germany.
>  > Copyright (C) 1999-2001 Universität Passau, Germany.
>  > Copyright (C) 2001 Universität des Saarlandes, Germany.
>  > Copyright (C) 2001-2004 Free Software Foundation, Inc.
>  >
>  > [Built from tar file]
>  >
>  > Thanks for a great effort.
>  >
>  > -Tony
>  >
>  > --
>  > Tony Mannucci
>  > Supervisor, Ionospheric and Atmospheric Remote Sensing Group
>  >   Mail-Stop 138-308,                     Tel > (818) 354-1699
>  >   Jet Propulsion Laboratory,              Fax > (818) 393-5115
>  >   California Institute of Technology, 
>Email > [email protected]
>  >   4800 Oak Grove Drive,                   http://genesis.jpl.nasa.gov
>  >   Pasadena, CA 91109
>  >
>  >
>  > _______________________________________________
>  > Ddd mailing list
>  > [email protected]
>  > http://lists.gnu.org/mailman/listinfo/ddd
>  >
>
>
>_______________________________________________
>Ddd mailing list
>[email protected]
>http://lists.gnu.org/mailman/listinfo/ddd


-- 
Tony Mannucci
Supervisor, Ionospheric and Atmospheric Remote Sensing Group
  Mail-Stop 138-308,                     Tel > (818) 354-1699
  Jet Propulsion Laboratory,              Fax > (818) 393-5115
  California Institute of Technology,     Email > [email protected]
  4800 Oak Grove Drive,                   http://genesis.jpl.nasa.gov
  Pasadena, CA 91109