Aug-22-2018, 03:14 PM
(This post was last modified: Aug-22-2018, 03:17 PM by FatalPythonError.)
(Aug-22-2018, 03:02 PM)metulburr Wrote: This is most likely a dead end, but i will ask. Have you created a .pth file at all on this system? This should not effect the standard lib io module if there was another io file elsewhere because 1) the .pth filepaths are search after the standard library ones, and 2) an uninstall should remove it from site-packages anyways. Unless you did something weird. But if you never did create a .pth file and have no idea what that is , then just ignore this post.No never did anything like that. I did have Anaconda and Spyder installed before(which I uninstalled) which had Python 3.6.5 and the single system wide version on Windows was 3.6.3. This is only thing I can think of which might have caused this breakdown. Never bothered with anything
.pth
related.(Aug-22-2018, 03:05 PM)metulburr Wrote:Quote:1. Why is this '-E' thing being installed by default? Is there any way to remove it? I just want it like before i.e take me to IDLE when I type 'python' instead of 'python -E'. Only want to keep one consistent python version installed on system.
the E argument does this
Quote: -E Ignore environment variables like PYTHONPATH and PYTHONHOME thatYou shouldnt have to do that to run a fresh python isntall. Continuing without fixing this first will cause future headaches.
modify the behavior of the interpreter.
Does that mean my PYTHONPATH and PYTHONHOME are broken for some reason? Any idead how to fix that?