On 30 Dec 2005, at 18:29, Christopher Armstrong wrote: > On 12/30/05, Robey Pointer <[EMAIL PROTECTED]> wrote: >> >> Just out of curiosity (really -- not trying to jump into the flames) >> why not just use epydoc? If it's good enough for 3rd-party python >> libraries, isn't that just a small step from being good enough for >> the builtin libraries? > > It's not really even "good enough" for a lot of my usage without some > seriously evil hacks. The fundamental design decision of epydoc to > import code, plus some other design decisions on the way it figures > types and identity seriously hinder its utility. Ever notice how > trying to document your third-party-library-using application will > *also* document that third party library, for example? Or how it'll > blow up when you're trying to document your gtk-using application on a > remote server without an X server running? Or how it just plain blows > right up with most Interface systems? etc.
Err... no, I haven't. But I may be using a more recent version than you were (I'm using 2.1). It's not perfect, and occasionally annoying, but much better than anything else I've found. Sounds like there's some political reason it's hated, but thought I would bring it up anyway. robey _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
