-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSX-builds: Deprecated OpenSSL library inside python@2 and python3.5 #70
Comments
#68 shall fix the issue when building with python 2.7
c.f. https://bugs.python.org/issue17128, I don't think there's some plan for python 3.4 & 3.5 official packages |
I saw the pr afterwards and I am waiting for it 👍 I don''t know if correct linking after: Is there a workaround for the user to replace the python you use for python3.5 with Thanks in advance |
Both relevant PRs (#68 and #69) are merged, and seem to be succeeding (#68 is still building but can hardly break any build). Until @joerick manages to find some time to approve and publish a new release, you can always |
Hey @YannickJadoul - just catching up on this. Thanks for merging these PRs! I'm happy to cut a release now. Gimme a few mins.... |
Released as 0.8.0! |
I'm pretty sure #69 won't help (as mentioned in #69 (comment)). |
Could you try the patch to check it really corrects issues you're seeing ?
|
This is fixed on Python 3.4 and 3.5 as of 0.9.1, which was just released :) |
I got a very well known error this days, concerning OSX and
openssl
which is:see from
urllib2
inpython@2
andurllib
inpython3.5
.After searching a lot I found out that this is because of deprecated version of open-ssl used by python: "OpenSSL 0.9.8zh 14 Jan 2016"
[You can see that by running
{python} -c "from __future__ import print_function; import ssl; print(ssl.OPENSSL_VERSION)"
- see fromurllib2
inpython@2
andurllib
in see]Instead, a version >= 1.0.2 is needed to avoid the error and although the system has it (as you can see when brew installing openssl), it is not the one executed from path. Even if you change the path and append the location of the desired binary in front, this is not a workaround for python as the correct libraries are not linked. An optional workaround is to
brew install {python} --with-brewed-openssl
and afterwards replace the one in path marked by {python} tagger. For this workaround you can see here.I am stuck and I don't know how to proceed because of aliases of python version and mysticism of where is the python executable is and if and how it can be replaced by a new one (if there are predependencies installed that are not the ones installed by user). That's why I am opening an issue and suggesting adding an installation of python in osx with the current version of openssl in your package, driven by the fact that this is not a problem of the project that I am testing and a normal user would be able to solve any dependency issue on his machine.
Thanks in advance for your awesome package and I hope the problem was made clear :)
The text was updated successfully, but these errors were encountered: