test
On 1/4/2011 7:06 PM, Corey Richardson wrote:
On 01/04/2011 06:59 PM, Alan Gauld wrote:
"Alex Hall" wrote
expected at all. I tried the pdb module, but I am running a wx
program
so it is not helping. I tried:
python -m pdb c:\prog\solitaire\game.py
The key to using any debugger in a GUI
"Corey Richardson" wrote
And of course print statements work too within the console
window.
I've done almost all my debugging via print statements at crucial
points. It's a good way to go, IMO.
It's a good way to go for short simple programs.
The big disadvantage is that the larger the pr
> and I will figure out how to get more. I will definitely look at
> setting breakpoints in the event handlers (every event is fired by a
> keystroke controled in an accelerator table).
It doesn't matter about the events, only the handler.
Provided you know the handler function that gets cal
On 01/04/2011 06:59 PM, Alan Gauld wrote:
>
> "Alex Hall" wrote
>
>> expected at all. I tried the pdb module, but I am running a wx
>> program
>> so it is not helping. I tried:
>> python -m pdb c:\prog\solitaire\game.py
>
> The key to using any debugger in a GUI environment is to set break
> p
Thanks to both of you. While I am not getting as much information from
pdb as I get from an error traceback, I suspect that it is my fault
and I will figure out how to get more. I will definitely look at
setting breakpoints in the event handlers (every event is fired by a
keystroke controled in an
"Alex Hall" wrote
expected at all. I tried the pdb module, but I am running a wx
program
so it is not helping. I tried:
python -m pdb c:\prog\solitaire\game.py
The key to using any debugger in a GUI environment is to set break
points on the event handlers of interest. Then when the event fi
On Tue, Jan 4, 2011 at 5:26 PM, Alex Hall wrote:
> Hi all,
> I am coming along quite nicely with Solitaire (sans graphics).
> However, I am getting some odd behavior, and I would like to see what
> is calling what so I can see where things are going wrong. It is not
> causing an error to print a t
Hi all,
I am coming along quite nicely with Solitaire (sans graphics).
However, I am getting some odd behavior, and I would like to see what
is calling what so I can see where things are going wrong. It is not
causing an error to print a traceback, but it is not doing what I
expected at all. I trie
