[Numpy-discussion] f2py produces so.so

George Nurser gnurser at googlemail.com
Mon Jun 19 17:15:10 CDT 2006

On 19/06/06, Berthold Höllmann <bhoel at despammed.com> wrote:
> "George Nurser" <gnurser at googlemail.com> writes:
> > I have run into a strange problem with the current numpy/f2py (f2py
> > 2_2631, numpy 2631).
> > I have a file [Wright.f] which contains 5 different fortran
> > subroutines. Arguments have been specified as input or output by
> > adding cf2py    intent (in), (out) etc.
> >
> > Doing
> > f2py -c Wright.f -m Wright.so
> simply try
> f2py -c Wright.f -m Wright
> instead. Python extension modules require the an exported routine
> named init<module name> (initWright in this case). But you told f2py
> to generate an extension module named "so" in a package named
> "Wright", so the generated function is named initso. The *.so file
> cannot be renamed because then there is no more matching init function
> anymore.
> Regards
> Berthold

Stupid of me! Hit head against wall.

Yes, I eventually worked out that f2py -c Wright.f -m Wright was OK.

But many thanks for the explanation ....I see, what f2py was doing was
perfectly logical.

Regards, George.

More information about the Numpy-discussion mailing list