[00:46:50] <lifeless> tchaypo: when will you be available ?
[00:52:25] <lifeless> ok, so I'm going to poke at this rebased resolver branch a bit. tchaypo - when you're around, please ping me on messenger or hangouts, as I won't see IRC
[08:22:28] <xafer> https://github.com/pypa/pip/pull/3106 to appease the search gods
[13:22:16] <xafer> Maybe we should switch pip/develop and pip/master to protected branches (the github feature) ? https://github.com/pypa/pip/settings/branches
[13:31:52] <dstufft> ah did we get that enabled for our acocunt already
[13:33:02] <dstufft> xafer: good idea, I protected master and develop, I didn't require status checks because our tests are too flakey atm :/
[13:42:10] <xafer> it makes me think of https://github.com/pypa/pip/issues/3074 , what versions are we supporting ? :)
[13:43:20] <dstufft> Generally the answer to that is, we test the latest versions of each series, and anything else we'll accept patches if someone makes them and they don't hurt the code readability too bad
[13:59:07] <sigmavirus24> dstufft: btw, just noticed I couldn't set those protected branch settings in twine
[13:59:14] <sigmavirus24> Would you mind protecting master?
[13:59:35] <dstufft> Do you want status checks required?
[14:00:10] <dstufft> (I tend to lean towards no, becuase they make some things more annoying, like requiring all PRs to be updated after anything merges to master)
[14:00:13] <sigmavirus24> Yeah I don't see why not, our stuff is stable enough (although minimal)
[19:09:27] <lifeless> dstufft: and we need your input on https://github.com/pypa/pip/pull/3105
[19:09:54] <lifeless> dstufft: if you're interested, the broad set of work we're pushing on is https://trello.com/b/n6jGWb3l/requirements
[19:10:04] <dstufft> Does "I3046" mean something that I'm not aware of
[19:10:20] <dstufft> lifeless: looks like a private board
[19:18:50] <dstufft> lifeless: so I don't fully grok what the code is doing in #2937, but I don't see anything that stands out as wrong and I think I understand the high level problem it's trying to solve, so I'm happy to merge it since you say it's good
[20:10:07] <lifeless> dstufft: so 2937 is solving a bug
[20:50:45] <xafer> If there is no blocker, I think I'll merge https://github.com/pypa/pip/pull/3085 tomorrow - the documentation can be extended afterwards, same for the default of the destination_dir option
[20:52:56] <xafer> I think a good part of the "pip install" documentation can be extracted and factorized with "pip wheel" and "pip download"
[20:52:59] <lifeless> dstufft: so yeah please do merge 2937
[20:53:29] <lifeless> xafer: does pip download do things like taking the union of conditional requirements?
[20:54:04] <xafer> pip download is currently just an alias of pip install --download-dir
[21:00:42] <dstufft> someday I won't constantly feel like I'm about 20 messages behind what everyone needs from me
[21:00:55] <xafer> yup I understood the ack part, not the "union of conditional requirements" :p
[21:01:38] <xafer> #2937 seems to require the "#egg=" in the constraint file ?
[21:03:28] <dstufft> xafer: will ``pip download`` on something that conditionally requires argparse on Python 2.6 always donwload argparse, even when run on not-Python 2.6
[21:03:35] <dstufft> and I'm pretty sure the answer to that is No
[21:05:48] <xafer> so if the "#egg=" part is required for the constraints, a note in https://github.com/pypa/pip/blob/develop/docs/user_guide.rst#id20 would be welcome :)
[21:49:29] <dstufft> lifeless: can you remind me later this week about 3105? I'll try to remember but I'm kind of overwhelmed right now and tomorrow is gonna be real bad with lots of family appointment stuff