[issue36196] sys.executable does not return python3 executable when using uwsgi
New submission from Joris VAN HOUTVEN : when serving a Flask app with uwsgi, using `sys.executable` will provide you the path to your uwsgi executable, not your python executable. However, the docs specify that it should always return the python interpreter: https://docs.python.org/3/library/sys.html#sys.executable -- assignee: docs@python components: Documentation messages: 337190 nosy: Joris VAN HOUTVEN, docs@python priority: normal severity: normal status: open title: sys.executable does not return python3 executable when using uwsgi type: behavior ___ Python tracker <https://bugs.python.org/issue36196> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue36196] sys.executable does not return python3 executable when using uwsgi
Joris VAN HOUTVEN 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 <https://bugs.python.org/issue36196> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
