Log file Viewer

[01:31:24] <wanghua> hi all, I met a problem when I use pip bebind a proxy. The log is Could not fetch URL https://pypi.python.org/simple/aioeventlet/: There was a problem comfirming the ssl certificate: [SSL: CERTIFICATE_VERIFY_FAILED] certicate verify failed(_ssl.c:590) - skipping.

[01:31:30] <wanghua> Can anyone help me

[12:10:37] <wiggy> is there anything blocking a pip 8.1.2 release?

[15:24:04] <moldy> hi

[15:25:00] <moldy> https://dpaste.de/mvHY is this a bug?

[16:28:38] <dowwie> in case anyone wasn't aware, dstufft talks about pypa http://pythonpodcast.com/donald-stufft-pip.html

[16:40:51] <dowwie> dstufft: that's good info about package signing

[18:34:06] <tbsf> pypi going down?

[18:40:58] <Wooble> hm?

[18:50:38] <hobarrera> There's a but in PyPI that's blocking me from doing a proper release.

[18:50:46] <hobarrera> It's been reported for a week now, affecting pleny of users.

[19:13:18] <hobarrera> Hello?

[19:13:57] <Wooble> hi?

[19:14:46] <Wooble> (pypi is for the most part unmaintained AFAICT. You can't even search for projects uploaded in the last 2 months...)

[19:15:19] <apollo13> there is much work going on to switch over to warehouse

[19:15:54] <hobarrera> The problem is of my users (including myself) use pip.

[19:16:28] <hobarrera> An pypi is still the canonical source for python packages, generally

[19:16:30] <apollo13> hobarrera: which issue? django issued a release recently just fine

[19:16:40] <apollo13> and downloading and installing with pip also works fine for me

[19:17:56] <hobarrera> Upoading packages returns 500, but the version is pushed.

[19:18:08] <hobarrera> SOME package tarballs/wheel are available, otehr are not:

[19:18:10] <hobarrera> https://bitbucket.org/pypa/pypi/issues/442/500-server-error-trying-to-register

[19:20:26] <hobarrera> Package URLs like these don't work for any recently uploaded package either:

[19:20:29] <hobarrera> "https://pypi.python.org/packages/source/t/$pkgname/$pkgname-$pkgver.tar.gz"

[19:20:38] <dstufft> hobarrera: when did you last try to upload

[19:21:07] <hobarrera> Fri Apr 22 15:26:10 2016 -0300

[19:21:19] <hobarrera> Sorry, that's not the last try.

[19:21:24] <hobarrera> Not sure when the last one was.

[19:21:50] <apollo13> so maybe retry?

[19:21:59] <apollo13> maybe the bug is not there anymore? :D

[19:22:09] <dstufft> hobarrera: the problem zzzeek reported should be resolved now

[19:22:21] <dstufft> pypi still intermittently 500's though, but not all the time

[19:22:25] <hobarrera> Pushing a new version now.

[19:22:43] <hobarrera> It's annoying to tag so many releases though...

[19:22:58] <hobarrera> ... And failed uploads are still registered somehow, so can't be retried.

[19:23:07] <dstufft> yea

[19:23:09] <dstufft> Warehouse fixes

[19:23:10] <hobarrera> eg: the tarball for them is unavailable, but pushing a new one is rejected.

[19:23:54] <dstufft> you can try uploading to Warehouse instead, but it may be randomly down and it doesn't purge the cache on PyPI itself so you'll want to edit the package once (even a no-op save should be enough) once all the files are uploaded

[19:25:14] <dstufft> I should probably just deploy a new upload endpoint already

[19:26:10] <hobarrera> Nope

[19:26:12] <dowwie> dstufft: why is it that a pip3.5 install results in wheel failures but a pip3.4 installs just fine

[19:26:19] <hobarrera> Just pushed a new release and:

[19:26:29] <hobarrera> 1. Tarball isn't available under the above URL

[19:26:32] <hobarrera> 2. pip searh does not list it.

[19:26:44] <hobarrera> 3. pypi DOES list it as the latest version, but not in searches

[19:27:41] <hobarrera> pypi is working so badly and erratically that I'd rather have under-development possibly-imperfect code, instead of unmaintained broken one. :P

[19:27:59] <dowwie> dstufft: "failed building wheel" errors, specifically

[19:28:03] <hobarrera> How *would* I push to warehouse?

[19:29:36] <dstufft> hobarrera: that URL structure isn't being used anymore, old stuff is still available under it but new stuff is using a new url scheme for various reasons-- Warehouse has a redirect from the old url scheme to the new url scheme but legacy PyPI is a horrible mess

[19:29:47] <dstufft> search is broken on legacy pypi

[19:30:45] <hobarrera> So package maintainer needs to use URLS like: https://pypi.python.org/packages/1b/b1/15e1e58b9c21707d9a087f1c94fa1b5b2104c162a5b89301fa7788f8c93d/todoman-1.6.3.tar.gz

[19:30:59] <dstufft> hobarrera: I'm in the process right now of trying to get wahtever we have implemented in Warehouse ready for a production deployment actually, and moving the old mess to legacy.pypi.io

[19:31:01] <apollo13> "use" for what?

[19:31:23] <apollo13> hobarrera: imo you should always have considered download urls an implementation detail

[19:32:18] <dstufft> hobarrera: you can use "https://pypi.io/packages/source/t/$pkgname/$pkgname-$pkgver.tar.gz" -- but that's a pre-production deployment so it may or may not go down

[19:33:09] <dstufft> hobarrera: you can publish to warehouse by setting the repository in your ~/.pypirc to https://pypi.io/pypi though.

[19:33:22] <dstufft> dowwie: Can you paste the entire output?

[19:33:43] <gchristensen> dstufft: thank you again for all your work, I imagine it is difficult being on the receiving end of the reports.

[19:35:27] <hobarrera> dstufft: Thanks a bunch!

[19:35:33] <hobarrera> And also, thanks for working on warehouse. :D

[19:37:05] <hobarrera> I'll see if pointing travis there does the auto-deploy for tags too. :)

[19:38:56] <dowwie> dstufft: I pm'd you

[19:39:40] <dstufft> gchristensen: https://s.caremad.io/RyrKokmiMS/fvAf54C.gif (Ok not really, mostly I excel at trying to pretend the bug tracker doesn't exist so I don't feel too guilty all the time about everything being broken, unless I'm getting a ton of emails from it)

[19:40:02] <dstufft> hobarrera: that URL (for uploads) might change in the future to something like https://upload.pypi.io/ (

[19:40:03] <dstufft> oops

[19:40:04] <gchristensen> dstufft: your domain name betrays you.

[19:40:05] <dstufft> oh well

[19:41:21] <ngoldbaum> it's just so difficult how people have these really high expectations about free services...

[19:42:11] <dstufft> PyPI is sort of critical infrastructure

[19:42:16] <dstufft> unfortinately it's just kind of me

[19:44:57] <J1m> FTR, in ubuntu-16.04, ensurepip tells you to pound sand and use apt :)

[19:46:27] <dstufft> J1m: only outside of a virtualenv IIRC, and yea they do that, but at least it tells you the right thing to do to get pip :/

[20:02:42] <ngoldbaum> J1m: debian is the worst :(