[PyQt] Experimental PyQt5 v5.6 Wheels Available

Julien Duponchelle julien at gns3.net
Mon Apr 11 08:35:29 BST 2016


On Sat, Apr 9, 2016 at 6:55 PM Phil Thompson <phil at riverbankcomputing.com>
wrote:

> I've created wheels for SIP and PyQt5 v5.6 snapshots that are available
> from their respective download pages. They are for the following
> architectures:
>
> Linux 64-bits
> OS X 64-bits
> Windows 64-bits
> Windows 32-bits
>
> The PyQt5 wheels contain a minimal copy of Qt v5.6 - only those parts
> needed to support PyQt. They include pyuic5 but not (yet) pyrcc5 and
> pylupdate5. They do not contain QScintilla - there will be separate wheels
> for that.
>
> Please give feedback.
>
> I'm particularly interested in how well the Linux wheel works across
> different Linux distros. They were created on Ubuntu.
>
> The wheels have not been uploaded to PyPi because the PyQt wheels are too
> large, which is a shame. My original plan was to *not* bundle Qt. However
> that means that PyQt has to make assumptions about where Qt has been
> installed. The only reasonable assumption is the default location used by
> the Qt installers (ie. ~/Qt5.6.0 on Linux and OS X and C:\Qt\Qt5.6.0 on
> Windows). I thought that was going to be too restrictive.
>
> I'd like feedback on the best approach to this...
>
> 1. Stick with the current approach, unable to use PyPi, large download,
> simple install once downloaded, supports non-default Qt locations.
>
> 2. Don't bundle Qt, can use PyPi, small download, simple install, Qt must
> be installed in its default location.
>
> I could supplement 2) with a tool (provided as part of the wheel) that
> could be run (once) to "re-direct" the installed PyQt to the actual Qt
> installation.
>
> A further variation would be a separate tool that would modify the
> downloaded wheel to do the re-direct so that the modified wheel would be
> correct for your personal/company standards for the Qt location.
>
> Thoughts?
>
> Phil
>
> Hi,

I like the idea of having a wheel with Qt provided.

The benefits for me is when we maintain multiple version of the same
software we can easily use a different Qt version based on the
requirements.txt of each branch instead of the system wide Qt.

Julien
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20160411/061ba826/attachment.html>


More information about the PyQt mailing list