wxPython woes

[km]

Hi all,

I feel its a real pain to install wxPython from sources it goes back to install gtk+ etc . may be thats why its not yet become defacto GUI standard for python.
but i'd like to know if anyone has made it easy with an installer for wxPython on linux (Debian woody)?

regards,
KM

ps: i have tried installing wxPython with the .deb files availble in testing and unstable section. it doesnt work - unable to load the module

 

[simo]

I feel its a real pain to install wxPython from sources it goes back to install
gtk+ etc . may be thats why its not yet become defacto GUI standard for python.
but i'd like to know if anyone has made it easy with an installer for wxPython
on linux (Debian woody)?

ps: i have tried installing wxPython with the .deb files availble in testing
and unstable section. it doesnt work - unable to load the module

I seem to recall installing wxPython 2.4.24 on a friends LindowsOS box
(a Debian-based abomination) and simply used something like "apt-get
install wxgtk-2.4" and it went ahead quite easily, even installing
Python 2.3.3 as one of the dependencies, I was very impressed, it was
almost as easy as Windows!

I do agree that getting wxPython installed is too much of a nightmare,
mainly due to having to install wxWidgets and GTK+, but PyQt was
probably more hassle.....

Once you have 2.4 installed, 2.5 seemed easier to install (you already
have GTK+ etc. sorted). The pre-packaged RPMs etc. just don't seem to
work, you really have to compile from source.

 

[Sridhar R]

Hi all,

I feel its a real pain to install wxPython from sources it goes back to install gtk+ etc . may be thats why its not yet become defacto GUI standard for python.
but i'd like to know if anyone has made it easy with an installer for wxPython on linux (Debian woody)?

Well, if your app. is target mainly to the UNIX platform, then you may
want to try PyGTK - http://www.pygtk.org (basically wxPython is just
another layer over GTK). GTK port is available for win and mac also
(look at gimp for eg.) - also see http://gtk-wimp.sf.net.

still, wxPython is better for apps to be run on win,mac and unix, but
gtk+ is catching very close.

 

[David Fraser]

Well, if your app. is target mainly to the UNIX platform, then you may
want to try PyGTK - http://www.pygtk.org (basically wxPython is just
another layer over GTK). GTK port is available for win and mac also
(look at gimp for eg.) - also see http://gtk-wimp.sf.net.

still, wxPython is better for apps to be run on win,mac and unix, but
gtk+ is catching very close.

The important difference is that wxWindows and wxPython are designed to
use real native widgets as much as possible, whereas gtk-wimp is
basically trying to use theming to make GTK widgets look like Windows
widgets.

David

 

[Reinhold Birkenfeld]

The important difference is that wxWindows and wxPython are designed to
use real native widgets as much as possible, whereas gtk-wimp is
basically trying to use theming to make GTK widgets look like Windows
widgets.

The difference is the number of layers on the different platforms:

Under Un*x:
wxPython --> wxWidgets --> GTK --> Xlib
-- or --
PyGTK --> GTK --> Xlib
-- or --
PyQt --> Qt --> Xlib

Under Windows:
wxPython --> wxWidgets --> Native Windows Controls
-- or --
PyGTK --> GTK --> Wimp --> Native Windows Controls

Reinhold

 

[David Fraser]

The difference is the number of layers on the different platforms:

Under Un*x:
wxPython --> wxWidgets --> GTK --> Xlib
-- or --
PyGTK --> GTK --> Xlib
-- or --
PyQt --> Qt --> Xlib

Under Windows:
wxPython --> wxWidgets --> Native Windows Controls
-- or --
PyGTK --> GTK --> Wimp --> Native Windows Controls

Reinhold

This isn't really what it says on the gtk-wimp page. Is it true?
#
# When running on XP, the Windows theming API is used so that GTK
widgets look like native widgets.
That's a different story to them actually being native widgets.

David

 

[Reinhold Birkenfeld]

This isn't really what it says on the gtk-wimp page. Is it true?
#
# When running on XP, the Windows theming API is used so that GTK
widgets look like native widgets.
That's a different story to them actually being native widgets.

That's right, I didn't remember the behavior correctly. So the figure
should be PyGTK --> GTK --> Wimp --> Windows Drawing API...

Reinhold

 

[Reinhold Birkenfeld]

Hi all,

So does it mean that access will be much faster when PyGTK or PyQT are used instead of wxPython as one can see one layer additionallyunder *nix?

Theoretically PyGTK is faster, yes. However, "much faster" is probably
carrying things too far. On modern machines, there should be no difference.

Reinhold

 

[km]

Hi all,

So does it mean that access will be much faster when PyGTK or PyQT are used instead of wxPython as one can see one layer additionallyunder *nix?

regards,
KM
------------------------------------------------------------------------------

The difference is the number of layers on the different platforms:

Under Un*x:
wxPython --> wxWidgets --> GTK --> Xlib
-- or --
PyGTK --> GTK --> Xlib
-- or --
PyQt --> Qt --> Xlib

Under Windows:
wxPython --> wxWidgets --> Native Windows Controls
-- or --
PyGTK --> GTK --> Wimp --> Native Windows Controls

Reinhold

--
Wenn eine Linuxdistribution so wenig brauchbare Software wie Windows
mitbrächte, wäre das bedauerlich. Was bei Windows der Umfang eines
"kompletten Betriebssystems" ist, nennt man bei Linux eine Rescuedisk.
-- David Kastrup in de.comp.os.unix.linux.misc

--