我的就可以啊。
好像是哪一个端口被占用了啊。
看看
IDLE can't bind TCP/IP port 8833...
A common problem that occurs when using IDLE is this:First it gets "stuck"—i.e. non-responsive, requiring you to "Force Quit" the application
Then, when you try to restart it, you get this error message (or something similar): IDLE can't bind TCP/IP port 8833, which is necessary to communicate, etc. etc. (see picture below)
The way to fix this problem, as simplistic as it sounds, is usually to wait about 30 seconds, and try again.What is happening is that thatthe different parts of IDLE communicate with each other using something called TCP/IP—the same method of communication that is used on the Internet. This happens even when you are running all the parts of IDLE on the same machine.
When you force quit IDLE, these connections are severed—and there is a rule in the TCP part of TCP/IP that you have to wait appoximately 30 seconds before you can reuse the same "port number".
If waiting 30 seconds doesn't work, it may be because you have another instance of IDLE that is still running on the same machine, and stronger measures may be needed to solve the problem.
实在不行的话,重装Python环境
重装windows系统