I've been getting this issue regualrly on all linux installations while playing with pyglet. I see it's fixed now in the repository but it's not in pypi yet. I have a few miscellanous questions:
presumably it will get a pypi update for this at some point The issue has been present since 2008, the first commit, how come it's only surfaced now? Is it the result of glx or other changes? I ask these questions as I am thinking of using pyglet for a comercial project for a client, and of course I am a little aprehensive in case i run into trouble with pyglet. However, pyglet seems to be exactly what I need, unless I waste effort going the DIY route. I saw some rumors of pyglets demise, but perhaps the project just needs more contributors. Thanks, Jason -- 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 pyglet-users+unsubscr...@googlegroups.com. To post to this group, send email to pyglet-users@googlegroups.com. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
