title: Python - tkinter call to after is too slow
body: <p>I had been working on a python and tkinter solution to the code golf here: <a href="https://codegolf.stackexchange.com/questions/26824/frogger-ish-game/">https://codegolf.stackexchange.com/questions/26824/frogger-ish-game/</a></p>
  
  <p>My response is the Python 2.7 one. The thing is, when I run this code on my 2008 mac pro, everything works fine. When I run it on Win7 (I have tried this on several different machines, with the same result), the main update loop runs way too slowly. You will notice that I designed my implementation with a 1-ms internal clock:</p>
  
  <pre><code>if(self.gameover == False):
   self.root.after(1, self.process_world)
  </code></pre>
  
  <p>Empirical testing reveals that this runs much, much slower than every 1ms. Is this a well-known Windows 7-specific behavior? I have not been able to find much information about calls to after() lagging behind by this much. I understand that the call is supposed to be executed "at least" after the given amount of time, and not "at most", but I am seeing 1000 update ticks every 20 seconds instead of every 1 second, and a factor of 20 seems excessive. The timer loop that displays the game clock works perfectly well. I thought that maybe the culprit was my thread lock arrangement, but commenting that out makes no difference. This is my first time using tkinter, so I would appreciate any help and/or advice!</p>