[issue27054] Python installation problem: No module named 'encodings'

STINNER Victor added the comment: > I continually get the error > "Fatal Python error: Py_Initialize: unable to load the file system codec > ImportError: No module named 'encodings'" FYI I enhanced this error in Python 3.8 to "dump the Python path configuration". Example: $ PYTHONHOME=x

[issue27054] Python installation problem: No module named 'encodings'

E added the comment: python3 gave the error but I could sudo python3. To solve: export PYTHONHOME= export PYTHONPATH= -- nosy: +ergun ___ Python tracker ___

[issue27054] Python installation problem: No module named 'encodings'

Sabuj Pattanayek added the comment: I can confirm that this does happen if you don't install as admin. I confirmed that I didn't have PYTHONHOME or PYTHONPATH set and I still got a similar error (except it was for the site module) for the python 3.4.4 installer. setting

[issue27054] Python installation problem: No module named 'encodings'

Changes by Zachary Ware : -- stage: -> resolved ___ Python tracker ___ ___

[issue27054] Python installation problem: No module named 'encodings'

Steve Dower added the comment: I suspect PYTHONHOME is the problem and not the installation method. There have been thousands of (presumably successful) installations of Python 3.5, and I expect most of them are just for the current user (as that's the default). If these were all failing for

[issue27054] Python installation problem: No module named 'encodings'

Hugh C. Lauer added the comment: All, it seems that installation of Python 3.5.1 on Windows 7 must also be done as administrator. Once I did that, the installation of Python 3.5.1, numpy 1.11.0, and matplotlib 1.5.1 all went seamlessly. The only environment variable that was changed was to

[issue27054] Python installation problem: No module named 'encodings'

Hugh C. Lauer added the comment: I am back from my travels. Thanks Zachary for this. On Windows 10, no PYTHON or PYTHONHOME environment variable is set. On Windows 7, they are set. Moreover, even though I am installing Python 3.5.1, the refer to C:\Program files\Python34 ! I will continue to

[issue27054] Python installation problem: No module named 'encodings'

Hugh C. Lauer added the comment: I am back from my travels. Thanks very much, Stefan. Running as administrator did the trick for Windows 10 installations. I now have a reliable, repeatable protocol that I can give to students with little computing experience that will enable them to install

[issue27054] Python installation problem: No module named 'encodings'

Hugh C. Lauer added the comment: Thanks, I will try it when I get out of airports. Hugh Lauer On May 19, 2016 11:56 AM, Zachary Ware wrote: > > > Zachary Ware added the comment: > > Here's some pretty compelling evidence for a bad PYTHONHOME setting: > > C:\>set

[issue27054] Python installation problem: No module named 'encodings'

Changes by ppperry : -- type: -> crash ___ Python tracker ___ ___ Python-bugs-list

[issue27054] Python installation problem: No module named 'encodings'

Zachary Ware added the comment: 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 0x1db4 (most

[issue27054] Python installation problem: No module named 'encodings'

Zachary Ware added the comment: Also, I suspect your pip issue on Windows 10 is due to the fact that you need to either specify the --user flag or run pip as administrator, since your user account can't write to the global site-packages under Program Files. --

[issue27054] Python installation problem: No module named 'encodings'

STINNER Victor added the comment: To list environment variable, you can open cmd.exe and type the command "set". -- nosy: +haypo ___ Python tracker ___

[issue27054] Python installation problem: No module named 'encodings'

Zachary Ware added the comment: Hugh, could you check your environment and see if you have any PYTHON* variables set, particularly PYTHONHOME? -- ___ Python tracker

[issue27054] Python installation problem: No module named 'encodings'

Stefan Krah added the comment: I can only comment on the Windows 10 issue: I think I did the install with "Right-click -> Run as administrator" and then installed for all users. Encodings, pip and everything else works here. -- nosy: +skrah ___

[issue27054] Python installation problem: No module named 'encodings'

Hugh C. Lauer added the comment: On a hunch, I uninstalled Python 3.5.1 and reinstalled it for the current user only, to see if it would make a difference in the association of the encodings in the Registry. There was no difference. The original error message still appears. Regards, Hugh C.

[issue27054] Python installation problem: No module named 'encodings'

Hugh C. Lauer added the comment: Upon further investigation, I find lots of encodings in the folder C:\Program Files\Python35\Lib\encodings\ and lots of compiled encodings in the subfolder __pycache__ . Somehow, these are not being found by Python itself, or there is something missing from

[issue27054] Python installation problem: No module named 'encodings'

Changes by Ned Deily : -- components: +Installation, Windows nosy: +paul.moore, steve.dower, tim.golden, zach.ware versions: +Python 3.5 ___ Python tracker

[issue27054] Python installation problem: No module named 'encodings'

New submission from Hugh C. Lauer: Hello, I am a university professor who regularly teaches classes in Python programming, particular to students who are NOT computer science majors. In preparing my course materials for next fall, I have been struggling with setting up a Python 3.5.1