Re: [Epydoc-devel] errors in 3.0alpha

[Stefan S. <se...@sy...>]

Edward Loper wrote:
> Hi, Stefan.
> 
> Thanks for the bug reports.  I *believe* that all the bugs you noted 
> should be fixed in the most recent version of epydoc (i.e., in the 
> subversion repository).  But I can't test that without having a piece of 
> sample code that elicits the problem.  If you're comfortable with using 
> subversion, please check out the most recent version of epydoc and see 
> if the problem(s) still exist:
> 
>   <http://sourceforge.net/svn/?group_id=32455>

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 (I judged simply by the existence of a 'setup.py'
file). Also, I'm not sure what URL to feed to svn for the checkout. None
of the ones I tried worked. Can you help ?
Thanks !

> 
> If you'd rather not check out a copy from subversion, or the problem(s) 
> still exist, please file a bug report on sourceforge:
> 
>   <http://sourceforge.net/tracker/?group_id=32455&atid=405618>
> 
> If possible, please include an attachment containing a small piece of 
> sample code that elicits the problem(s).

Ok, I will try to.

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, as I'd like
to improve the synopsis tool (http://synopsis.fresco.org). Synopsis
provides tools to parse source code in different languages (Python, IDL,
C, C++) and then process the generated AST, for example into documentation.

Thus there is considerable overlap with tools such as epydoc. May be there
are some ideas to share...

Regards,
		Stefan