Time to start testing for PyOpenGL 3.0.1
Written by
on
in
Snaking.
PyOpenGL 3.0.1 is pretty much finished AFAICS. The biggest visible change is support for the OpenGL_accelerate module (written in Cython) which provides a noticeable speedup for my applications. However, the fact that the code is C (once generated) means that bugs are going to be introduced (including possible segfaults).
There are also a number of bug-fixes in the code since the 3.0.0 release. So, if you'd like to help out, branch the current head, compile the OpenGL_accelerate module and test (or test without the accelerate module, if you'd like to help with testing that version as well). Particularly need testing by people with weird and exotic platforms, like Win32 or OSX. 32-bit Linux could also use testing.
Comments
Comments are closed.
Pingbacks
Pingbacks are closed.
Mike C. Fletcher, the VRPlumber, is a philosopher of design turned computer programmer based in Toronto, Canada. He works primarily in the Python programming language, and maintains a large number of Open Source software packages. You can reach him at: mcfletch@vrplumber.com.
Stu on 05/14/2009 6:23 p.m. #
It occurs to me there are 3 main python opengl bindings -
PyOpenGL
Pyglet
Blender.BGL
I wonder how compatible these are... could we run the tests for PyOpenGL on the others...?
If there are incompatibilities, could they be worked out ?
Mike C. Fletcher on 05/15/2009 10:52 a.m. #
Pyglet and PyOpenGL's OpenGL/raw are likely close enough to compatible as to let you run most Pyglet code across them. Pyglet doesn't try to provide a PyOpenGL (traditional) API. Don't know how Blender.BGL works.