a517c4c5d0
Because 'bin/dotbot' is a hybrid sh/Python script that finds the appropriate Python binary and then runs, the test code should not invoke it as an sh script when sh does not source the pyenv initialization script. The fix implemented in this patch is to directly run 'bin/dotbot' as a Python script using 'python', which when called from bash, will run with the correct Python version (because bash is set up to source the pyenv initialization script).
62 lines
1.1 KiB
Bash
62 lines
1.1 KiB
Bash
test_description='can find python executable with different names'
|
|
. '../test-lib.bash'
|
|
|
|
if ${USE_VAGRANT}; then
|
|
DOTBOT_EXEC="/dotbot/bin/dotbot" # revert to calling it as a shell script
|
|
fi
|
|
|
|
# the test machine needs to have a binary named `python`
|
|
test_expect_success 'setup' '
|
|
mkdir ~/tmp_bin &&
|
|
(
|
|
IFS=:
|
|
for p in $PATH; do
|
|
find $p -maxdepth 1 -mindepth 1 -exec sh -c \
|
|
'"'"'ln -sf {} $HOME/tmp_bin/$(basename {})'"'"' \;
|
|
done
|
|
) &&
|
|
rm -f ~/tmp_bin/python &&
|
|
rm -f ~/tmp_bin/python2 &&
|
|
rm -f ~/tmp_bin/python3
|
|
'
|
|
|
|
test_expect_failure 'run' '
|
|
PATH="$HOME/tmp_bin" run_dotbot <<EOF
|
|
[]
|
|
EOF
|
|
'
|
|
|
|
test_expect_success 'setup 2' '
|
|
touch ~/tmp_bin/python &&
|
|
chmod +x ~/tmp_bin/python &&
|
|
cat >> ~/tmp_bin/python <<EOF
|
|
#!$HOME/tmp_bin/bash
|
|
exec $(which python)
|
|
EOF
|
|
'
|
|
|
|
test_expect_success 'run 2' '
|
|
PATH="$HOME/tmp_bin" run_dotbot <<EOF
|
|
[]
|
|
EOF
|
|
'
|
|
|
|
test_expect_success 'setup 3' '
|
|
mv ~/tmp_bin/python ~/tmp_bin/python2
|
|
'
|
|
|
|
test_expect_success 'run 3' '
|
|
PATH="$HOME/tmp_bin" run_dotbot <<EOF
|
|
[]
|
|
EOF
|
|
'
|
|
|
|
test_expect_success 'setup 4' '
|
|
mv ~/tmp_bin/python2 ~/tmp_bin/python3
|
|
'
|
|
|
|
test_expect_success 'run 4' '
|
|
PATH="$HOME/tmp_bin" run_dotbot <<EOF
|
|
[]
|
|
EOF
|
|
'
|