Log file Viewer

[15:18:29] <gabeio> is there a way to pin a url requirement using pip? I tried: https://s3.amazonaws.com/example-pip/forks/inotify-0.5.zip#egg=python_inotify==0.5 and it seems to work, but only when outside of the requirements file which seems _strange_. if this is the wrong channel to ask these questions let me know :)

[15:26:59] <tos9> gabeio: when you're specifying a direct path to a tarball, what does it mean to pin a requirement

[15:27:04] <tos9> the tarball is the one and only version there

[15:29:20] <nisstyre> Hi, I'm trying out the new pip resolver, and I have a question. I have a conflicting dependency where some package depends on an older version of protobuf (3.0.0a3), and that package itself is a dependency, but my requirements have protobuf==3.6.1. I don't actually care if the other package uses a newer protobuf, because I know it will work. Is there any way to tell pip to just ignore that one?

[15:29:52] <nisstyre> I guess the only other option is to fork it and update the dependency constraints, but I'd rather avoid that

[15:32:36] <gabeio> tos9: that's what I thought too but apparently when running pip install on the requirement it will reinstall it because it doesn't know the name/version of the requirement/tarball, it just knows you want "that" requirement installed so it will uninstall and reinstall, which is what I'm aiming to avoid.

[15:35:17] <dstufft> nisstyre: afaik there's currently no way to override that. I think there's a ticket about adding the ability to override the resolver and say "I don't care what the resolver says, I want to install X at version Y regardless"

[15:36:28] <nisstyre> dstufft: ok thanks

[19:06:23] <nisstyre> I couldn't find the issue related to this, if there is one. Shall I go ahead and make a feature request?