does jedi support python 3 ?
See original GitHub issueI am using python 3.4.3 in virtualenv. While opening a python file I get these errors.
"asynctest.py" [noeol] 24L, 454C
Error detected while processing function provider#python#Call:
line 1:
Exception('no request handler registered for "python_execute_file"',)
Press ENTER or type command to continue
If I disable the jedi plugin these errors go away. Also in python 2 these errors dont pop up. Any idea what can be done to fix it ?
Issue Analytics
- State:
- Created 8 years ago
- Comments:18 (2 by maintainers)
Top Results From Across the Web
Jedi - an awesome autocompletion, static analysis and ...
Jedi is a static analysis tool for Python that is typically used in IDEs/editors plugins. Jedi has a focus on autocompletion and goto...
Read more >Suppport for python 3.10 alpha 6 · Issue #1756 · davidhalter/jedi
It doesn't look like jedi supports the latest features of python 3.10.0a6 . Specifically, support for pattern matching syntax.
Read more >Jedi - Python autocompletion - Package Control
Please note Jedi does not support Python 3.3 any more. Installation. with Git. cd ~/.config/sublime-text-2/Packages/ git clone https://github.com/ ...
Read more >Dave Halter (@jedidjah_ch) / Twitter
Jedi 0.18.0 is out. Finally dropped Python 2. Improves Python 3.9 support.
Read more >python-jedi - SUSE Package Hub
Jedi is a static analysis tool for Python that can be used in IDEs/editors. Its focus is autocompletion and static analysis. Jedi has...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
let g:jedi#force_py_version=3 or call jedi#force_py_version(3)
@vmindru Thanks for sharing. It will slowdown your Vim startup though. I recommend to use Neovim instead in general, and in this particular case you are able to configure the plugins usually instead (jedi-vim (
g:jedi#force_py_version
), UltiSnips etc).If you want to keep this method, see how jedi-vim does it: https://github.com/davidhalter/jedi-vim/blob/7ddc50829eaa8350aa2bd60f4bb04e6620329b4f/autoload/jedi.vim#L76-L78:
And you should also set
g:jedi#force_py_version
then. Related: https://github.com/davidhalter/jedi-vim/pull/674.