The problem is the text output not the debugger.
I just tried it on my Q6600 (3GHz overclocked) System and my numbers are even worse.
But its easy to see that they are going down the more output text is added.
I tried to run it with
1000 iterations => 7,8 sec
2000 iterations => 28,5 sec
3000 iterations => 70 sec
I did some low level TK stuff in the past and i know that the TkText Widget is keeping the text in a BTree structure. Appending text a character a time is one of the worst ways to do but this seems to be what IDLE is doing. The normal way is to catch more data and append a larger chunk of text.
Amazingly if you write print 'x\n' the output is much faster. 3000 iterations in 7 seconds and your 10000 in 19 sec.
So the problem is definitely with appending single chars to existing lines. The IDLE programmer didn't know how TkText works.
So the advise is to add more newlines into your text or output larger chunks and not only a single 'x' character.