Ah, I misunderstood the functionality of the epydoc extension. Events! http://pyglet.org/doc/api/pyglet.window.Window-class.html
On Apr 11, 4:01 pm, Nathan <[email protected]> wrote: > On Wed, Apr 11, 2012 at 10:01 AM, Steve <[email protected]> wrote: > >> Treatment of events will require a small extension. An extension is > >> slightly neater than an entire fork which is what epydoc needed. :) > > > Why? You can just create arbitrary reStructuredText pages. > > I'm sure he doesn't want to hand-craft the API documentation for each > change to the code. He'll want to generate it, which means 'pyglet > events' will need an extension so they can be treated differently than > regular methods. > > ~ Nathan -- 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.
