[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyQt] PyQt Digest, Vol 115, Issue 32
From:       David Cortesi <davecortesi () gmail ! com>
Date:       2014-02-23 15:30:28
Message-ID: CALyzANv5Hz9gD3rhireVEso+csDChJo58z8sCQn4+Qh4eNVXWg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Phil said,

> The deployment tool with take a Python installation, your
> application, PyQt5 (much like tools like PyInstaller, py2exe etc) and
> create a qmake .pro file and the required C++ source code for creating a
> single application executable. The standard Qt tools will then handle
> all the complicated packaging and deployment issues - for all platforms.
> See...
> http://www.riverbankcomputing.com/hg/pyqtdeploy/

Wonderful news! Thank you! This will remove SO many
complications and uncertainties in packaging. And will greatly
increase the value and desirability of PyQt as a development tool.

[Attachment #5 (text/html)]

<div dir="ltr"><div>Phil said,<br><br>&gt; The deployment tool with take a Python \
installation, your<br> &gt; application, PyQt5 (much like tools like PyInstaller, \
py2exe etc) and<br> &gt; create a qmake .pro file and the required C++ source code \
for creating a<br> &gt; single application executable. The standard Qt tools will \
then handle<br> &gt; all the complicated packaging and deployment issues - for all \
platforms.<br> &gt; See...<br>
&gt; <a href="http://www.riverbankcomputing.com/hg/pyqtdeploy/" \
target="_blank">http://www.riverbankcomputing.com/hg/pyqtdeploy/</a><br><br></div><div>Wonderful \
news! Thank you! This will remove SO many<br></div><div>complications and \
uncertainties in packaging. And will greatly<br>

increase the value and desirability of PyQt as a development \
tool.<br><br></div></div>



_______________________________________________
PyQt mailing list    PyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt

[prev in list] [next in list] [prev in thread] [next in thread]