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.

classification
Title: Fatal Python error
Type: Stage: resolved
Components: Versions:
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: abdallahadham, methane, zach.ware
Priority: normal Keywords:

Created on 2019-01-24 17:29 by abdallahadham, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (4)
msg334308 - (view) Author: Abdallah (abdallahadham) Date: 2019-01-24 17:29
,He,
i am having this problem for about 2 weeks , I can't do anything , so please give me some instructions so i can solve .it

Fatal Python error: initfsencoding: unable to load the file system codec
ModuleNotFoundError: No module named 'encodings'

:Current thread 0x00003c7c (most recent call first

Process finished with exit code -1073740791 (0xC0000409)

 Thanks
msg334311 - (view) Author: Zachary Ware (zach.ware) * (Python committer) Date: 2019-01-24 17:37
Hi Abdallah,

This tracker is for reporting bugs in the CPython interpreter or standard library, not for general help; as such I'm closing this issue.  For help, it's better to ask on the main python mailing list (python-list@python.org), in the #python IRC channel on Freenode, or in the #general/help stream on python.zulipchat.com.

That said, this is usually caused by having the PYTHONHOME or PYTHONPATH environment variables set incorrectly; try unsetting *all* environment variables that start with PYTHON and see if that helps.

If that doesn't fix it, ask for help on one of the forums I mentioned above, but include more details about what you're actually doing and what's not working so that folks can help you effectively.  Also include your operating system, OS version, Python version, and anything else that you feel might be relevant.
msg334326 - (view) Author: Abdallah (abdallahadham) Date: 2019-01-24 23:50
Thank you alot

On Thu, 24 Jan 2019, 19:37 Zachary Ware <report@bugs.python.org wrote:

>
> Zachary Ware <zachary.ware@gmail.com> added the comment:
>
> Hi Abdallah,
>
> This tracker is for reporting bugs in the CPython interpreter or standard
> library, not for general help; as such I'm closing this issue.  For help,
> it's better to ask on the main python mailing list (python-list@python.org),
> in the #python IRC channel on Freenode, or in the #general/help stream on
> python.zulipchat.com.
>
> That said, this is usually caused by having the PYTHONHOME or PYTHONPATH
> environment variables set incorrectly; try unsetting *all* environment
> variables that start with PYTHON and see if that helps.
>
> If that doesn't fix it, ask for help on one of the forums I mentioned
> above, but include more details about what you're actually doing and what's
> not working so that folks can help you effectively.  Also include your
> operating system, OS version, Python version, and anything else that you
> feel might be relevant.
>
> ----------
> nosy: +zach.ware
> resolution:  -> not a bug
> stage:  -> resolved
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue35819>
> _______________________________________
>
msg336994 - (view) Author: Inada Naoki (methane) * (Python committer) Date: 2019-03-02 06:12
By the way, do you remember why you set PYTHONHOME?
I afraid that someone recommends such bad practice on Web and this issue is spreading.

Beginner ~ average Python user must not try PYTHONHOME.
History
Date User Action Args
2022-04-11 14:59:10adminsetgithub: 80000
2019-03-02 06:12:53methanesetnosy: + methane
messages: + msg336994
2019-01-24 23:50:34abdallahadhamsetmessages: + msg334326
2019-01-24 17:37:49zach.waresetstatus: open -> closed

nosy: + zach.ware
messages: + msg334311

resolution: not a bug
stage: resolved
2019-01-24 17:29:50abdallahadhamcreate