I have been using "standard" Pydoc (actually slightly hacked) to document PyOpenGL outside the man pages, but PyOpenGL is almost entirely composed of things that don't work well with the standard tools; functions are actually class instances that check for availability before attempting to call, "functions" are defined in "raw" modules then imported into their final locations, lots of the code is replaced by accelerator modules, etceteras.

Some time ago I started writing a rather stupid little replacement tool that is PyOpenGL specific and can be (easily) taught how to handle new object-types.  The biggest downside of it is that it no longer processes the docstrings to extract information (intra-module links, emphasis, http links, etc), but it does make the "pydoc" for PyOpenGL a little more useful, particularly modules such as arrays.VBO.