[f2py] Draft: F2PY Users Guide and Reference Manual
Fri, 6 Dec 2002 15:17:51 +0100
On Fri, 6 Dec 2002, Pearu Peterson wrote:
>> >> 1.) In the draft, f2py is always used either with the -h or with the -c
>> >> switch. Is there any sense using f2py without any option,
>> >> i.e "f2py foo.pyf foo.f"?
>> >Yes, there is. Without -c and -h switch f2py just generates the
>> >source file <modulename>module.c to the current directory.
>> But I think the average user usually does not fiddle with
>> <modulename>module.c, and will use f2py always with -c or -h, am I
>Yes. That's true. In the early days of F2PY the main task for it was to
>generate <modulename>module.c. Currently generating <modulename>module.c
>is only useful when debugging, or when one wants to use other building
>tools (make, scons, jam,etc.) than scipy_distutils.
>So, do you have any suggestions regarding -c and -h switches?
I think its o.k. the way it is. In the users guide there should be
explained that -- depending on the input files and the switches -- three
steps are performed by f2py:
1.) Generation of the .pyf file.
2.) Generation of the <modulename>module.c file.
3.) Use the compiler to preprocess, compile, assemble and link the
And that without a switch f2py stops after step 2.), which is seldom
Another thing, i am not familiar with scipy_distutils, but is it
possible to pass compiler flags through f2py to the compiler in order to
have better control of the compilation step?
f2py-users mailing list
----- End forwarded message -----
_| -------> Hier steht KEIN origineller Spruch <-------