On 9/21/06, Sebastian Haase <[EMAIL PROTECTED]> wrote:
On Thursday 21 September 2006 09:05, Charles R Harris wrote:
> Travis,
>
> A few questions.
>
> 1) I can't find any systematic code testing units, although there seem to
> be tests for regressions and such. Is there a place we should be putting
> such tests?
>
> 2) Any plans for code documentation? I documented some of my stuff with
> doxygen markups and wonder if we should include a Doxyfile as part of the
> package.

Are able to use doxygen for Python code ? I thought it only worked for C (and
alike) ?

IIRC correctly, it now does Python too. Let's see... here is an example
## Documentation for this module.

#
# More details.

## Documentation for a function.
#
# More details.
def func():
pass

Looks like ## replaces the /**

Chuck


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Numpy-discussion mailing list
Numpy-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/numpy-discussion

Reply via email to