Re: [Epydoc-devel] errors in 3.0alpha

[Edward L. <ed...@gr...>]

Stefan Seefeld wrote:

> I had a look at that but wasn't quite sure what to check out. I expected
> the content of 'trunk' to be the root of the mainline, but it looks more
> as if http://svn.sourceforge.net/viewcvs.cgi/epydoc/trunk/epydoc/src/
> is what I'm looking for

To get the contents of the current trunk (including docs, source code, 
sandbox, etc), use:

% svn co https://svn.sourceforge.net/svnroot/epydoc/trunk/epydoc epydoc

To get just the source code for epydoc, use:

% svn co 
https://svn.sourceforge.net/svnroot/epydoc/trunk/epydoc/src/epydoc epydoc

> To be honest, the main reason for me to try out epydoc is because I was
> looking into the javadoc and rest parsers for inspiration, [...]
> Thus there is considerable overlap with tools such as epydoc. May be there
> are some ideas to share...

I'm sure there are -- I've taken more than a few good ideas from some of 
the other API documentation extractors out there, including javadoc, 
doxygen, pydoc, pythondoc, etc.  A nice list of these tools is available 
at <http://www.stack.nl/~dimitri/doxygen/links.html>

-Edward