-
-
Notifications
You must be signed in to change notification settings - Fork 774
Prevent multiple issues related to KeyError: 'pylint' #1030
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
Comments
@HaleTom Also, in the https://github.com/python-mode/python-mode#how-to-install We've migrated to the develop branch a long time ago (~2 years). I can't see much reasons to go back to the master branch since our development rate is very low ATM. That would just cause issues for the users that are already using python-mode and have installed it for the past two years, IMHO. |
Btw, if there is any plugin manager instruction missing, Pull Requests are welcome! :) |
It must have been a glitch in Neobundle... perhaps I killed it because the submodule clone was taking a long time, and it didn't recover properly. Here's the config which I confirm working for NeoBundle:
|
Thanks @HaleTom ! |
Issues related to
KeyError: 'pylint'
are quite common: #774 #775 #783 #863 #864 #902Here's the general gist:
It took me ages to to work out the solution
For the googlers:
Don't use
master
, usedevelop
:NeoBundle 'python-mode/python-mode', 'develop', { 'on_ft': 'python' }
It took me a while to realise that I then had two plugin directories:
bundle/python-mode
bundle/python-mode_develop
In the 2nd directory, type:
Would you please either:
master
branch (or describe what is it's purpose)README.md
to requiredevelop
branch with appropriate plugin manager instructionsgit
commandThe text was updated successfully, but these errors were encountered: