On Mar 10, 2:11 pm, Stefan Behnel <[EMAIL PROTECTED]> wrote: > Malcolm Greene wrote: > >> My personal experience with wxPython has its ups and downs. Specifically > >> when it comes to crashes, I wouldn't bet my life on it. > > > I'm new to Python and getting ready to build a small client based > > application intended to run on Windows and Linux. I was planning on using > > wxPython until I saw your comment above. > > Just to make this sound a bit less like FUD: my last experience with wxPython > dates back a couple of years (2004/5?), but back then, we used BoaConstructor > in a project, which crashed a bit too often to do real work with it - and with > crashing I mean crashing Python, not just showing us its blank traceback. So > this was definitely a problem either in wxWindows or in wxPython. > > I have no idea how well it works today, but this has definitely forged my > opinion on wxPython. > > > Any suggestions on an alternative Python client-side GUI library (pyQT ?) > > or tips on where I can find out more about wxPython/wxWidget problems? > > The only other GUI library I used was PyQT3. To me, it has proven to be very > stable, pretty easy to use and feature rich. And from what I read about it, > PyQT4 is supposed to be another lot better and has removed the few API quirks > I found at the time (AFAIR, it finally returns plain Python strings from the > API, for example). No, it still returns QStrings, so it doesn't break tons of code. I just always convert it to unicode if I'm going to keep the string around. > > Stefan
-- http://mail.python.org/mailman/listinfo/python-list
