Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Recently vim-jedi stopped working for me where it used to work fine. It now fails during start up. Version-Release number of selected component (if applicable): $ rpm -qv vim-enhanced vim-jedi vim-enhanced-8.1.1991-2.fc30.x86_64 vim-jedi-0.9.0-1.fc30.noarch How reproducible: Always Steps to Reproduce: 1. yum install vim-enhanced vim-jedi 2. vim test.py Actual results: Fails to load with: Error detected while processing function jedi#init_python: line 7: Error: jedi-vim failed to initialize Python: jedi#setup_py_version: could not import jedi_vim: Mod uleNotFoundError: No module named 'jedi_vim'. (in function jedi#init_python[3]..<SNR>45_init_pytho n[50]..jedi#setup_py_version, line 30) Error: jedi-vim failed to initialize Python: jedi#setup_py_version: could not import jedi_vim: Mod uleNotFoundError: No module named 'jedi_vim'. (in function jedi#init_python[3]..<SNR>45_init_pytho n[50]..jedi#setup_py_version, line 30) Expected results: Loads without issues Additional info: https://src.fedoraproject.org/rpms/vim/c/fdad298eb135b3c6d8701c5f65619d0dd53f9a28?branch=f30 dropped Python 2 support. The module vim_jedi module does exist, but itself fails to load vim. $ python2 Python 2.7.16 (default, Apr 30 2019, 15:54:43) [GCC 9.0.1 20190312 (Red Hat 9.0.1-0.10)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import vim_jedi Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named vim_jedi >>> import jedi_vim Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python2.7/site-packages/jedi_vim.py", line 18, in <module> import vim ImportError: No module named vim
I have used https://kojipkgs.fedoraproject.org//packages/vim-jedi/0.9.0/5.fc32/src/vim-jedi-0.9.0-5.fc32.src.rpm on Fedora 30 with mock to build a new package for Fedora 30. After installation of this package "vim /tmp/abc.py" starts without errors. Please would someone with the appropriate rights update the package for Fedora 30 (build on koji, update via bodhi)? Thanks in advance.
By the way: version 10 was released in July on GitHub: https://github.com/davidhalter/jedi-vim/
I also have this issue. After a recent update of vim in Fedora 30 from 2:8.1.1471-1.fc30 to 2:8.1.2102-1.fc30, jedi-vim (vim-jedi-0.9.0-1.fc30) refuses to start with the message that Edgar posted above. In vim has('python3') is true while has('python') is false. I assume this might have changed in that update (which, if true seems bad as it's likely to break a lot of stuff on what should be a maintenance update?). The vim-jedi is installed for python3.7 instead of python2.7 starting with vim-jedi-0.9.0-2.fc31, so this build also needs to be backported to Fedora 30 or the vim change needs to be rolled back. In the meantime, I was able to work around this by doing: sudo dnf --releasever=31 update vim-jedi
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '30'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 30 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.