Use sys.executable instead of python?

[Jeremiah-England]

I installed this onto a venv ran into this error:

{'type': 'result', 'message': 'error', 'payload': {'msg': '"/home/jje/.pyenv/shims/python": not in executable format: file format not recognized'}, 'token': None}

But /home/jje/.pyenv/shims/python is executable, so I'm not sure what the issue is.

ls /home/jje/.pyenv/shims/python -l
# -rwxr-xr-x 1 jje jje 176 Sep  8 22:12 /home/jje/.pyenv/shims/python*

Does it need to be a proper binary?

cat /home/jje/.pyenv/shims/python
# #!/usr/bin/env bash
# set -e
# [ -n "$PYENV_DEBUG" ] && set -x
# 
# program="${0##*/}"
# 
# export PYENV_ROOT="/home/jje/.pyenv"
# exec "/usr/share/pyenv/libexec/pyenv" exec "$program" "$@"

But it's not the executable I wanted anyway. I wanted the one from the venv I was calling python -m profilia in. Changing this line got it working the way I needed in my particular case:

-    process.stdin.write(b"-file-exec-file python\n")
+    process.stdin.write(bytes(f"-file-exec-file {sys.executable}\n", encoding="utf-8"))

[itamarst]

Makes sense, I can do that.