New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IDLE 3.7.0 on Mac cannot open subprocess #78765
Comments
Every time IDLE is opened this message "IDLE's subprocess didn't make connection. Either IDLE can't start a subprocess or personal firewall software is blocking the connection" shows up. Date/Time: 2018-09-05 17:09:24.893 +0800 Sleep/Wake UUID: 30FAEA7D-EBF8-44D0-AE53-A40B0636777A Time Awake Since Boot: 87000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Termination Reason: Namespace OBJC, Code 0x1 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1: Thread 2: Thread 3: Thread 4: Thread 5:: Dispatch queue: NSCGSDisableUpdates Thread 6: Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 0 Binary Images: External Modification Summary: VM Region Summary:
REGION TYPE SIZE COUNT (non-coalesced) Model: MacBookAir7,2, BootROM MBA71.0176.B00, 2 processors, Intel Core i5, 1.8 GHz, 8 GB, SMC 2.27f2 |
Might be related to the below : open issue : https://bugs.python.org/issue14576 https://bugs.python.org/issue14576 I think from the above threads you have something in path that collides with the name of some file in Python standard library. Thanks |
Problem saved... turns out I saved a math.py file in my python location and thats what cause the crash. when i remove the math.py file or change its name, python got back to work. thanks |
I'm not to happy about the crash, the interpreter shouldn't crash like this. This may well be Tk related though. |
idlelib/run.py imports math through about 3 intermediaries. Hence it failed, and pyshell displayed the message in the .png. Both modules can raise failure messages. In bpo-25514, the run.py message was revised to point to a new section of the doc: "Startup failure". The second paragraph is "A common cause of failure is a user-written file with the same name as a standard library module, such as random.py and tkinter.py. When such a file is located in the same directory as a file that is about to be run, IDLE cannot import the stdlib file. The current fix is to rename the user file." This is what Joseph should have seen. I added a note to the issue to also fix the pyshell message to point to this section. A better but harder fix would be to temporarily remove the user directory from sys.path so that user files cannot stop run's startup. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: