Re: [Bitpim-devel] bitpim (CVS) and wxPython 2.5.x (CVS) do not get along...

[Roger B. <ro...@ro...>]

I have committed fixes for both the issues you are seeing.
The coredump was because I didn't supply an initial value
for the combobox.  On Windows and Linux it then defaults
to the empty string.  On Mac it defaults to a coredump :-)

The other pubsub stuff was because I changed the format of
the categories from a dictionary to a list, but missed it
in one place.

BTW debuggers are for wimps :-)  I actually just use
print statements etc.  I do use them on C/C++ code however.

Linus' opinions are interesting:

http://lwn.net/2000/0914/a/lt-debugger.php3

I would agree with him in the context of the kernel.  In
BitPim I do want development to be really easy, and Python
is definitely a different programming style.  Prior to 0.7
the stack traces only gave line numbers.  I could usually
figure out exactly what the problem was as a result.

0.7 now also has the groovy feature of including local
variables in each frame which goes a long way to almost
making this trivial :-)  They work fine for issues in
the Python code, but not for C code issues such as coredumps
like you had.

Thanks for nailing down the issue.

Roger