Guys,
First of all - thank you for accepting it and trying to fix it.
I lost two days attempting to resurrect python3 on my laptop and ended up
with uninstalling it and restoring python 2.7.10.
I agree (and I think it is separate and well known python's problem) -
there are several tools/techniques  installing python and paths ARE
different between OS. this is what I was observing today comparing Mac OS
and CentOS 7.
and as it seems to me this "complaint" about "encoding" is exactly about it
- as it is such a directory on Linux and there is no such directory on Mac.
In any case, whatever way it all this handled, it should not cause python
to die and more importantly - something is making changes in configuration
of python on the system and user is unable to use python after this error
AT ALL.
I had to reinstall it completely several times yesterday and today because
of this.
About shebangs.
yes, I do have different ones (and I suspect many of us do, as python's
very interesting feature of incompatibility between major versions)
And after all these my attempts to fix python 3 on my laptop I ended up
with total mess on the system - none of the pythons were working.
So, I said - you know... I'll wait for python 3 be more mature...
Perhaps that is the reason Apple is not installing more resent version and
keeps 2.7.10? :)

Regards,
Slava

On Wed, May 23, 2018 at 6:20 PM, STINNER Victor <report@bugs.python.org>
wrote:

>
> STINNER Victor <vstinner@redhat.com> added the comment:
>
> I completed the _PyCoreConfig structure to add home,
> module_search_path_env, and many other options. It might help to guess how
> the final configuration has been computed. I also reworked the code to
> clarify when and how sys.path is computed. sys.path value (not the actual
> sys.path Python list) is now computed earlier.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue33611>
> _______________________________________
>