Closed hynek closed 2 years ago
Apparently same problem applies to Python 3.3:
[precise.build] run: dist/ddns-0-linux-x86_64/install.sh -p python3.3 /vrmd/ddns
[precise.build] out: Setting up virtualenv
[precise.build] out: Using base prefix '/usr'
[precise.build] out: New python executable in /vrmd/ddns/bin/python3.3
[precise.build] out: Also creating executable in /vrmd/ddns/bin/python
[precise.build] out: Installing setuptools, pip...done.
[precise.build] out: Installing ddns-0
[precise.build] out: Ignoring indexes: https://pypi/root/vrmd/+simple/
[precise.build] out: Collecting wheel
[precise.build] out: Collecting ddns
[precise.build] out: Collecting repoze.lru==0.6 (from ddns)
[precise.build] out: Could not find any downloads that satisfy the requirement repoze.lru==0.6 (from ddns)
[precise.build] out: No distributions at all found for repoze.lru==0.6 (from ddns)
[precise.build] out: Done.
[precise.build] out:
I tried cleaning the cache but it didn’t help.
I’ve dug into this and I think the problems are unrelated. PyPy simply does not work wit wheels that have compiled C code. Which sucks because many packages have optional C code but work without it just fine (e.g. Twisted, PyYAML, …).
As for the Python 3 problem, I could solve it for myself by creating the wheels using pip3 wheel instead of pip wheel (I’ve abandoned platter for a homegrown solution and run into the same problem).
One last update, they seem to be related after all and I just used the wrong pip for PyPy.
The solution to this whole bug is simple: use the correct pip to generate the wheels.
@hynek - could you elaborate? what did you do in order to use the correct pip?
I don’t really remember, I think I did it manually or something. I don't use platter anymore since pip grew most of the features I found useful.
Building the same package using CPython works, while PyP complains, that it can’t find its wheels:
PyPy
CPython
Everything is identical except for the -p argument to install.sh.