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 zach.ware
Recipients lauer@wpi.edu, paul.moore, skrah, steve.dower, tim.golden, vstinner, zach.ware
Date 2016-05-19.15:56:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1463673364.87.0.464630969517.issue27054@psf.upfronthosting.co.za>
In-reply-to
Content
Here's some pretty compelling evidence for a bad PYTHONHOME setting:

C:\>set PYTHONHOME=C:\path\not\here

C:\>py -3.5
Fatal Python error: Py_Initialize: unable to load the file system codec
ImportError: No module named 'encodings'

Current thread 0x00001db4 (most recent call first):

C:\>set PYTHONHOME=C:\Python27\

C:\>py -3.5
Fatal Python error: Py_Initialize: unable to load the file system codec
  File "C:\Python27\\lib\encodings\__init__.py", line 123
    raise CodecRegistryError,\
                            ^
SyntaxError: invalid syntax

Current thread 0x00000664 (most recent call first):

C:\>set PYTHONHOME=

C:\>py -3.5
Python 3.5.1 (v3.5.1:37a07cee5969, Dec  6 2015, 01:54:25) [MSC v.1900 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>>
History
Date User Action Args
2016-05-19 15:56:04zach.waresetrecipients: + zach.ware, paul.moore, vstinner, tim.golden, skrah, steve.dower, lauer@wpi.edu
2016-05-19 15:56:04zach.waresetmessageid: <1463673364.87.0.464630969517.issue27054@psf.upfronthosting.co.za>
2016-05-19 15:56:04zach.warelinkissue27054 messages
2016-05-19 15:56:04zach.warecreate