Ned Deily added the comment:
> PYTHONPATH=/usr/local/lib/python2.7/site-packages
That looks pretty suspicious right there. It's pulling in 2.7 modules. Normally
you should never need to set PYTHONPATH in a shell initialization script, like
.profile, rarely elsewhere.
s added the comment:
:)
sure. if you want to close it - it's up to you.
if you however, want to fix it, please tell me what information do you need
me to provide.
I don't think my tone was bad/offensive. ...and it's still a bug,
regardless of my tone or anything else.
and
STINNER Victor added the comment:
Slava doesn't seem to want to provide any useful information to debug his
event, whereas Naoki asked multiple times gently. I also dislike Slava's tone
in answers, trolling Python 3 doesn't help to fix your issue...
There are millions of
STINNER Victor added the comment:
msg317525, s (sm): "Guys, (...)"
In the future please use gender-neutral words such as "folks" and "y'all"
instead of "guys". Thanks.
--
___
Python tracker
INADA Naoki added the comment:
I feel your message is just a complaint, not issue report.
You didn't report any concrete information about your environment. (e.g. How
did you install Python, which bash do you use, `env` output, `which python`
output, etc...)
Your
s added the comment:
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
STINNER Victor 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
INADA Naoki added the comment:
> 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
INADA Naoki added the comment:
> if it could be broken installation or configuration (like incorrectly set
> PYTHONHOME or any other python related environment variables), then this
> crash should be expected every time I invoke python executable and attempt
> to run
STINNER Victor added the comment:
> Maybe, your Python installation is broken, or you have wrong PYTHONPATH
> envvar.
We should maybe dump sys.path into stderr on the specific "unable to load the
file system codec" error.
--
nosy: +vstinner
INADA Naoki added the comment:
It seems not a bug of Python.
Maybe, your Python installation is broken, or you have wrong PYTHONPATH envvar.
--
nosy: +inada.naoki
___
Python tracker
New submission from s :
Fatal Python error: Py_Initialize: unable to load the file system codec
ModuleNotFoundError: No module named 'encodings'
###
Process: Python [1889]
Path:
12 matches
Mail list logo