Hide Forgot
Description of problem: When I start vim (or gvim), I get the following error message on the terminal: $ vi /usr/share/vim/vimfiles/plugin/powerline.vim Traceback (most recent call last): File "<string>", line 4, in <module> ImportError: No module named 'powerline' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<string>", line 9, in <module> ImportError: No module named 'powerline' An error occurred while importing powerline module. This could be caused by invalid sys.path setting, or by an incompatible Python version (powerline requires Python 2.6, 2.7 or 3.2 and later to work). Please consult the troubleshooting section in the documentation for possible solutions. Unable to import powerline, is it installed? Press ENTER or type command to continue Version-Release number of selected component (if applicable): powerline-2.2-2.fc22.x86_64 vim-powerline-2.2-2.fc22.noarch How reproducible: Always Steps to Reproduce: 1. Just run vim in terminal 2. message appears on terminal 3. press ENTER and everything looks fine. Powerline has been imported as usual. Additional info: I didn't have the problem with the previous release of powerline 2.1-1. The message "Unable to import powerline, is it installed?" comes from file /usr/share/vim/vimfiles/plugin/powerline.vim (line 112) in vim-powerline package.
powerline-2.3-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-9d6632c476
powerline-2.3-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-30494f69c4
powerline-2.3-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update powerline' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-9d6632c476
powerline-2.3-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update powerline' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-30494f69c4
powerline-2.3-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
powerline-2.3-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Description of problem: vim-powerline, when installed reports errors in terminal when launching vim or gvim Version-Release number of selected component (if applicable): vim-powerline-2.7-1.fc29.noarch How reproducible: every time Steps to Reproduce: 1. install vim-powerline plugin via dnf 2. run vim or gvim from a terminal 3. ... 4. Profit? Actual results: 12:27 PM {1038} localhost: ~>$ gvim Traceback (most recent call last): File "<string>", line 9, in <module> ImportError: No module named powerline.vim An error occurred while importing powerline module. This could be caused by invalid sys.path setting, or by an incompatible Python version (powerline requires Python 2.6, 2.7 or 3.2 and later to work). Please consult the troubleshooting section in the documentation for possible solutions. Unable to import powerline, is it installed? Expected results: 12:27 PM {1038} localhost: ~>$ gvim 12:27 PM {1039} localhost: ~>$ Additional info: removing vim-powerline makes the problem go away, so I am certain it is not being caused by anything in my personal ~/.vim/* or ~/.g?vimrc I noticed a bug filed back in fedora 22 was marked as fixed ( bug 1272103 ), but apparently it is still present in F29, so I am re-opening this bug rather than filing a new one
Further testing has proven I had plugin conflicts with TWO separate plugins in vim -- older versions of both pandoc.vim and vdebug.vim which upon removal cleaned up the error report -- sorry for the false positive.