
March 6, 2019
3:47 a.m.
Joris VAN HOUTVEN <joris.vanhoutven@uhasselt.be> added the comment: OK, so it is indeed uwsgi interfering with the sys.executable value. In the github pst Inada Naoki refers to: "uwsgi is your current python interpreter, as it links the libpython.so. Getting sys.executable is not possibile as there is no binary path hard-encoded in library by itself" So I suppose this issue can be closed here. I will comment on the uwsgi github. ---------- _______________________________________ Python tracker <report@bugs.python.org> <https://bugs.python.org/issue36196> _______________________________________