[PyOpenGL-Users] Ctype autogen summary?

[Mark H. <ma...@mi...>]

I'm trying to gather the lessons-learned so far on the great ctypes - 
PyOpengl work, especially with respect to the auto generated wrappers.  
Id like to do the same w/ another large (larger) OS project  (OpenCv).  
So far I have:
    -pulled the ctypes branch from CVS
    -Read the ooffice doc in there
    -Surfed for comments on M. Fletcher's vrplumber blog.
    -Surfed through ctypes-users mail for codegen. comments.

I'm hoping to get some pointers on the best way / lessons learned on 
autogen'ing the wrappers.  Agreed that ctypes is a better bet than SWIG 
for all the reasons listed the doc above, but for a project with >10k 
header lines Ive got to have the majority of the work autogen'd.  So 
some specific questions:

-Is the consensus that the ctypes wrapper is workable for a production 
release and if so is there some guesstimate of the road map/schedule to 
do so?
-The code generation module has been pulled from the pending Py 2.5 
inclusion of ctypes.  Looks like M. Fletcher suggested this.  Is this a 
problem, indicating no faith in the codegen?
-Which version of ctypes is to be used for PyGl?
-Are there some summary docs (even code comments) that explains the 
method / approach to making the wrappers?  The docs above do a good job 
of explaining why, but I've not found a how.

Regards,
Mark