[PyOpenGL-Users] Should PyOpenGL's usage of SWIG be rethinked?

[Andy Sy <an...@ne...>]

I've noticed that PyOpenGL has lagged behind the latest
OpenGL versions for sometime now.  Is the complexity of
SWIG to blame for this?

Would a different approach, say ctypes
(http://starship.python.net/crew/theller/ctypes/) or use
of the Python C API actually make things easier?

I took a look at Ruby's OpenGL interface (
http://www2.giganet.net/~yoshi/ ), and
interestingly, there's not much acrobatics that
need to be done.  There's a single 4,252 line C source
with a seemingly very simple way of wrapping C
OpenGL calls and that's it. (Could Ruby's C interface
really be that clean?!?)