The most boiled down example that provides Python 3 to fatally exit is: $ PYTHONHOME=/does/not/exist /usr/bin/python3
Fatal Python error: Py_Initialize: Unable to get the locale encoding ImportError: No module named encodings Aborted (core dumped) That's to be expected I suppose; it's not a bug in Python in the sense that it is purposefully aborting itself when it cannot find the encodings module during start up. I'm not sure what else Python could do in that case (and neither is upstream, hence the self-abort). It's not at all clear to me what we can do here, short of reporting the problem to VMware and having them not break the Python environment when they invoke lsb_release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/938869 Title: lsb_release crashed with SIGABRT in Py_FatalError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.2/+bug/938869/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
