Closed alcarney closed 1 year ago
It would appear that this is a Windows only issue.. I am unable to reproduce this on Linux....
It would also seem that this is not limited to conda either....
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/esbonio/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/esbonio/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/esbonio/
Could not fetch URL https://pypi.org/simple/esbonio/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/esbonio/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping
ERROR: Could not find a version that satisfies the requirement esbonio>=0.6.0 (from versions: none)
ERROR: No matching distribution found for esbonio>=0.6.0
WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host='pypi.org', port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available.")) - skipping
The terminal process "c:\....\.env\Scripts\python.exe '-m', 'pip', 'install', 'esbonio>=0.6.0'" terminated with exit code: 1.
This will be made redundant by v1 of the language server + vscode extension
See #609 for more details
Allowing the extension to automatically install the Language Server when a conda envrionment is configured does not work. Something about them is different enough that simply calling the corresponding python executable is not sufficient to allow it to discover all the supporting libraries it needs.
Manually opening a new terminal and letting the Python extension activate the environment first and then running
pip install ...
works fine though