[04:03:15] <agronholm> I found another bug -- pip install -U won't upgrade the package despite the fact that it correctly parses the wheel's version string but then it pretends it never saw it
[04:03:24] <agronholm> but I'm too tired to report it now
[04:05:16] <agronholm> the same happens with installation
[07:41:54] <skepster> Hi, I want to use pip + wheel together with a local folder of wheels on a server that runs lots of virtualenv backed python installs, my goal is to build a large enough wheel cache that I don't need to compile/download anything until a new package is released. Is there any way to make pip install to copy the installed wheels to a folder for every install?
[13:29:02] <skepster> Hi, I want to enable the --pre for all my pip commands, what should I put in pip.conf [install] to do that?
[13:49:54] <agronholm> skepster: I'm in a similar situation
[13:50:05] <agronholm> though I'm looking to deploy using salt
[15:39:39] <jness> hello, I have a question regarding using pip wheel with remote vcs: http://fpaste.org/103839/40068666/
[15:40:01] <jness> anyone familar with pip wheel that maybe able to point me in the correct direction?
[17:12:49] <pf_moore> jness: I don't think you can do that - requirements files have to be files in the local filesystem
[17:14:15] <pf_moore> jness: I can imagine a PR for getting a requirements file from a URL and then using github's url access to raw files, but that still wouldn't be the requirement file from the actual checkout you're installing (which might matter if you're specifying the revision)
[17:15:12] <dstufft> you can use an url for a requireents file