Ben, Here is another item for your list (copying part of my reply in another thread where someone hit this bug just now):
http://code.google.com/p/pyglet/issues/detail?id=407 (pyglet issue 407), whose comments say it's fixed in trunk (r2327) but not in the 1.1-maintenance branch (and not in any release). I think that's the pyglet bug most often encountered in the last pyweek. - Bruce --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
