[00:39:50] <njs> [Tritium]: re: venvbs, you might be interested in my mad-science idea of writing a pip+virtualenv replacement whose key idea is that (a) it lives "outside" the venv instead of "inside" it like pip does, so you can make it a one-time single-file download and use it for all your envs, and (b) instead of all the horrible screwinga round that virtualenv needs to do, we just stick pre-built wheels of python interpreters up on pypi, so when you want to create a new
[00:39:51] <njs> environment you just say "give me python 3.3 with ..." and it downloads and unpacks that and then isntalls the requested packages.
[00:40:51] <njs> I haven't actually done anything on this, but it seems like an idea worth playing with (the other part being that it could be a good testbed for pushing the ecosystem forward without pip's backward compatibility constraints). Maybe I'll try to recruit some folks to sprint on it at pycon or something :-)
[01:12:45] <dstufft> njs: I'm pretty sure we can get pip to work outside of the virtual environment once build dependencies are working
[03:17:26] <[Tritium]> For the sake of onboarding new python developers... or even build environments... it would be nice to have a one file "hers your environment, without root (looking at you docker)"
[09:32:50] <ionelmc> [Tritium]: can you elaborate? what do you mean 'without root'?
[09:33:32] <[Tritium]> ionelmc: you need root... or to be in a root equivilant group... to use docker
[09:34:19] <[Tritium]> if you are in the docker group, you might as well have root
[09:34:29] <ionelmc> yes but that's unrelated to virtualenv?
[09:38:06] <[Tritium]> I was equating a single file pip+virtualenv option to a docker container for python only (and without root)
[09:39:05] <[Tritium]> I was referencing an earlier conversation... that was apparently done hour earlier
[13:55:03] <bean> Anyone available to help me out with a question regarding PyPI, and more specifically, the download links for packages there?
[14:03:54] <gchristensen> bean: best to just ask your question
[14:08:49] <bean> gchristensen, thanks. It was related to issues with direct downloads from PyPI for caching purposes, but bitbucket/pypi/438 seems to have an answer for me.
[15:15:33] <nedbat> my appveyor builds are now all failing, and it seems to be something about pip: https://ci.appveyor.com/project/nedbat/coveragepy/build/default-314/job/vy3m6nwi1b3jgbtm#L375 any clues what's going on here? Is it windows-specific? appveyor-specific? Any clues at all are welcomed :(
[15:17:05] <dstufft> nedbat: you're installing pip==8.1.1 but pip 8.1.2 is already installed
[15:24:59] <nedbat> dstufft: thanks for the pointer. seems like tox should change its default :)
[15:28:57] <nedbat> dstufft: wow, lots of people set this, but none seem to use what you suggested: https://github.com/search?p=1&q=install_command+filename%3Atox.ini&type=Code&utf8=%E2%9C%93
[15:30:05] <dstufft> nedbat: it's ok, a lot of people are often wrong :P (ok, to be fair a lot of those are trying to change the default flags that get passed to pip)
[15:33:26] <nedbat> dstufft: weird: that setting in tox fails with: /Users/ned/coverage/trunk/.tox/py26/bin/python: pip is a package and cannot be directly executed