[issue36196] sys.executable does not return python3 executable when using uwsgi

Change by Inada Naoki : -- resolution: fixed -> not a bug ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue36196] sys.executable does not return python3 executable when using uwsgi

Change by Inada Naoki : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[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

[issue36196] sys.executable does not return python3 executable when using uwsgi

Inada Naoki added the comment: I don't think this is a documentation bug. They insert "uwsgi" to "sys.executable" manually. https://github.com/unbit/uwsgi/blob/3149df02ed443131c54ea6afb29fcbb0ed4d1139/plugins/python/pyutils.c#L398-402 #ifdef PYTHREE PyDict_SetItemString(sys_dict,

[issue36196] sys.executable does not return python3 executable when using uwsgi

Karthikeyan Singaravelan added the comment: related uwsgi issue : https://github.com/unbit/uwsgi/issues/670 -- nosy: +xtreak ___ Python tracker ___

[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: