[PyKDE] How To Publish a pyqt application

sole at esrf.fr sole at esrf.fr
Wed Mar 29 01:17:38 BST 2006

Quoting Hans-Peter Jansen <hpj at urpla.net>:
> Using a sane package manager with proper dependencies is the right and 
> the easiest way to go. 
> Or quick n'dirty:
> try:
>     from qt import *
> except:
>     popen2("kdialog --sorry 'PyQt (Qt bindings for Python) is required 
> for this script.'")
>     raise

Certainly the easiest way to go for the programmer, not for the end user :-)

Another advantage of a "frozen" binary is that does not force a different
python/Qt/PyQt installation to the one the end user has.

My frozen applications only ask the end user:

- to extract a tar file in linux (that will give even a script to position the
library path) or
- to run a .exe installer in windows.
- to extract a tar file in MacOSX (py2app used in this case)

Once the build system is properly setup, the time cost to the programmer is less
than 5 minutes per platform.

We had applications where we asked the end user to install python, numeric, Blt
and to compile the source files. The applications never got "popular". We
offered the same applications as a frozen versions and the users were very
enthusiastic about them. 

If anybody is interested on x-ray fluorescence analysis, I can give him/her a
couple of links to "frozen" applications that run in almost any linux flavour (I
have not found a distribution more recent than SuSE82 not supporting them). 



This mail sent through IMP: http://horde.org/imp/

More information about the PyQt mailing list