Hello, Ok, so until I find a better solution I've tried hosting a wheel on a personal server, but then I get the following error when installing it: $ pyvenv-3.4 t $ source t/bin/activate (t) $ pip install https://ssl.pitrou.net/llvmlite-0.1-py2.py3-none-linux_x86_64.whl llvmlite-0.1-py2.py3-none-linux_x86_64.whl is not a supported wheel on this platform. Storing debug log for failure in /home/antoine/.pip/pip.log Yet: (t) $ python Python 3.4.1 (3.4:d1bf37def4fd, May 19 2014, 19:52:53) [GCC 4.8.1] on linux Type "help", "copyright", "credits" or "license" for more information.
import sysconfig sysconfig.get_platform() 'linux-x86_64'
The log file doesn't tell anything really interesting: ------------------------------------------------------------ /home/antoine/t/t/bin/pip run on Tue Oct 28 15:18:06 2014 llvmlite-0.1-py2.py3-none-linux_x86_64.whl is not a supported wheel on this platform. Exception information: Traceback (most recent call last): File "/home/antoine/t/t/lib/python3.4/site-packages/pip/basecommand.py", line 122, in main status = self.run(options, args) File "/home/antoine/t/t/lib/python3.4/site-packages/pip/commands/install.py", line 257, in run InstallRequirement.from_line(name, None)) File "/home/antoine/t/t/lib/python3.4/site-packages/pip/req.py", line 167, in from_line raise UnsupportedWheel("%s is not a supported wheel on this platform." % wheel.filename) pip.exceptions.UnsupportedWheel: llvmlite-0.1-py2.py3-none-linux_x86_64.whl is not a supported wheel on this platform. Regards Antoine.
Can you see what the following says (results here are from my Windows Python 3.4 system)?
from wheel.pep425tags import get_supported ['-'.join(t) for t in get_supported()] ['cp34-none-win_amd64', 'cp34-none-any', 'cp3-none-any', 'cp33-none-any', 'cp32-none-any', 'cp31-none-any', 'cp30-none-any', 'py34-none-any', 'py3-none-any', 'py33-none-any', 'py32-none-any', 'py31-none-any', 'py30-none-any']
I suspect you might be missing the combination "py2" with an architecture other than "any". Paul On 28 October 2014 14:22, Antoine Pitrou <solipsis@pitrou.net> wrote:
Hello,
Ok, so until I find a better solution I've tried hosting a wheel on a personal server, but then I get the following error when installing it:
$ pyvenv-3.4 t $ source t/bin/activate (t) $ pip install https://ssl.pitrou.net/llvmlite-0.1-py2.py3-none-linux_x86_64.whl llvmlite-0.1-py2.py3-none-linux_x86_64.whl is not a supported wheel on this platform. Storing debug log for failure in /home/antoine/.pip/pip.log
Yet:
(t) $ python Python 3.4.1 (3.4:d1bf37def4fd, May 19 2014, 19:52:53) [GCC 4.8.1] on linux Type "help", "copyright", "credits" or "license" for more information.
import sysconfig sysconfig.get_platform() 'linux-x86_64'
The log file doesn't tell anything really interesting:
------------------------------------------------------------ /home/antoine/t/t/bin/pip run on Tue Oct 28 15:18:06 2014 llvmlite-0.1-py2.py3-none-linux_x86_64.whl is not a supported wheel on this platform. Exception information: Traceback (most recent call last): File "/home/antoine/t/t/lib/python3.4/site-packages/pip/basecommand.py", line 122, in main status = self.run(options, args) File "/home/antoine/t/t/lib/python3.4/site-packages/pip/commands/install.py", line 257, in run InstallRequirement.from_line(name, None)) File "/home/antoine/t/t/lib/python3.4/site-packages/pip/req.py", line 167, in from_line raise UnsupportedWheel("%s is not a supported wheel on this platform." % wheel.filename) pip.exceptions.UnsupportedWheel: llvmlite-0.1-py2.py3-none-linux_x86_64.whl is not a supported wheel on this platform.
Regards
Antoine.
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
On Tue, 28 Oct 2014 14:44:22 +0000 Paul Moore <p.f.moore@gmail.com> wrote:
Can you see what the following says (results here are from my Windows Python 3.4 system)?
from wheel.pep425tags import get_supported ['-'.join(t) for t in get_supported()] ['cp34-none-win_amd64', 'cp34-none-any', 'cp3-none-any', 'cp33-none-any', 'cp32-none-any', 'cp31-none-any', 'cp30-none-any', 'py34-none-any', 'py3-none-any', 'py33-none-any', 'py32-none-any', 'py31-none-any', 'py30-none-any']
I suspect you might be missing the combination "py2" with an architecture other than "any".
Does matching really happen that way? Here it is anyway. There's no "py2" at all:
['-'.join(t) for t in get_supported()] ['cp34-cp34m-linux_x86_64', 'cp34-abi3-linux_x86_64', 'cp34-none-linux_x86_64', 'cp34-none-any', 'cp3-none-any', 'cp33-none-any', 'cp32-none-any', 'cp31-none-any', 'cp30-none-any', 'py34-none-any', 'py3-none-any', 'py33-none-any', 'py32-none-any', 'py31-none-any', 'py30-none-any']
Regards Antoine.
On 28 October 2014 14:51, Antoine Pitrou <solipsis@pitrou.net> wrote:
Does matching really happen that way?
Unfortunately yes :-( get_supported() introspects the system you're installing on and builds a list of tag combinations it's willing to accept. In doing so it misses some that I'd consider obscure but reasonable (notably here, independent of Python implementation (py rather than cp) but architecture specific). I consider this a flawed design, but it's always been like this. You'll need to raise a bug report for this. Actually two, as the pep425tags code is in both pip and wheel independently (the one you actually *want* is the pip one, though). I know - this should really be fixed. I'd like to see pep425tags in a separate project, referenced (or vendored if necessary) from both pip and wheel. And I'd like a matching algorithm for checking tags rather than generating a list of valid values. Oh, and a pony :-)
Here it is anyway. There's no "py2" at all:
Sorry, from any given Python you'll get either py2 or py3 depending on the major version of your Python. Paul
On Tue, 28 Oct 2014 15:03:23 +0000 Paul Moore <p.f.moore@gmail.com> wrote:
On 28 October 2014 14:51, Antoine Pitrou <solipsis@pitrou.net> wrote:
Does matching really happen that way?
Unfortunately yes :-(
get_supported() introspects the system you're installing on and builds a list of tag combinations it's willing to accept. In doing so it misses some that I'd consider obscure but reasonable (notably here, independent of Python implementation (py rather than cp) but architecture specific). I consider this a flawed design, but it's always been like this.
You'll need to raise a bug report for this. Actually two, as the pep425tags code is in both pip and wheel independently (the one you actually *want* is the pip one, though).
Apparently already reported to pip :-) https://github.com/pypa/pip/issues/1870 Reported to wheel at https://bitbucket.org/pypa/wheel/issue/125/get_supported-should-return-more Thanks for the explanations. Regards Antoine.
On 28 October 2014 15:15, Antoine Pitrou <solipsis@pitrou.net> wrote:
Apparently already reported to pip :-) https://github.com/pypa/pip/issues/1870
I *knew* I'd seen it somewhere. Thanks for locating it.
Reported to wheel at https://bitbucket.org/pypa/wheel/issue/125/get_supported-should-return-more
And thanks again. Paul
participants (2)
-
Antoine Pitrou -
Paul Moore