> On 24 Dec 2015, at 14:40, Chris Withers wrote:
> 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
Hi All,
I hit this every time I install packages on Mac OS X that use libssl, it
looks like extensions are built linking to .dylib's that are not
resolveable when the library is actually used:
>>> from OpenSSL import SSL
Traceback (most recent call last):
File "", line 1, in
File "python
On 24/12/2015 14:36, Cory Benfield wrote:
On 24 Dec 2015, at 11:17, Chris Withers 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-hittin
> On 24 Dec 2015, at 11:17, Chris Withers wrote:
>
> Hi All,
>
> 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
> h
Hi All,
I hit this every time I install packages on Mac OS X that use libssl, it
looks like extensions are built linking to .dylib's that are not
resolveable when the library is actually used:
from OpenSSL import SSL
Traceback (most recent call last):
File "", line 1, in
File "python2.
