[01:51:04] <buck1> dstufft: i made this diagram https://gist.github.com/bukzor/0d0a171f70a375759039#file-find_requirement-png
[01:51:10] <buck1> the parts that can touch http are highlighted
[06:56:19] <Seraf> Hello everyone, I have a problem with my requirements.txt file : https://github.com/Seraf/LISA/blob/master/requirements.txt#L1. I'm actually installing mongoengine 0.8.7 because the 0.8.6 contains a fix I want. The problem is that django-tatypie-mongoengine has a mongoengine <=0.8.2 because of a little bug, even if it works with mongoengine 0.8.7. Until yesterday, it was working, and worked well on travis too, but tried yesterday to build it and now I have a co
[06:56:19] <Seraf> nflict. Any idea how to force my version and not resolve the django-tastypie-mongoengine ? Thanks
[07:05:34] <mgedmin> ask django-tatypie-mongoengine to release a version that supports the latest mongoengine?
[07:07:24] <Seraf> mgedmin, the problem is with mongoengine itself... regression in their code without test :(
[07:07:39] <Seraf> fix planned for a future release (who'll never come :p )
[07:08:48] <mgedmin> there's always the option to fork the packages, give them whatever backported fixes you want, assign your own local version numbers (0.8.7mg1 or something) and --find-links https://mycompany.com/packages/
[07:08:59] <Seraf> I saw git url is supported in requirements file. I just asked to tag a release without this dependancy
[07:09:13] <mgedmin> I don't recall if pip has an option to ignore version requirements, but even if it does it strikes me as a bad idea to do that globally
[07:09:48] <mgedmin> pointing to git is also an option
[07:32:25] <mgedmin> and besides, this is open source, so it would be nice to solve the problem for everyone: get the upstreams to have releases that play nice with each other
[07:32:54] <mgedmin> (in addition to deploying whatever workaround you need to make it work for you right now, of course ;)
[07:47:31] <Seraf> mgedmin, I'm an opensource lover, but I don't have time to invest in mongoengine project :( don't have too much time for my own project ...
[07:47:58] <Seraf> but I agree, fork isn't the definitive solution
[07:48:06] <mgedmin> Seraf, filing bugs is sufficient, imho, just let upstreams know there's a problem
[07:49:06] <Seraf> mgedmin, already done, ticket is planned for the next milestone, but don't have time to wait for it
[07:49:41] <Seraf> I just needed a workaround (and it worked :D)
[15:49:21] <bowlofeggs> hello! i'm interested in building a plugin for http://pulpproject.org that is pip compatible. i will likely have a few questions about the data structures and protocols as i go
[15:49:37] <bowlofeggs> is anybody in here knowledgeable about pip/pypi?
[15:49:56] <bowlofeggs> and in particular, about the data formats/APIs that pip expects to find on the remote end
[15:50:07] <bowlofeggs> if there's docs on that, i would be very happy ☺
[15:51:48] <dstufft> there isn't much in the way of documentation :|
[16:14:35] <buck11> dstufft: i've reformulated my problem as making a path that can avoid the blue bits https://gist.github.com/bukzor/0d0a171f70a375759039#file-find_requirement-png
[18:27:11] <buck11> HTTP error 404 while getting https://github.com/dstufft/freezegun/archive/fix-pytest.zip