On 24/12/2015 14:36, Cory Benfield wrote:
On 24 Dec 2015, at 11:17, Chris Withers <ch...@simplistix.co.uk> wrote:
Here's a couple of examples of this problem in the wild:
https://github.com/alekstorm/backports.ssl/issues/9
http://stackoverflow.com/questions/32978365/how-do-i-run-psycopg2-on-el-capitan-without-hitting-a-libssl-error
https://github.com/psycopg/psycopg2/issues/385
I'm well out of my depth here, I just want to use these libraries, but I'm
happy to try and do the work to make the world a better place for Mac users of
these libraries...
I think this is actually nothing to do with Python itself, and everything to do
with Mac OS X and the neutered way it ships OpenSSL. Given that the library
you’re actually having difficulty with is cryptography, I recommend using their
mailing list[0] to ask your question again. I happen to know that there have
been a few problems with OS X and OpenSSL since El Capitan, so you’re probably
not the first to encounter them.
Hi Cory,
I'm not not sure, _ssl included in a Python distribution works and does
the right thing, it's third party packages built on the machines that
appear to have the problem.
How does Python itself "get it right" and how could psycopg2 and
cryptography mirror that?
This feels like a dynamic linking problem rather than something
ssl-specific.
cheers,
Chris
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
