<div dir="ltr">I started a amazon ubuntu 64 instance upgraded the python to 3.5 and got the same error:<br><br>pip install sip-4.18.dev1604081802-cp35-cp35m-linux_x86_64.whl <br>sip-4.18.dev1604081802-cp35-cp35m-linux_x86_64.whl is not a supported wheel on this platform.<br>Storing debug log for failure in /home/ubuntu/.pip/pip.log<br><br>------------------------------------------------------------<br>/usr/bin/pip run on Sat Apr 9 18:21:20 2016<br>sip-4.18.dev1604081802-cp35-cp35m-linux_x86_64.whl is not a supported wheel on this platform.<br>Exception information:<br>Traceback (most recent call last):<br> File "/usr/lib/python2.7/dist-packages/pip/basecommand.py", line 122, in main<br> status = self.run(options, args)<br> File "/usr/lib/python2.7/dist-packages/pip/commands/install.py", line 257, in run<br> InstallRequirement.from_line(name, None))<br> File "/usr/lib/python2.7/dist-packages/pip/req.py", line 168, in from_line<br> raise UnsupportedWheel("%s is not a supported wheel on this platform." % wheel.filename)<br>UnsupportedWheel: sip-4.18.dev1604081802-cp35-cp35m-linux_x86_64.whl is not a supported wheel on this platform.<br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Apr 9, 2016 at 10:54 AM, Detlev Offenbach <span dir="ltr"><<a href="mailto:detlev@die-offenbachs.de" target="_blank">detlev@die-offenbachs.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div style="font-family:'Noto Sans';font-size:9pt;font-weight:400;font-style:normal">
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">Hi,</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">I tried to install the Linux wheel on openSUSE Leap 42.1 but got this output.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'monospace';color:#000000;background-color:#ffffff">pip install PyQt5-5.6.dev1604091249-cp35-cp35m-li</span><span style="font-family:'monospace'"><br>nux_x86_64.whl <br></span><span style="font-family:'monospace';color:#b21818;background-color:#ffffff">PyQt5-5.6.dev1604091249-cp35-cp35m-linux_x86_64.whl is not a supported wheel on this platform.</span><span style="font-family:'monospace'"><br></span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'noto sans'">It seems the wheel is built for Python 3.5 but openSuse seems to be at Python 3.4. Providing wheels could mean to support multiple Python versions. Here is a short summary of the various Python versions of my (virtual) Linux machines.</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'noto sans'">openSUSE 42.1: Python 3.4</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'noto sans'">Ubuntu 15.10: Python 3.4</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'noto sans'">Mint 17.3: Python 3.4</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'noto sans'">Fedora 23: Python 3.4</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-family:'noto sans'">What was the reason to create Linux wheels for Python 3.5?</span></p><span class="">
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">On Saturday 09 April 2016, 17:49:53 Phil Thompson wrote:</p>
</span><div><div class="h5"><p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> I've created wheels for SIP and PyQt5 v5.6 snapshots that are available from</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> their respective download pages. They are for the following architectures:</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> Linux 64-bits</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> OS X 64-bits</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> Windows 64-bits</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> Windows 32-bits</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> The PyQt5 wheels contain a minimal copy of Qt v5.6 - only those parts needed</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> to support PyQt. They include pyuic5 but not (yet) pyrcc5 and pylupdate5.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> They do not contain QScintilla - there will be separate wheels for that.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> Please give feedback.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> I'm particularly interested in how well the Linux wheel works across</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> different Linux distros. They were created on Ubuntu.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> The wheels have not been uploaded to PyPi because the PyQt wheels are too</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> large, which is a shame. My original plan was to *not* bundle Qt. However</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> that means that PyQt has to make assumptions about where Qt has been</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> installed. The only reasonable assumption is the default location used by</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> the Qt installers (ie. ~/Qt5.6.0 on Linux and OS X and C:\Qt\Qt5.6.0 on</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> Windows). I thought that was going to be too restrictive.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> I'd like feedback on the best approach to this...</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> 1. Stick with the current approach, unable to use PyPi, large download,</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> simple install once downloaded, supports non-default Qt locations.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> 2. Don't bundle Qt, can use PyPi, small download, simple install, Qt must be</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> installed in its default location.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> I could supplement 2) with a tool (provided as part of the wheel) that could</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> be run (once) to "re-direct" the installed PyQt to the actual Qt</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> installation.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> A further variation would be a separate tool that would modify the</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> downloaded wheel to do the re-direct so that the modified wheel would be</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> correct for your personal/company standards for the Qt location.</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> Thoughts?</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> </p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> Phil</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> _______________________________________________</p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> PyQt mailing list <a href="mailto:PyQt@riverbankcomputing.com" target="_blank">PyQt@riverbankcomputing.com</a></p>
</div></div><p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px">> <a href="https://www.riverbankcomputing.com/mailman/listinfo/pyqt" target="_blank">https://www.riverbankcomputing.com/mailman/listinfo/pyqt</a><br>-- </p>
<p style="margin-top:12px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><span style="font-size:0.92em;font-weight:600">Detlev Offenbach</span></p>
<p style="margin-top:0px;margin-bottom:0px;margin-left:0px;margin-right:0px;text-indent:0px"><a href="mailto:detlev@die-offenbachs.de" target="_blank">detlev@die-offenbachs.de</a></p></div><br>_______________________________________________<br>
PyQt mailing list <a href="mailto:PyQt@riverbankcomputing.com">PyQt@riverbankcomputing.com</a><br>
<a href="https://www.riverbankcomputing.com/mailman/listinfo/pyqt" rel="noreferrer" target="_blank">https://www.riverbankcomputing.com/mailman/listinfo/pyqt</a><br></blockquote></div><br></div>