Re: [Epydoc-devel] epydoc 2.1 can't handle PyGetSetDefs?
Brought to you by:
edloper
From: Barry W. <ba...@py...> - 2006-07-11 16:10:39
|
On Jul 11, 2006, at 8:16 AM, Daniele Varrazzo wrote: >> I've had a few minor problems along the way, and some ideas that I'll >> share later, but I wanted to ask a quick question for my current >> blocker. It appears that epydoc cannot handle class attributes >> defined in extension modules with PyGetSetDef. > > Hello Barry, > > i hammered together a patch: with it getset_descriptors appear like > properties. > > The patch id is 1520501 and it can be downloaded from > http://sourceforge.net/tracker/index.php? > func=detail&aid=1520501&group_id=32455&atid=405620 > > Epydoc 3.0 HEAD behaves nicer with getset_descriptors, but it > erroneously files it as a class variable (the same thing happened in > the making of the 2.1 patch). I will fix it too. Thanks Daniele, I tested the patch and it appears to work well. I had to make one other small change to objdoc.py for what I think is an unrelated problem (although I'm not sure because I didn't see the bug before). Without this, I'd get a traceback from add_one() because one of my getset descriptors did not have its parent ID in self.data. I don't quite understand why that might be though, except that perhaps it's because the parent is a base class defined in the extension module. In any event, with this patch, I can generate all my docs and even the traceback'ing getset descriptor gets documented correctly. Cheers, -Barry |