New in this Version
Breakpoint, trace() calls, and shell() calls are placed in the editor, and remembered across exits and restarts of PyDebug. Playpen checksum (actually an md5) is calculated at load time, and an notification is issued when the user is about to abandon playpen code that has been modified.
Breakpoints are essential when using a debugger. So far, I’ve encountered a blockage in getting IPython to stop at a breakpoint that is set on code that is executed due to a callback from a button press. So in the short term, I’ve developed a work-around. There is an easy way to insert a single line in the user’s program which executes the IPython debugger in the context of the insertion. (Inserted lines are stripped from the code when it is written from playpen to storage).
What’s missing in this Version?
The examples need a lot of development. I had hoped to have a simple gtk widget cookbook, sort of condensing the pygtk tutorial examples. I’d like to find some simple pygames to Sugarize. Do one as an example. Leave one to the learner.
The pleac branch on the help page need to go away. I’m not sure about “Dive into Python” as an intro.
It would be nice to configure pydoc so that the program in the playpen is featured at the top of the pydoc page. Work an example of how to use pydoc to learn essential information, solving real world programming version/interface incompatibility situation.