-
Notifications
You must be signed in to change notification settings - Fork 7
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
SSL issue with pip pysbol package on Linux #202
Comments
Hi Tim, I've attempted to correct this issue by recompiling libpython with OpenSSL and deploying a new wheel. At your convenience, please update to the new wheel and re-test with Python3.6.
This should upgrade your package to pySBOL-2.3.0.post20-cp36-cp36m-manylinux1_x86_64.whl |
Here is the result:
|
@tim-tx Hi Tim, I've made another attempt at building the Linux wheel with support for secure HTTP: At your convenience, please update to the new wheel and test with Python3.6. $ pip install --user --upgrade This should upgrade your package to pySBOL-2.3.0.post21-cp36-cp36m-manylinux1_x86_64.whl |
@bbartley Hi Bryan, I did the upgrade, though I seem to be running into the same issue:
And then:
|
Hi, the latest version of pySBOL now has a workaround for this issue. Before sending a request to synbiohub, you can configure the certificate path for your Linux distribution, as follows:
Where By default the certificate path is configured for Red Hat Linux |
Can you deploy a Linux / Python 3.7 wheel for pySBOL-2.3.2? If I can get a wheel for this I'm happy to test. I wonder if there isn't some appropriate abstraction layer that can tell you where to look, that could be used instead of this workaround in the future? As I remember I did not have any SSL issues when I built the Python bindings from libSBOL directly. |
@tim-tx There is now a Python 3.7 wheel available for Linux that should auto-configure the certificate path. It seems to work on Ubuntu and CentOS so far:
You should get: |
Python 2 and 3 affected (2.7 and 3.6 tested).
Steps to reproduce:
Result:
The above steps work against pysbol built manually from the libSBOL source.
The text was updated successfully, but these errors were encountered: