[16:01:41] <davidovich> hi, can someone have a look at https://github.com/pypa/pip/pull/1834 ?
[16:05:36] <davidovich> jaraco: did you have time to look at my updated change for binary scripts ? (https://bitbucket.org/pypa/setuptools/pull-request/60/fix-regression-in-issue-218)
[16:08:32] <Ivo> davidovich: pf_moore is our resident windows developer :)
[16:08:56] <Ivo> currently we need to get the failing build fixed, unfortunately not totally trivial
[16:09:18] <dingus9> hey quick question: trying to add a local git repo to my requirments.txt... getting "Could not find any downloads" when only when including my library from another requirements.txt in a project that depends on the former
[16:10:48] <jaraco> davidovich, I have not had time, but I hope to look at things this weekend.
[16:10:55] <jaraco> Ivo, I'm also a Windows developer.
[16:11:10] <Ivo> davidovich: one tests relies on pypi.appspot.com which no longer works after pypi mirror support ended, not sure who runs it either :/
[16:11:17] <Ivo> jaraco: you hardly have time to work on setuptools! :P
[16:11:35] <Ivo> I suppose I shold say resident pip developer instead
[16:12:13] <dingus9> ^^ So a -> requirements.txt requires git+ssh://...libB -> libB requirements.txt requires git+ssh://...libc.git
[16:12:18] <jaraco> Ivo, fair enough. I thought you were responding to the setuptools inquiry w.r.t. windows.
[16:13:04] <dingus9> anyone seen where the cascading deps fail like this?
[16:13:49] <Ivo> jaraco: ah sorry I was replying to request on the pip pull... you're welcome to comment if the unc path handling looks correct / runs correctly!
[16:13:50] <dingus9> I'm down to adding the libC directly to app a
[16:15:06] <Ivo> dingus9: requirements.txt does not get looked at all when installing a project from setup.py
[16:16:01] <Ivo> hopefully I'm interpreting the nature of your predicament correctly
[16:16:02] <dingus9> Ivo: doing pip install -r requirements.txt for app A... does that not cascade through deps
[16:16:56] <dingus9> Ivo: also in setup.py from pip.req import parse_requirements
[16:17:07] <Ivo> dingus9: the requirements.txt uses a -r ../../blah/project_b_requirements.txt ?
[16:24:40] <dstufft> Ivo: why don't we just stop rlying on pypi.appspot.com
[16:28:24] <elarson> dingus9: so you are saying that when you use a git+ssh entry in your requirements.txt it doesn't subsequently install that packages requirements?
[16:29:10] <dingus9> it seems to fail for nested packages not available from pypy
[16:29:42] <dingus9> IE: a git repo requiring another git repo
[16:32:12] <elarson> dingus9: hmm... thinking about it for a second, wouldn't pip checkout the repo and install it via pip install -e in which case it would look for a setup.py that couldn't have another git repo as a dep. right?
[16:42:58] <dingus9> elarson: I'm doing from pip.req import parse_requirements
[16:43:19] <dingus9> it seems to work from setup.py but IDK anymore
[16:44:03] <elarson> dingus9: ah, so in the sub-repo's setup.py you do that?
[17:00:25] <dingus9> the actual error I'm getting is "Could not find any downloads that satisfy the requirement my-reponame"
[17:01:25] <dingus9> elarson: is there a way to specify what a -e git+ssh repo provides?
[17:02:31] <dingus9> I tried adding the ==version to the end of the #egg string which makes pip think it's to find that non existent version
[17:02:41] <dingus9> I want to provide that version some how
[17:03:51] <elarson> dingus9: I'm not really sure. I typically would just use a build script for this sort of thing rather than try to cook it into my setup.py
[17:04:53] <dingus9> hmm ok just noticed my second dependency is being installed as python_keystoneclient-dev
[17:05:08] <dingus9> maybe I can ref that generated name