-
Notifications
You must be signed in to change notification settings - Fork 17
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
Problem initializing? #13
Comments
I have the same problem |
Sounds like the Python used by Sublime isn't compiled with SSL support. |
I think that's the case for linux. But on the other hand, the source is a http url so I don't understand why this is a problem. |
PyPI now only supports downloading packages over https, so it's redirecting to an https url. |
Maybe it would be better to just bundle the coverage tarball with this plugin. |
Can workaround this on Linux by fetching the package via shell, e.g: cd ~/.config/sublime-text-2/Packages/Python\ Coverage
wget http://pypi.python.org/packages/source/c/coverage/coverage-3.5.2.tar.gz
tar -xzvf coverage-3.5.2.tar.gz coverage-3.5.2
mv coverage-3.5.2/coverage/ .
rm -rf coverage-3.5.2*
touch SublimePythonCoverage.py # Tell Sublime to reload the plugin |
Came across this error when trying to load it:
Reloading plugin /home/cosmogia/.config/sublime-text-2/Packages/Python Coverage/SublimePythonCoverage.py
SublimePythonCoverage installing coverage.py.
Traceback (most recent call last):
File "./sublime_plugin.py", line 62, in reload_plugin
File "./SublimePythonCoverage.py", line 16, in
payload = urllib.urlopen(SOURCE).read()
File ".\urllib.py", line 86, in urlopen
File ".\urllib.py", line 205, in open
File ".\urllib.py", line 360, in open_http
File ".\urllib.py", line 373, in http_error
File ".\urllib.py", line 657, in http_error_301
File ".\urllib.py", line 638, in http_error_302
File ".\urllib.py", line 653, in redirect_internal
File ".\urllib.py", line 202, in open
File ".\urllib.py", line 214, in open_unknown
IOError: [Errno url error] unknown url type: 'https'
The text was updated successfully, but these errors were encountered: