search

markbaas / atom-python-autopep8

MIT License
9 stars 6 forks source link

executable not being picked up from PATH #2

Closed michaelaye closed 7 years ago

michaelaye commented 9 years ago

This seems to be a common problem currently in Atom, apparently some API has changed inside Atom that prevents this from working? I currently have to provide the full path in the settings, as for flake8 and isort, those packages suffer from the same problem. I don't know if this should be solved on Atom level or on package level. I would prefer the flexibility to have it set by the PATH environment because that way the currently active virtual environment decides which executable is being used for this. Even so maybe for pep8 there are no differences between Python2 and Python3?

Sapphire64 commented 8 years ago

@michaelaye do you still have this problem? I just installed autopep8 to my Mac and without restarting and anything else got atom-python-autopep8 working, Autopep8 Path in settings is the default value.

Atom 1.1.0

michaelaye commented 8 years ago

currently i have the problem that it doesn't work at all, neither with the path set nor without. :(

dpo commented 8 years ago

Same here.

harryjubb commented 8 years ago

+1 here as well.

I get this in the status bar:

run_parse_fpocket_py_ __users_hj4_google_drive_scripts
Moini commented 7 years ago

Same for me.

tianjiqx commented 7 years ago

OK, It work! We need install autopep8 by pip install autopep8 . Then use the path. //me, too.I don't know how to set the path.

michaelaye commented 7 years ago

Still not working here at all, neither with or without setting the path. Atom: 1.14.4 macOS 10.11.6

michaelaye commented 7 years ago

I just implemented #5 in my fork, and all works, even without setting the path. Try my fork if you want. (apm install git-url works just fine) ;)
https://github.com/michaelaye/atom-python-autopep8