[00:24:33] <dturner_> I was wondering what the release process is for pip? https://github.com/pypa/pip/issues/1350 just bit me, and it looks like there's a fix that hasn't quite made it into a release yet (see the last comment, from thomasboyt).
[00:44:36] <dstufft> dturner_: the release process is more or less, whenever I make a release
[00:45:02] <dstufft> dturner_: I'm planning to make a release after setuprools 8.0 is released
[00:46:14] <dturner_> Maybe it would be possible to cut a 1.5.7 with just this fix? I don't know what the setuptools schedule is like, so maybe 8.0 will be released tomorrow.
[00:47:31] <dstufft> dturner_: I think maybe a week or so assuming no issues are found with 8.0b1
[00:50:28] <dturner_> OK, I can apparently work around it for now by hacking my virtualenv copy of pip. Thanks.
[00:53:30] <dstufft> dturner_: you can install the dev verison of pip too
[00:55:57] <dstufft> it'll take a minute or so because cloning our repo is slow
[00:56:52] <dturner_> Yeah, I don't really want to put that into the main script that generates our virtualenv because ~1500 twitter engineers suddenly cloning your repo can't be good for github (or for our build times). But fortunately, it looks like this issue only hits some of us.
[14:43:16] <collinanderson> dstufft: re tarball: could use https://github.com/pypa/pip/archive/develop.tar.gz
[18:18:45] <Wooble> Is https://wiki.python.org/moin/CheeseShopDev saying the "previous" version on pypi ran until the end of 2013 a reference to there actually being different code running currently on pypi.python.org, or just... wild optimism about warehouse being done?
[18:21:09] <dstufft> idk why it says previous, bitbucket.org/pypa/pypi is still whats deployed