WxPython versus Tkinter.

[rusi]

On Jan 24, 9:16 am, "Littlefield, Tyler" <ty... at tysdomain.com> wrote:
>  >PS: Be sure not to cause any segfaults because these linux folks can't
>  >debug for shite!
> Or maybe it is that the person fighting and throwing insults around like
> candy at a parade can't code for shite. Or *gasp* the library that is
> supposedly cross-platform has issues on certain platforms. You provided
> a challenge to show how superior wxPython was. If it segfaults, that
> tells me that: 1) you can't code worth "shite," or 2) the library you
> are drooling over sucks and shouldn't be cross-platform. Which is it? I
> highly doubt there is a third option, but please feel free to tell me,
> rather than insulting again.

I think there is a third option
About rr's code-ing ability... this thread is long enough  :-)
Likewise if a certain library not in python standard distribution does
not work properly its the problem of the library.
But if python crashes its not good for the image of python.

Personal note 1: I am often teaching python with code I am seeing for
the first time -- typically something the class presents me which we
understand/debug/refactor together.
Usually I am not afraid of python because errors are helpful and
gentle.
Segfaulting on the other hand is the last thing I want to see in such
a context :-)

Personal note 2: I dont regard myself as a gui programmer and Ive
often wondered which toolkit to demonstrate.  I probably wont be
looking at wx now unless someone gives a convincing argument that the
segfault did not happen "inside" wx.

Of course as Steven pointed out wx is written in C++ which is almost
certainly where the crash is occurring.
But this is technical nitpicking.
The real issue is that when coding in C/C++ segfaults are a daily
affair.
Whereas for python its the first time I am seeing it in 10 years...