[Numpy-discussion] f2py functions, docstrings, and epydoc

Tom Loredo loredo@astro.cornell....
Thu Mar 27 12:20:33 CDT 2008


> smll_offset = smll_offset
> exec `smll_offset.__doc__`

Thanks for the quick and helpful response!  I'll give it
a try.  I don't grasp why it works, though.  I suppose I don't
need to, but... I'm guessing the exec adds stuff to the current
namespace that isn't there until a fortran object's attributes
are explicitly accessed.

While I have your attention... could you clear this up, also just
for my curiousity?  It's probably related.

> f2py generated functions (that, by the way, are
> actually instances of `fortran` type and define __call__ method).

I had wondered about this when I first encountered this issue,
and thought maybe I could figure out how to put some hook into
epydoc so it would document anything with a __call__ method.
But it looks like 'fortran' objects *don't* have a __call__
(here _cbmlike is my f2py-generated module):

In [1]: from inference.count._cbmlike import smllike

In [2]: smllike
Out[2]: <fortran object at 0x947a668>

In [3]: dir smllike
------> dir(smllike)
Out[3]: ['__doc__', '_cpointer']

In [4]: smllike.__call__
AttributeError                            Traceback (most recent call last)

/home/inference/loredo/tex/meetings/head08/<ipython console> in <module>()

AttributeError: __call__

Yet despite this apparent absence of __call__, I can magically
call smllike just fine.  Would you provide a quick explanation of
what f2py and the fortran object are doing here?


This mail sent through IMP: http://horde.org/imp/

More information about the Numpy-discussion mailing list