[Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows (original) (raw)
anatoly techtonik techtonik at gmail.com
Wed Oct 31 18:21:24 CET 2012
- Previous message: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows
- Next message: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Oct 23, 2012 at 2:39 AM, Stephen J. Turnbull < turnbull at sk.tsukuba.ac.jp> wrote:
So it shuts down abnormally. That's what an abort means, in programming as in rocket launches. Users should be scared if this happens; somebody really screwed up. (Unless it's themselves, and then they only have themselves to blame.) > The error message could be > improved though. Right now I get: > > E:>python > Fatal Python error: PyInitialize: unable to load the file system codec > ImportError: No module named 'encodings' > > This could be improved to: > > Fatal Python error: PyInitialize: unable to find module named 'encodings' > in 'C:' That may be an improvement. But in that case it might be worth explaining where "C:" came from (in this case PYTHONHOME, I guess?)
Good idea.
Fatal Python error: Py_Initialize: unable to find module named 'encodings' in PYTHONHOME ('C:') -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20121031/4bdc9678/attachment.html>
- Previous message: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows
- Next message: [Python-Dev] Segmentaion fault with wrongly set PYTHONPATH on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]