Bug 2311031 - vim-jedi looks non-working on Fedora 41
Summary: vim-jedi looks non-working on Fedora 41
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: vim-jedi
Version: 41
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Petr Hracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2311860
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-10 06:06 UTC by Pavel Raiskup
Modified: 2025-12-16 17:10 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-16 17:10:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pavel Raiskup 2024-09-10 06:06:29 UTC
Anytime I try to open a Python file, I see this error:

Error detected while processing BufRead Autocommands for "*"..script /usr/share/vim/vim91/scripts.vim[27]..function dist#script#DetectFiletype[4]..<SNR>11_DetectFromHashBang[37]..FileType Autocommands for "*"..function <SNR>12_LoadFTPlugin[18]..script /usr/share/vim/vimfiles/ftplugin/python/jedi.vim[1]../usr/share/vim/vimfiles/autoload/jedi.vim[261]..function jedi#init_python[13]..BufRead Autocommands for "*"..script /usr/share/vim/vim91/scripts.vim[27]..function dist#scr
ipt#DetectFiletype[4]..<SNR>11_DetectFromHashBang[37]..FileType Autocommands for "*"..function <SNR>12_LoadFTPlugin[18]..script /usr/share/vim/vimfiles/ftplugin/python/jedi.vim[1]../usr/share/vim/vimfiles/autoload/jedi.vim[261]..function jedi#init_python[11]..<SNR>41_display_exception:
line   19:
Error: jedi-vim failed to initialize Python: jedi-vim requires Vim with support for Python 3. (in BufRead Autocommands for "*"..script /usr/share/vim/vim91/scripts.vim[27]..function dist#script#DetectFiletype[4]..<SNR>11_DetectFromHashBang[37]..FileType Autocommands for "*"..function <SNR>12_LoadFTPlugin[18]..script /usr/share/vim/vimfiles/ftplugin/python/jedi.vim[1]../usr/share/vim/vimfiles/autoload/jedi.vim[261]..function jedi#init_python[4]..<SNR>41_init_python, line 4
)
Error detected while processing BufRead Autocommands for "*"..script /usr/share/vim/vim91/scripts.vim[27]..function dist#script#DetectFiletype[4]..<SNR>11_DetectFromHashBang[37]..FileType Autocommands for "*"..function <SNR>12_LoadFTPlugin[18]..script /usr/share/vim/vimfiles/ftplugin/python/jedi.vim:
line   40:
E117: Unknown function: jedi#configure_call_signatures


Reproducible: Always

Comment 1 Adam Williamson 2025-12-02 01:16:55 UTC
This message is a reminder that Fedora Linux 41 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15.
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
'version' of '41'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 41 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 Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Samyak Jain (RedHat) 2025-12-16 17:10:13 UTC
Fedora Linux 41 entered end-of-life (EOL) status on 2025-12-15.

Fedora Linux 41 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 Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.