Today open Python idle does not respond, and then through the online search let me in the installation directory click idle.py Pop-up error, a lot of attempts, still did not get resolved, but in the process of trying to find out what everyone said the problem is because A new. Py script conflicts with the system. py file resulting in an error.
I had this same problem today. I found another stack overflow post where someone had a tkinter.py
File in the same directory as python
, and they fixed it by removing that tkinter.py
File. When I looked in my python
directory, I realized I had created a script called random.py
and put it there. I suspect that it conflicted with the normal random module in Python. When I removed the this file, Python started working again.
So I would suggest the your main Python directory and see if there is any .py
files, could move to different places.
Yes, I also had named a program ' random.py ' lol. Something in StackOverflow clued me on So I renamed my program. By, time I ' d already lost "edit with IDLE" so I added the registry entry:hkey_classes_root\systemfileassociations\.py \shell\edit with IDLE (py3) \command Setting the value to:c:\python33\pythonw.exe c:\python33\lib\idlelib\idle.pyw-e%1 T Hen edit with Idle is back and I-ran the program from IDLE and it worked! I can ' t thank you enough for responding to my question and nailing it, I really appreciate it. Wish would let me vote up
This is the answer of some of these netizens, come from: http://stackoverflow.com/questions/15888186/ Cant-run-python-via-idle-from-explorer-2013-idles-subprocess-didnt-make-c
Also in this blog is a similar to the new script and system scripting conflict problems and then make an error problem: http://www.cnblogs.com/skyhiter/p/3381385.html
I did not solve the problem by trying all these statements, so I simply rudely uninstalled the Python compiler completely, reloading it, deleting all the scripts I wrote that could cause conflicts with the system. py file, and the problem was solved, but the various Python toolkits that were previously configured need to be configured again.
Python idle error subprocess didn ' t make connection