powerline bash binding looking for powerline-config in the wrong directory on macos

[paul-tcell]

attempted to launch powerline after installing using these instructions.

. ./Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/powerline.sh

Got this error:

. ./Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/powerline.sh
-bash: ./Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/../../../scripts/powerline-config: No such file or directory
-bash: ./Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/../../../scripts/powerline-config: No such file or directory

seems the file is actually here: ~/Library/Python/3.7/bin/powerline-config and not in the scripts directory.

I got it working with: ln -s ~/Library/Python/3.7/bin ~/Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/../../../scripts but that seems suboptimal.

install info

Name: powerline-status
Version: 2.7
Summary: The ultimate statusline/prompt utility.
Home-page: https://github.com/powerline/powerline
Author: Kim Silkebaekken
Author-email: [email protected]
License: MIT
Location: /Users/me/Library/Python/3.7/lib/python/site-packages
Requires: 
Required-by: 

[erichlf]

This looks related to #850

[erichlf]

Checkout this answer:
https://askubuntu.com/a/953875

[ZyX-I]

Directory $HOME/Library/Python/3.7/bin is supposed to be in your $PATH, you don’t and must not link it where you linked it as that directory is supposed to be maintained by your package manager. If it was powerline would not try to use fallbacks leading to attempting to use powerline-config from the directory you see it attempt to use.

[c5f]

@ZyX-I why was this issue closed? @paul-tcell's symlink was an attempt at a workaround, not the cause of the problem.

I got it working with: ln -s ~/Library/Python/3.7/bin ~/Library/Python/3.7/lib/python/site-packages/powerline/bindings/bash/../../../scripts but that seems suboptimal.

[c5f]

this test seems to be failing even though $PATH is correct in my environment

https://github.com/powerline/powerline/blob/3b85be683658685d89ab87ed83a48d9a918bc4ff/powerline/bindings/bash/powerline.sh#L140

POWERLINE_CONFIG_COMMAND was actually exported in my shell session -- i don't know if this was caused by trying to source powerline.sh before starting the powerline-daemon, or more likely by trying to source powerline.sh before amending my PATH to contain my pip --user directory; but forcing it to powerline-command as below solved the issue _(so did restarting all of my sessions)_.

https://github.com/powerline/powerline/blob/3b85be683658685d89ab87ed83a48d9a918bc4ff/powerline/bindings/bash/powerline.sh#L142

this seems to be a commonly-asked question early this year, and i'm curious if there is some setup procedure causing this to break on new macos installs.