Hi and thanks for a cool game library. It's great to see people stepping up to work on it again too. :)
I browsed through the pyglet sourcecode to familiarize myself and have a question about the implementation of the standard run loop (https://code.google.com/p/pyglet/source/browse/pyglet/app/base.py#144). Considering the time-critical aspect of the run loop, it surprised me to see it doing variable referencing every step of the loop. A simple test with a vanilla python loop suggests that reassigning the idle() and step() methods to local variables before entering the loop (so no method lookup is required every step) gives a pure python execution speed increase of about 30%. It's not something I would mention if this wasn't in what I presume to be one of the most time-critical aspects of the code - the faster the event loop can crank the wheels the more flexibility we have (even though one may often decide to lock the frame rate). Since this is a simple and completely harmless optimization (as far as I can see) I wonder if I may have misunderstood something? . Griatch -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
