Log file Viewer

[13:49:58] <jonathanj> I'm trying to create a new package (called "compose") but trying to upload my PKG-INFO to PyPI I get:

[13:50:00] <jonathanj> Forbidden

[13:50:02] <jonathanj> You are not allowed to store 'compose' package information

[13:50:32] <jonathanj> i'm not sure why i'm not allowed to store it, https://pypi.python.org/pypi/compose is 404

[13:51:46] <tos9> jonathanj: the URLs (at least used to be) case sensitive, so it could be at Compose

[13:51:56] <tos9> but that doesn't appear to be the case this time

[13:52:07] <tos9> so I'd guess what happened is a package that got taken down possibly.

[13:52:46] <jonathanj> so if there's no package currently on pypi with that name, is it possible i can have that name?

[13:52:48] <tos9> jonathanj: dstufft or richard jones (who doesn't appear to be in here but I think is in #python-infra or you could mail him) should be able to tell you exactly

[13:53:01] <tos9> jonathanj: "probably yes" I think, assuming my guess is right

[13:53:39] <tos9> never mind he's not there either, not sure what TZ he's in.

[13:53:56] <jonathanj> tos9: thanks, i'll wait until someone has time to take a look

[16:02:08] <dstufft> jonathanj: compose is registered by someone, they don't have any releases published though

[16:47:28] <robak> hi

[16:47:41] <robak> should it be possible to create virtualenv using pypy?

[16:47:59] <tdsmith> yep!

[16:47:59] <robak> I cant get it to work, it fails like that: https://gist.github.com/bartekrutkowski/47cfecc67ce7724cd1b7

[16:48:41] <robak> and I am out of clues what the problem could be, I am able to reproduce the problem on another OS with pypy 2 and 3 as well

[16:50:09] <robak> it does work when I use --no-setuptools, but then the venv created isnt very useful

[16:50:57] <tdsmith> hmmmmm, works for me on osx/homebrew

[16:52:21] <robak> I am seeing it on FreeBSD

[20:58:22] <agronholm> ubuntu 15.04...works fine here

[20:58:54] <nanonyme> robak, why on earth would you even consider --no-setuptools?

[20:59:21] <nanonyme> Oh, bad workaround. Never mind

[20:59:32] <wsanchez> Does this PITA look familiar to anyone:

[20:59:32] <wsanchez> Download error on https://pypi.python.org/simple/cffi/: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -- Some packages may not be found!

[20:59:47] <wsanchez> I'm using Linux, which is confusing and scary

[21:02:03] <nanonyme> wsanchez, I'd try running it with more verbosity levels to see if there's a more specific error to the SSL

[21:02:16] <wsanchez> a'ight

[21:02:42] <nanonyme> This is a machine with up-to-date root CA's though, right?

[21:03:37] <wsanchez> nanonyme: Not sure how to verify, but this does load the page: `curl https://pypi.python.org/simple/cffi/`

[21:12:11] <nanonyme> Right

[21:12:38] <nanonyme> wsanchez, well, might still want to run it with a high verbosity level

[21:27:43] <wsanchez> pip --verbose is more chatty but doesn't add any SSL info, unfortunately.

[21:31:05] <wsanchez> FYI" http://pastebin.ca/3017942

[23:05:09] <robak> nanonyme: I am not considering it, I was simply debugging the problem and discovered that when this option is being used, the problem goes away - I even said that the venv is useless when this is used