FS#48358 - [powerline] zsh plugin doesn't work in virtualenv
Attached to Project:
Community Packages
Opened by Ng Oon-Ee (ngoonee) - Saturday, 27 February 2016, 16:27 GMT
Last edited by Jiachen Yang (farseerfc) - Sunday, 28 February 2016, 16:01 GMT
Opened by Ng Oon-Ee (ngoonee) - Saturday, 27 February 2016, 16:27 GMT
Last edited by Jiachen Yang (farseerfc) - Sunday, 28 February 2016, 16:01 GMT
|
Details
Description:
Since powerline was moved from the AUR the zsh plugin is broken when in a virtualenv. Source of the issue is that the /usr/bin/powerline-{config,render} scripts use /usr/bin/env python rather than /usr/bin/python{,2} as was the case with the AUR package. This means when in a virtualenv that it won't find powerline, as that module is not installed in any of my virtualenvs (why should it be, after all?). I notice that the previous AUR package simply ran install while the current community package runs build, not sure what difference that makes. All I know is that the change above fixes behaviour in virtualenvs for me. Additional info: * package version(s) powerline-2.3-5 Error Message (for google): Traceback (most recent call last): File "/usr/bin/powerline-config", line 11, in <module> from powerline.shell import ShellPowerline ImportError: No module named powerline.shell File "/usr/bin/powerline-render", line 13, in <module> from powerline.shell import ShellPowerline ImportError: No module named powerline.shell Steps to reproduce: Just install powerline, modify zshrc to use it, and workon any virtualenv (that doesn't include system packages). |
This task depends upon
Closed by Jiachen Yang (farseerfc)
Sunday, 28 February 2016, 16:01 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in powerline-2.3-6
Sunday, 28 February 2016, 16:01 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in powerline-2.3-6