Catalyst.Spacy.Test - urllib3 needs openssl 1.1.1+
See original GitHub issueDescribe the bug
Running the Catalyst.Spacy.Test
returns the following error:
Unhandled exception. Python.Runtime.PythonException: ImportError : urllib3 v2.0 only supports OpenSSL 1.1.1+, currently the 'ssl' module is compiled with OpenSSL 1.1.0j 20 Nov 2018. See: https://github.com/urllib3/urllib3/issues/2168
To Reproduce
- Open the solution in Visual Studio 2022.
- Debug/Run the project
Catalyst.Spacy.Test
Expected behavior The processed document should be appear as json in the console.
Screenshots
Issue Analytics
- State:
- Created 4 months ago
- Comments:5
Top Results From Across the Web
ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+ ...
The issue is that the version of the 'ssl' module that is currently installed in your environment is compiled with LibreSSL 2.8.3, which...
Read more >NotOpenSSLWarning: urllib3 v2.0 only supports OpenSSL ...
I am trying to work with spaCy in Jupyter notebook and VScode on a Mac OS , but every time ... NotOpenSSLWarning: urllib3...
Read more >Fixing ImportError: urllib3 v2.0 only supports OpenSSL 1.1.1+
A growing number of Python developers have been complaining about an ImportError being reported when attempting to import packages that depend ...
Read more >Actions fail with error urllib3 v2.0 only supports OpenSSL ...
Importing requests module will result in action failure because the latest version of requests is dependent on urllib3 v2 and urllib3 v2 ...
Read more >v2.0 Migration Guide - urllib3 2.0.4 documentation
urllib3 v2.0 is now available! Read below for how to get started and what is contained in the new major release. Migrating from...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Most probably due to the older Python.Included package used in Catalyst.Spacy, I’ve updated it in e2bb759 and will update the test project to the latest Catalyst.Spacy package as soon as it is published to NuGet.
The issue has been fixed, however, I’m getting the following error: “Runtime.PythonDLL was not set or does not point to a supported Python runtime DLL”. I have tried setting Runtime.PythonDLL to the python37.dll installed by Python.Installer but it didn’t work. Should I open another issue?