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 sm
Recipients methane, ned.deily, ronaldoussoren, sm, vstinner
Date 2018-05-23.22:44:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAOamOocYPvEnm7y6oyUAPSiSm8bOZVD3ZQ5bHqUkjhuLOW05mQ@mail.gmail.com>
In-reply-to <1527069566.26.0.682650639539.issue33611@psf.upfronthosting.co.za>
Content
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 python scripts.
However, it is not a case, and some of my scripts are running just fine.
I definitely have some bugs in certain scripts (they are accessing sqlite3)
and this is when I am seeing this crash of python.
...and it is python, who is crashing:
I think whatever bugs in my scripts are - it is not a valid reason for
python (which is wrapper around c code and compiles c code on the fly) to
crash.

I have reinstalled python3 on my laptop with brew and for half of the day
it was running fine...

On Wed, May 23, 2018 at 2:59 AM, STINNER Victor <report@bugs.python.org>
wrote:

>
> STINNER Victor <vstinner@redhat.com> 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
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue33611>
> _______________________________________
>
Files
File name Uploaded
image.png sm, 2018-05-23.22:44:28
History
Date User Action Args
2018-05-23 22:44:29smsetrecipients: + sm, ronaldoussoren, vstinner, ned.deily, methane
2018-05-23 22:44:29smlinkissue33611 messages
2018-05-23 22:44:29smcreate