On Monday, September 19, 2016 at 10:44:21 AM UTC+1, Floh wrote:
>
>
> > python -c "import ssl; print ssl.OPENSSL_VERSION"
>
> ...which in my case prints:
>
> OpenSSL 1.0.2h 3 May 2016
>
Thanks for the suggestion. I get the same response (1.0.2h), which verifies
that the python used via my PATH
On Monday, September 19, 2016 at 12:28:53 PM UTC+1, Floh wrote:
>
> PS: I also cannot reproduce the problem when going back to MacOS 10.12's
> default python installation, installing and './emsdk update' both work:
>
> ➜ emsdk_portable python -c "import ssl; print ssl.OPENSSL_VERSION"
> OpenSSL
PS: I also cannot reproduce the problem when going back to MacOS 10.12's
default python installation, installing and './emsdk update' both work:
➜ emsdk_portable python -c "import ssl; print ssl.OPENSSL_VERSION"
OpenSSL 0.9.8zh 14 Jan 2016
➜ emsdk_portable python --version
Python 2.7.10
➜
I haven't seen the certificate problem on OSX yet (I'm currently on the
latest MacOS Sierra prerelease-version).
However I'm not using the standard python version coming with OSX (which is
2.7.10), but use the brew version 2.7.12. I have also openssl installed via
brew (although not directly
No idea which version will be used. Emsdk invokes 'python' on the command
line to do all the work (via #!/usr/bin/python shebang at top of emsdk
script), and the http(s) requests it does are launched via python's http
libraries, and git commands via the 'git' command line, by looking its
location
On Sunday, August 14, 2016 at 10:21:57 AM UTC+1, Floh wrote:
>
> Hi, I just got a bug ticket in one of my projects from a user who has
> trouble setting up the emscripten SDK because of an SSL certificate
> validation error in the emsdk script when downloading the file
>
