Issue 17658: pythonw.exe crashes on opening IDLE (original) (raw)

Created on 2013-04-08 03:51 by Acebulf, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
WER1B0A.tmp.WERInternalMetadata.xml Acebulf,2013-04-08 03:51
WER5D77.tmp.appcompat.txt Acebulf,2013-04-08 03:52
WER5EA0.tmp.mdmp Acebulf,2013-04-08 03:52
Messages (8)
msg186268 - (view) Author: Patrick Poitras (Acebulf) Date: 2013-04-08 03:51
I just installed Python 3.3.1, and tried to open IDLE, which failed to come up, giving only the classic pythonw.exe has stopped responding. Will post dumps.
msg186269 - (view) Author: Patrick Poitras (Acebulf) Date: 2013-04-08 04:02
So I tried to open Python33\python.exe and it's trying to load codecs from Python 2.7 which I think has to be the cause of the problem. When it raises CodecRegistryError, the 2.7 syntax is wrong for 3.3 and causes a SyntaxError. Fatal Python error: Py_Initialize: unable to load system file codec File "C:\Python27\Lib\encodings\__init__.py", line 123 raise CodecRegistryError,\ ^ SyntaxError: invalid syntax
msg186299 - (view) Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) Date: 2013-04-08 13:06
Hum, do you have any environment variable that refer to Python27? In a terminal window (cmd.exe), try the following command: set | findstr /i python
msg186306 - (view) Author: Patrick Poitras (Acebulf) Date: 2013-04-08 15:18
It returns this: C:\Users\Acebulf>set | findstr /i python Path=C:\Python27\Lib\site-packages\PyQt4;C:\Program Files (x86)\NVIDIA Corporati on\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windo ws\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files\Microsoft SQL Server\1 10\Tools\Binn\;C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\;C:\Program Files\In tel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Python27\ PYTHONPATH=C:\Python27\Lib;C:\Python27\DLLs;C:\Python27\Lib\lib-tk;
msg186312 - (view) Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * (Python committer) Date: 2013-04-08 15:39
Please remove the PYTHONPATH environment variable. I don't know how it came here, but it's certainly not needed: these directories are computed at runtime when the python27 interpreter starts; it can only do harm when another interpreter is installed.
msg189722 - (view) Author: Roger Serwy (roger.serwy) * (Python committer) Date: 2013-05-21 03:42
Patrick, does removing PYTHONPATH from your environment variables fix this problem?
msg190046 - (view) Author: Roger Serwy (roger.serwy) * (Python committer) Date: 2013-05-26 01:08
I'm closing this issue due since it's root problem is a misconfigured environment variable.
msg190047 - (view) Author: Roger Serwy (roger.serwy) * (Python committer) Date: 2013-05-26 01:10
s/it's/its
History
Date User Action Args
2022-04-11 14:57:44 admin set github: 61858
2013-05-26 01:10:15 roger.serwy set messages: +
2013-05-26 01:08:31 roger.serwy set status: pending -> closedresolution: works for memessages: +
2013-05-21 03:42:15 roger.serwy set status: open -> pendingnosy: + roger.serwymessages: +
2013-04-08 15:39:16 amaury.forgeotdarc set messages: +
2013-04-08 15🔞26 Acebulf set messages: +
2013-04-08 13:06:45 amaury.forgeotdarc set nosy: + amaury.forgeotdarcmessages: +
2013-04-08 04:02:30 Acebulf set messages: +
2013-04-08 03:52:38 Acebulf set files: + WER5EA0.tmp.mdmp
2013-04-08 03:52:18 Acebulf set files: + WER5D77.tmp.appcompat.txt
2013-04-08 03:51:55 Acebulf create