[00:04:08] <xafer> dstufft, done in https://github.com/pypa/pip/pull/2463
[01:39:39] <carljm> wickman: I use nested requirements files. But just for stuff like base/prod/dev, not for anything where I've ever cared about having scoped --find-links etc.
[01:55:07] <wickman> my question is more aimed at those implementing requirements parsers and the like. i will probably implement it the "correct" way but it will differ from what pip does.
[01:55:42] <wickman> in other words, scope flags that alter the resolution behavior to only the requirements therein.
[21:37:09] <pjdelport> Quick question: running the pip tests locally, i see that many of them fail because of Subversion and Bazaar not being installed.
[21:37:30] <pjdelport> Would it be a good idea to modify the test suite to skip them instead?
[21:37:38] <pjdelport> (If those are not installed.)
[21:43:05] <dstufft> pjdelport: I think there was a PR to do that before, not sure what happened to it. The answer though, is yes that's fine to do, as long as we can also assert that those tests *msut* be run sometimes too. IOW the skip would need to be conditional, we'd want those tests to fail if svn is not installed on the CI not skip
[21:46:08] <pjdelport> dstufft: Maybe a good approach is to just have an intentional flag of some sort to disable them, and to document that in docs/development.rst?
[21:47:25] <pjdelport> That PR seems to do the right thing, then.
[21:47:32] <pjdelport> Except it needs updating to merge?
[21:54:49] <dstufft> yea it might be it just got lost in the shuffle