Upgrade Jedi to 0.12.0 - Githubissues

edelvalle commented 6 years ago

Use Jedi directly inside the sublime Python interpreter without break the interface. Notice this is a suggestion...

Using Environments:

I infer the virtualenv from the python interpreter path.
and the python interpreter path from the virtualenv.
if that does not work I fallback to the default interpreter.
to support extra_packages the I use the sys_path parameter of the jedi.Script constructor.
I removed all the threading stuff, and use set_timeout_async in sublime 3 and set_timeout in sublime 3. So it is non-blocking for sublime 3, and blocking for sublime 2. I think this is a way to make people also upgrade their sublimes.... :laughing:

@srusskih give me your opinion Cheers, Eddy

srusskih commented 6 years ago

You did a great job! Thanks!

Blocking operations for Sublime2 are little worry me. Maybe we can spawn a Thread for ST2 users? Blocking operation can so be annoying, especially when you got stacked after each key-press 🤤

edelvalle commented 6 years ago

Sure, I will do so using the Python 2 API for that... thread.start_new_thread, is that ok?

srusskih commented 6 years ago

Sounds good

edelvalle commented 6 years ago

@srusskih Ready to go!

srusskih / SublimeJEDI

Upgrade Jedi to 0.12.0 #240