This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author methane
Recipients methane, ned.deily, ronaldoussoren, sm, vstinner
Date 2018-05-24.01:15:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1527124539.51.0.682650639539.issue33611@psf.upfronthosting.co.za>
In-reply-to
Content
> We should maybe dump sys.path into stderr on the specific "unable to load the file system codec" error.

In addition to sys.path, I think "What's current python home (prefix and exec-prefix), and where it come from" is very useful.

I recently fixed Vim's bug. https://github.com/vim/vim/pull/2787

Vim called Py_SetPythonHome with path of Python when vim is compiled.  After reinstalling Python to another directory, vim fails with "no module named encoding" error everytime.  This suffered many homebrew users because homebrew use different directory to install Python every revisions.

Python home will be come from different locations:

* Calculated from Python executable path
* Embedded in Python static/dynamic library
* PYTHONHOME environment variable
* Py_SetPythonHome()
History
Date User Action Args
2018-05-24 01:15:39methanesetrecipients: + methane, ronaldoussoren, vstinner, ned.deily, sm
2018-05-24 01:15:39methanesetmessageid: <1527124539.51.0.682650639539.issue33611@psf.upfronthosting.co.za>
2018-05-24 01:15:39methanelinkissue33611 messages
2018-05-24 01:15:38methanecreate