This is what it says:
IDLE subprocess didnt make connection.
Either IDLE cant start a subprocess or personal firewall software is blocking the connection.
Ps: I already tried the firewall
This is what it says:
IDLE subprocess didnt make connection.
Either IDLE cant start a subprocess or personal firewall software is blocking the connection.
Ps: I already tried the firewall
As indicated in the comments the problem is caused because you are calling your file with the name of a library that you use, since this causes an infinite loop of import, and in this case IDLE is not able to handle it generating an error (The firewall is irrelevant, surely the developers saw that the main error is caused by the firewall, so they tell you to review it) and therefore it closes.
Due to the above and for other reasons, a caller to a file with the same name as an existing library is considered a bad practice.