[00:47:50] <AA_> I have tried both to create a virtualenv by the simple command virtualenv /home/.../python and also with the options --clear & --always-copy
[00:48:36] <AA_> but in both cases when running the created virtualenv python it will have a sys.path that contains '/usr/lib/python2.7'
[12:14:57] <oberstet_> dstufft: is the following correct? pypi will prevent uploading an already published artifact (like a source dist) for a given package version a second time, but it will NOT prevent publishing _additional_ artifacts for an already published package version?
[12:16:18] <oberstet_> because this is what I think just happened with one of our dependencies, and that broke our (version and hash pinned) builds https://github.com/msgpack/msgpack-python/issues/183
[16:35:19] <oberstet_> dstufft: thanks. too bad. we're gonna switch to u-msgpack, as upstream doesn't want to change what he is doing =(
[16:36:32] <dstufft> oberstet_: Ideally pip would be smarter here, and if there are 5 files available and one of them doesn't match a hash, it'll just ignore that file
[16:37:38] <oberstet_> right. or seal the whole set of artifacts for a package version. or, what does ToR (was it?) have for "doing watertight releases" again?
[16:38:49] <oberstet_> dstufft: meejah pointed me to something state of the art rgd all that (how to move bits to users tamperfree etc), but I forgot
[16:41:55] <simon_weber> can anyone help figure out why https://pypi.python.org/pypi/swaggergenerator isn't found by pip? I always see "Could not find a version that satisfies the requirement swaggergenerator". I can install other packages without problems.
[16:42:24] <simon_weber> (I started with swagger_generator, switched to swagger-generator to appease distutils, then finally removed the dash when that still wasn't working)
[16:43:33] <dstufft> simon_weber: you didn't upload any files
[16:46:00] <simon_weber> dstufft: what do you mean by that? I see a source distribution here: https://www.dropbox.com/s/16cj4ndc9k0p6s3/Screenshot%202016-04-29%2012.38.12.png?dl=0
[18:06:39] <Vye> I'm trying to install pip via get-pip.py, but the python binary I'm using apparently has an incomplete distutils (no distutils.command), causing get-pip.py to blow up: https://dpaste.de/f5gT
[18:09:51] <Vye> Is there any way around this? I do have a working system python interpreter that has the same major version. I'm just not sure if I should use a it to manage packages for this pre-packaged version.