[CentralOH] wxPython / Py2Exe && CxFreeze && PyInstaller && IronPython

[James -- Atlantix]

Mark;

 

Sorry to hear about the issues with Windows 7. I am not surprised. I have
been having similar problems with PyQt/PySide conversions to .exe on Windows
7 and Vista.

 

We have developed several commercial grade applications with PySide here at
Atlantix, and getting them into .exe has been more than difficult.


We have adopted two strategies:

 

1)      CxFreeze, Py2Exe, and Pyinstaller -> Simply do not work consistently

2)      We believe in PySide as the defacto GUI tool for Python (and use
WxPython from time to time), however IronPython can be used to create custom
.dll's or .exe's for sections of the code, and then called from your main
application. In this case, it would be WxPython. 

3)      The major weakness of GUI apps with python is clear, and I mean
clear, readable documentation about compiling GUI code into .exe with
CxFreeze or Py2exe. Py2exe has so many dependencies now, particularly with
GUI tools and using any types of graphics, that it is ridiculous. Hence, we
made our own graphics toolkit for use in PySide and have bypassed
matplotlib. 

 

Sorry for your pain. Microsoft is contributing to this greatly with side by
side installations and just in time installers for Office, which will defeat
win32com. I spent 6 hours on the phone with Microsoft this past fall on this
issue. 

 

Summary statement: Rewrite some of your GUI with IronPython and link it to
your WxPython GUI, then distribute your app with .pyc files into
/Lib/site-packages. 

 

-James

 

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/mailman/private/centraloh/attachments/20110315/552650de/attachment.html>