Skip to content
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

emmet.pyv8loader: Unable to download packages list. URL error [WinError 10060] #14

Open
cheahkhing opened this issue Aug 18, 2014 · 6 comments

Comments

@cheahkhing
Copy link

Hi, emmet.pyv8 still always fail on startup, i am in a corporate firewall environment which i think pyv8 didn't use the proxy i have in windows. For sublime package manager, it works without any problem as it is detecting the proxy correctly. Not sure where can i set the proxy for pyv8 loader?

@gravidThoughts
Copy link

Same issue.

Manually installed PyV8 per exact instructions, and on restart, it still appears to attempt to download binaries.

Manual instructions indicate package folder for ST2. I have ST3 which also has the ability to browse the package folder. Is it possible that in ST3 this is no longer the correct folder?

@belgoros
Copy link

Same problem on a Windows 7 64x PC.

  • Installed ST3, build 3065.
  • add proxy settings
  • installed some needed packages without problems
  • install emmet package via Package Control and got the nice success confirmation page
  • restarted ST3 and got the error message (...wait while Py8 binaries to be downloaded etc.)
  • followed the instructions described at https://github.com/emmetio/pyv8-binaries
  • downloaded the binaries pyv8-win64-p3.zip
  • unzipped it into C:\Users\XXXXX\AppData\Roaming\Sublime Text 3\Packages\PyV8\pyv8-win64-p3
  • restarted ST3 and got the same error message.

Most of the available emmet shortcuts do not work at all.

@jeromelachaud
Copy link

same here on Windows 7 64x PC

@ezeeyahoo
Copy link

Issue persist with latest build as well. Please anyone?

@jackqqxu
Copy link

I got the same problem.

@silvster27
Copy link

Same problem and same build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants