libc_ver() runtime error when sys.executable is empty

[d35782fe-786f-4def-aec5-222e902c1300]

BPO	46338
Nosy	@malemburg

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields: ```python assignee = None closed_at = None created_at = labels = ['3.9', 'type-crash'] title = 'libc_ver() runtime error when sys.executable is empty' updated_at = user = 'https://bugs.python.org/alliehammond' ``` bugs.python.org fields: ```python activity = actor = 'allie.hammond' assignee = 'none' closed = False closed_date = None closer = None components = [] creation = creator = 'allie.hammond' dependencies = [] files = [] hgrepos = [] issue_num = 46338 keywords = [] message_count = 3.0 messages = ['410261', '410283', '410372'] nosy_count = 2.0 nosy_names = ['lemburg', 'allie.hammond'] pr_nums = [] priority = 'normal' resolution = None stage = None status = 'open' superseder = None type = 'crash' url = 'https://bugs.python.org/issue46338' versions = ['Python 3.9'] ```

[d35782fe-786f-4def-aec5-222e902c1300]

libc_ver() in platform.py (called from platform()) causes a runtime error if sys.executable returns null. In my case, FreeRADIUS offers a module rlm_python3 which allows you to run python code from the C based FreeRADIUS server - since this module doesn't use a python binary to execute sys.executable returns null trigering this error.

[malemburg]

On 10.01.2022 23:01, Allie Hammond wrote:

libc_ver() in platform.py (called from platform()) causes a runtime error if sys.executable returns null. In my case, FreeRADIUS offers a module rlm_python3 which allows you to run python code from the C based FreeRADIUS server - since this module doesn't use a python binary to execute sys.executable returns null trigering this error.

Interesting. I guess rlm_python3 embeds Python. Is sys.executable an empty string or None ?

[d35782fe-786f-4def-aec5-222e902c1300]

Thanks for getting back to me so quickly! It's an empty string