Log file Viewer

[14:26:40] <estan> hi folks. i'm trying to use pip install -f https://my.domain.com/wheels/h5py-2.9.0-cp36-cp36m-linux_x86_64.whl h5py==2.9.0 in order to use a custom-built h5py wheel, but it's still picking the manylinux1 wheel from PyPI. -v shows that it is finding the link correctly, but it's just not using it.

[14:27:41] <estan> i know there is --no-index, but i don't want to disable index lookup completely (i'm using pip-tools, just debugging right now with manual pip install calls).

[14:27:57] <estan> is there some way to make it prefer the wheel i have using -f ?

[14:28:02] <estan> *i gave.

[14:32:24] <moldy> estan: just install directly from the URL?

[14:34:02] <moldy> estan: alternatively, give your custom a wheel a custom version and specify that?

[14:39:31] <estan> yea i think i'm going to have to go with the latter.

[14:39:49] <estan> (i found https://github.com/pypa/pip/issues/3844 now, which is about the priority of manylinux vs generic linux).

[14:40:53] <estan> i think i have to go with the latter, because we're using pip-tools, and it unfortunately has a limitation that you can't just give a wheel URL in its input requirements.in and have it preserved into the generated requirements.txt.

[14:42:18] <estan> hm. we built the wheel with `pip wheel ...`, is there some simple flag to modify the version of the resulting wheel?

[14:42:36] <estan> would be a bit awkward if we'd have to keep our own source package as well :/

[14:49:07] <estan> ah looks like the bdist_wheel command has a --build-number, i'll have a go at that.

[15:11:51] <estan> hmf. seems pip does not consider build numbers, so can't use that to distinguish it.

[15:12:01] <moldy> estan: that limitation is a huge part of why i abandoned pip-tools years ago. too bad they did not fix that yet :-/

[21:35:35] <estan> moldy: yea, it also has a bit of other annoying limitations.