On Wed, Sep 14, 2011 at 10:28 AM, Kent Tenney <[email protected]> wrote:
> Check out pudb > http://asmeurersympy.wordpress.com/2010/06/04/pudb-a-better-python-debugger/ Thanks for this reminder. However, I doubt this will work. The "platinum" solution, imo, is to be able to run a pdb-like debugger from *within* Blender. YMMV, but for me pdb is more than good enough when traces fail to do the job. To run pdb successfully, it must interact with the *Blender* console. It's unlikely this can be done from outside blender: we probably don't have any way of creating a proper bride. Of course I could be wrong, but modifying blender/2.59/python/lib/pdb seems like the most straightforward approach. I'm working on it now... Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
