[12:59:52] <jleclanche> does pipenv have an equivalent to `yarn upgrade`?
[13:00:31] <jleclanche> I can't even get pipenv lock to pick up on an updated version of one of my libs :/
[13:01:38] <jleclanche> ah figured out why. question still stands tho
[22:36:44] <rambo123456> So I was happily installing python packages via pip a week ago and now I'm getting the following error: SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:661)'),)': /pypi
[22:37:42] <rambo123456> adding --trusted-host pypi.python.org to the pip command makes it work but I'm interested to know what I changed to change the pip behavior
[22:41:38] <sumanah> rambo123456: could it be that you are working in a virtualenv that was created under a previous version? before you upgraded to 10.13?
[22:41:44] <rambo123456> sumanah hmmm. upgrading might be worth a shot
[22:42:11] <sumanah> rambo123456: Also! heads-up about the new PyPI :) https://pyfound.blogspot.com/2018/03/warehouse-all-new-pypi-is-now-in-beta.html
[22:42:35] <rambo123456> sumanah I know I did a OSX update recently. but not upgrade I don't think
[22:43:10] <sumanah> rambo123456: I suggest you upgrade pip to 9.0.3
[22:43:44] <rambo123456> sumanah ok let me try that. Thanks sumanah!
[22:43:50] <sumanah> and please spread the word, rambo123456
[22:44:51] <sumanah> rambo123456: here's a longer explanation of what's happening in terms of SSL stuff https://github.com/pypa/warehouse/issues/3293#issuecomment-378468534
[22:47:10] <rambo123456> sumanah interesting. I installed pip via homebrew. so I guess Its not going to affect me? I haven't read much of your links yet but will do. Thanks again
[22:50:36] <sumanah> rambo123456: what version of homebrew are you running?
[22:51:43] <rambo123456> sumanah I just tried upgrading pip via >pip install --trusted-host pypi.python.org -U pip... still having the ssl issues after
[22:52:04] <sumanah> rambo123456: what version of pip does it now believe you are using?
[23:04:43] <rambo123456> thanks tdsmith di_codes I ran the command... it hasn't returned but it says okay. am I supposed to have the window up while doing pip commands?
[23:04:59] <tdsmith> no -- it shouldn't return, go ahead and hit ctrl+c
[23:05:03] <tdsmith> the first few lines of the output are interesting
[23:05:46] <tdsmith> specifically the certificate chain section; it "should" look like https://gist.github.com/tdsmith/87d0a5ee5da924d50cf816603e7e7f46
[23:15:31] <rambo123456> I was messing with my .ssh/known_hosts and config earlier. but that shouldn't have anything to do with ssl certificates right?
[23:16:48] <di_codes> rambo123456: sorry for not mentioning this earlier: this is almost definitely not your fault. there have been some infrastructure changes for PyPI
[23:16:53] <rambo123456> the only other thing I can think off is I was playing with creating certificates for xcode
[23:17:18] <di_codes> rambo123456: can you try installing the `certifi` package?
[23:17:32] <di_codes> using `--trusted-host` or whatever works
[23:20:15] <rambo123456> looks like its not my particular python. I just tried it from a docker instance
[23:20:35] <rambo123456> but I logged into another machine and it works
[23:20:46] <rambo123456> but that one has version 8.1.1. pretty old
[23:21:11] <tdsmith> you're sure your clock is right?
[23:21:35] <rambo123456> like the system clock? yea. its the correct time
[23:22:43] <tdsmith> nevermind, also; there used to be a magic list of locations pip would look for certs but i think switching to certifi means that no longer happens