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 eryksun
Recipients Ray Donnelly, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-12-30.20:10:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514664613.26.0.213398074469.issue32457@psf.upfronthosting.co.za>
In-reply-to
Content
Here's a way to trigger this error that's unrelated to the PATH environment variable:

    >>> subprocess.call('python', executable=r'C:\Program Files\Python36\.\python.exe')
    Fatal Python error: Py_Initialize: unable to load the file system codec
    ModuleNotFoundError: No module named 'encodings'
    [...]

Apparently Windows doesn't normalize the process image path if it uses only backslash as the path separator. It normalizes it if at least one backslash is replaced with a slash.
History
Date User Action Args
2017-12-30 20:10:13eryksunsetrecipients: + eryksun, paul.moore, tim.golden, zach.ware, steve.dower, Ray Donnelly
2017-12-30 20:10:13eryksunsetmessageid: <1514664613.26.0.213398074469.issue32457@psf.upfronthosting.co.za>
2017-12-30 20:10:13eryksunlinkissue32457 messages
2017-12-30 20:10:13eryksuncreate