-
Notifications
You must be signed in to change notification settings - Fork 74
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
Autocomplete-python error #22
Comments
Do you have python installed and available? |
Yes, sure, I have. |
Hmm, Can I ask you to try it with one possible fix? Open the provider file at
and replace Old:
New:
I have no idea if it will with the problem, but worth to try. I don't have windows right now to test it by myself. |
And you have to restart your Atom after the change, of course. |
I did it, but I have the same problem. [Enter steps to reproduce below:]
Atom Version: 0.211.0 Stack TraceFailed to activate the autocomplete-python package
Commands
Config{
"core": {
"themes": [
"atom-material-ui",
"atom-material-syntax"
],
"autoHideMenuBar": true,
"disabledPackages": [
"highlight-line"
]
},
"autocomplete-python": {}
} Installed Packages# User
atom-material-syntax, v0.1.1
atom-material-ui, v0.4.7
autocomplete-python, v0.4.3
file-icons, v1.5.8
linter, v1.0.4
linter-flake8, v1.4.2
# Dev
No dev packages |
Hm, thanks for trying. I will try to reproduce it by myself. |
Okay, I will wait |
Another possible solution from stackoverflow: Check if you have "Run this program as an administrator" selected on your python.exe. If you do, try to unselect it. http://stackoverflow.com/questions/30809808/node-webkit-child-spawn-unknown-error |
Oh, it is working! Idiotic selector. I had problems with linter and other packages and it all solved together! Thanks |
[Enter steps to reproduce below:]
Atom Version: 0.211.0
System: Unknown Windows Version
Thrown From: autocomplete-python package, v0.4.3
Stack Trace
Failed to activate the autocomplete-python package
Commands
Config
Installed Packages
The text was updated successfully, but these errors were encountered: