On Mon, Sep 6, 2010 at 8:13 PM, Bruce Smith <[email protected]> wrote: > On Mon, Sep 6, 2010 at 8:15 AM, Andreas Schiefer > <[email protected]> wrote: >> >> On 6 Sep., 15:47, Tristam MacDonald <[email protected]> wrote: >> > Is anyone familiar with the process of up[grading pyglet's supported >> > OpenGL >> > version? I assume that it is a script which operates on glext.h to >> > generate >> > the supported extensions? >> >> I guess it's something like >> >> $ python tools/gengl.py gl >> >> called from within pyglet's root directory (run without the "gl" >> attribute to see all possible modules). >> But unfortunately it doesn't work on my computer (crashes while >> accessing a method of a None object). > > FYI, A few months ago Joe Wreschnig filed an issue > http://code.google.com/p/pyglet/issues/detail?id=485 > about a crash in that gengl.py script, and included a patch (but not a > traceback). There was a bit more info in the pyglet-users thread at the > time, so maybe you can figure out whether it's the same issue.
The traceback is fairly useless and probably even misleading, because the problem is not that some function got a None, but that there was a misparse some steps earlier and exactly what happens when you get a misparse is dependent on what exactly was in the header file after the misparse (for example the misparse was harmless in many other header files). The bug report goes into more detail. -- 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.
