Hi @srusskih how is it going? Did you see there is a new jedi version? 0.12.0, so I was trying to integrate it and using the current setup it does not work. It incorporates a new way to configure
jedi.Script, using Environments... so basically you create an
Environment telling the path to a virtualenv and then you pass that to
jedi.Script script and it does ll the magic.
The good thing is that you don't need the daemon any more because you could run jedi inside the Sublime Python interpreter and configure the Envioroment depending on the project so you can have direct communication with Jedi.
The bad is that that will require some heavy work in the integration between the plugin and the new jedi.
What do you thin? Any idea?
--- a/Makefile +++ b/Makefile @@ -12,8 +12,8 @@ dummy: dependencies: rm -rf dependencies/ mkdir dependencies/ - $(call get_dependency,jedi,https://github.com/davidhalter/jedi,v0.11.1) - $(call get_dependency,parso,https://github.com/davidhalter/parso,v0.1.1) + $(call get_dependency,jedi,https://github.com/davidhalter/jedi,v0.12.0) + $(call get_dependency,parso,https://github.com/davidhalter/parso,v0.2.0)
from django.|asking for autocompletion fallsback to the sublime completion
91998 ?? S 0:00.39 /usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/Resources/Python.app/Contents/MacOS/Python ../dependencies/jedi/evaluate/compiled/subprocess/__main__.py ../dependencies