[01:19:31] <dstufft> huh? what do you mean, we don't discover any dependencies until after the requirements.txt has been compeltely parsed
[01:19:35] <lifeless> do I need to implement that for no-binary and only-binary
[01:20:20] <dstufft> pip doesn't recursively read requirements.txt, it only reads the ones you pass into -r requirements.txt (and ones they refer to with -r), it's a pbr thing to make a requirements.txt mean anything when you don't pass it into -r
[01:20:28] <dstufft> and yea, it should probably be implemented for it
[01:57:42] <lifeless> if you were broadly interested
[01:58:02] <lifeless> I could writeup .pyi files for some of the bits of pip I need to touch to get setup_requires done
[02:01:23] <dstufft> lifeless: dunno enough about it, I probably wouldn't commit them to develop but it'd probably be interesting to see them if you wanted to do them
[02:01:53] <lifeless> dstufft: one of the potential things is to add a new travis job for such things
[02:02:03] <lifeless> dstufft: (perhaps not on day one :))