Steve Dower <steve.do...@python.org> added the comment:
> $ v311/bin/python -m venv 311-nested > Error: [Errno 2] No such file or directory: > '/private/tmp/bpo-46028/311-nested/bin/python' I assume /private/tmp/bpo-46028/311-nested/bin/python3.11 exists though? Probably that's the issue here - I don't know how else to get the real executable *name* other than copying from argv[0], and it isn't supposed to be necessary. You also have v311/bin/python3.11, right? If you use that one, does it work? I'm trying to narrow down where the base executable is actually being launched and why. ---------- title: 3.11.0a3: sys._base_executable is wrong, breaks venv - it wasn't under 3.11.0a2 -> 3.11.0a3: under tox, sys._base_executable is wrong _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue46028> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com