On Thu, March 27, 2008 7:20 pm, Tom Loredo wrote:
>
> Pearu-
>
>> 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
Pearu-
> 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 objec
Hi,
Tom Loredo wrote:
> Hi folks-
>
> Can anyone offer any tips on how I can get epydoc to produce
> API documentation for functions in an f2py-produced module?
> Currently they get listed in the generated docs as "Variables":
>
> Variables
> psigc =
> sigctp =
> smll_offset
Hi folks-
Can anyone offer any tips on how I can get epydoc to produce
API documentation for functions in an f2py-produced module?
Currently they get listed in the generated docs as "Variables":
Variables
psigc =
sigctp =
smll_offset =
Yet each of these objects is cal
