Re:Python, Machine Learning, and Language Wars (2015)
by takeda on Tuesday March 22, 2016 @03:43PM
(#11339401)
Wheel is a binary distribution, so files would already be compiled and therefore python-dev would not be needed anymore.
Re:Python, Machine Learning, and Language Wars (2015)
by yeukhon on Tuesday March 22, 2016 @03:45PM
(#11339421)
Is wheel not default? Or play it elementary :-) how would I avoid this issue in the future?
Re:Python, Machine Learning, and Language Wars (2015)
by takeda on Tuesday March 22, 2016 @07:34PM
(#11340833)
I did not write anything worthy to send to PIP so don't know exactly but looks like it is up to the developers[1]
Anyway I just noticed that PyPI only supports binary packages for Windows and Mac OS X. Although, you could still generate wheels of packages that you use by using something like this:
pip wheel -r requirements.txt
You can then install them with pip install <file> or (unfortunately I forgot the option, perhaps it was -i) you can use an option to point to a directory containing wheels and pip install to install the main package. It should use all dependencies in that directory as well.
Re:Python, Machine Learning, and Language Wars (2015)
by techdragon on Wednesday March 23, 2016 @05:05AM
(#11342990)
the issue with Wheels on Linux, and this is very much a Linux problem, is that the 'pre built' nature of libraries in wheels doesnt play nice with the raw chaos of Linux's package management + distro + kernel ecosystem. I raised the question of FreeBSD and Solaris based wheels at a PyCon when I was in a face to face discussion with someone more knowledgeable, and the answer was 'in theory that should work like Windows & OSX, no one has done the hard work yet.'
So yeah Linux is not the most friendly environment for Python Wheels.
For example, you can't get through PyYaml unless python-dev is installed on Ubuntu. I am not sure if wheel would fix it but I don't think so.