Displayed Python Version Incorrect (alias not resolved)

[whateverforever]

Bug Report

Current Behavior

The python version displayed isn't correct. It displays the default version that came with my OS.

Expected Behavior

I expect it to show the actual python version that would be used if I were to run python xyz.py at this moment. (3.6.7 in this case).

Additional context/Screenshots

Environment

• Starship version: starship 0.26.2
• Shell type: zsh
• Shell version: zsh 5.3 (x86_64-apple-darwin18.0)
• Shell plugin manager: oh-my-zsh
• Terminal emulator: Terminal.app
• Operating system: macOS 10.14.5 (18F132)

Relevant Shell Configuration

export ZSH=/.../*snip*/.../.oh-my-zsh
plugins=(git)
source $ZSH/oh-my-zsh.sh

alias venv="source .venv/bin/activate || echo 'No venv found in dir'"

eval "$(nodenv init -)"

alias python="python3"

[ -f ~/.fzf.zsh ] && source ~/.fzf.zsh

source /.../*snip*/.../conda.sh

eval "$(starship init zsh)"

Starship Configuration

add_newline = false

[directory]
truncate_to_repo = false

[line_break]
disabled = true

Possible Solution

It has problems with the alias. If I remove it, I get the correct behaviour:

~ via 🐍 v2.7.10 ❯ python --version
Python 2.7.10
~ via 🐍 v2.7.10 ❯ 

[BasixKOR]

Aliases are not searched by utils::exec_cmd because std::process::Command::new(..) only looks for PATH variable. Personally I don't think std should resolve aliases since they are shell features, so fix for this has to be done for every shell starship supports.

[andytom]

Similar to #652, I'm going to close this since I don't think we are going to be able to resolve aliases (at least not in the near future) and we have a work around for this, #652 (comment).