You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
In your documentation its stated that: python-mode seems to interfere with jedi so we should disable it. I dont want to start a discussion about pros and cons. But rather we made it explicit that what is it exactly what it is that should be disabled(Outright disabling is rather extreme IMHO)?
I think this documentation will make the transition/cooperation between python-mode users and jedi users easier. There are also features like auto refactoring that aren't really available in jedi that are as good as rope.
The text was updated successfully, but these errors were encountered:
Closing this, because it doesn't really help with the current status quo. If somebody is able to document this well, I'm happy to take any pull requests. But it's not really a jedi-vim issue, since jedi-vim is at the moment a small and lightweight plugin, compared to python-mode. I think the problem is probably on the python-mode side, because they do a thousand different things (like debugging, etc).
i.e. you just have to decide at the moment which plugin to use. Jedi will introduce refactoring at some point, but we still need to improve the parser at the moment.
Hi,
In your documentation its stated that: python-mode seems to interfere with jedi so we should disable it. I dont want to start a discussion about pros and cons. But rather we made it explicit that what is it exactly what it is that should be disabled(Outright disabling is rather extreme IMHO)?
I think this documentation will make the transition/cooperation between python-mode users and jedi users easier. There are also features like auto refactoring that aren't really available in jedi that are as good as rope.
The text was updated successfully, but these errors were encountered: