Be explicit about python absolute path

One some distros `virtualenv` still uses a Python 2 executable, I always set `python` to point to Python 3 so be explicit about getting the absolute path to `python` when creating a `virtualenv` with `autoenv add=py`.
Fix autoenv add=py .enter when run in subdirectory
2022-03-22 13:29:33 +00:00 · 2022-03-22 13:29:33 +00:00
1 changed files with 2 additions and 2 deletions
--- a/autoenv/autoenv.zsh
+++ b/autoenv/autoenv.zsh
@ -97,8 +97,8 @@ commands:
        echo '.enter or .exit not found'; return 1
      fi
      _autoenv_exit $PWD
-      virtualenv .local
-      echo 'source .local/bin/activate' >> .enter
+      virtualenv -p `command -v python` .local
+      echo 'source ${0:a:h}/.local/bin/activate' >> .enter
      echo 'deactivate' >> .exit
      _autoenv_authorized $PWD/.enter yes
      _autoenv_authorized $PWD/.exit yes
Author	SHA1	Message	Date
Kenneth Benzie (Benie)	b349befbf4	Be explicit about `python` absolute path One some distros `virtualenv` still uses a Python 2 executable, I always set `python` to point to Python 3 so be explicit about getting the absolute path to `python` when creating a `virtualenv` with `autoenv add=py`.	2022-03-22 13:29:33 +00:00
Kenneth Benzie (Benie)	74f2dd7dae	Fix `autoenv add=py` .enter when run in subdirectory	2022-03-22 13:29:33 +00:00