6N\ d Z g dZddlZddlZddlZddlmZ ddlmZ ej Zej Z dd Z
d
Z d Z d Z
dS )z(Fortran to Python Interface Generator.
)run_maincompile get_include N )f2py2e)diagnoseuntitled T.fFc d ddl }ddl}|.| | \ } }
t j | n|}
t | t st
| d } t |
d 5 } | | ddd n # 1 swxY w Y dd|| j g} t |t r't j dk } |
|| }| | t j
dd
g| z }
t j |
d }|r&t! |j n(# t& $ r t j |
d
dd }Y nw xY w|t j |
n # |t j |
w w xY w|r|S |j S )a
Build extension module from a Fortran 77 source string with f2py.
Parameters
----------
source : str or bytes
Fortran source of module / subroutine to compile
.. versionchanged:: 1.16.0
Accept str as well as bytes
modulename : str, optional
The name of the compiled python module
extra_args : str or list, optional
Additional parameters passed to f2py
.. versionchanged:: 1.16.0
A list of args may also be provided.
verbose : bool, optional
Print f2py output to screen
source_fn : str, optional
Name of the file where the fortran source is written.
The default is to use a temporary file with the extension
provided by the ``extension`` parameter
extension : ``{'.f', '.f90'}``, optional
Filename extension if `source_fn` is not provided.
The extension tells which fortran standard is used.
The default is ``.f``, which implies F77 standard.
.. versionadded:: 1.11.0
full_output : bool, optional
If True, return a `subprocess.CompletedProcess` containing
the stdout and stderr of the compile process, instead of just
the status code.
.. versionadded:: 1.20.0
Returns
-------
result : int or `subprocess.CompletedProcess`
0 on success, or a `subprocess.CompletedProcess` if
``full_output=True``
Examples
--------
.. literalinclude:: ../../source/f2py/code/results/compile_session.dat
:language: python
r N)suffixzutf-8wz-cz-mposix)r z)import numpy.f2py as f2py2e;f2py2e.main()T)capture_output )stdoutstderr)tempfileshlexmkstemposclose
isinstancestropenwritenamesplitextendsys
executable
subprocessrunprintr decodeOSErrorCompletedProcessremove
returncode)source
modulename
extra_argsverbose source_fn extension full_outputr r ffnameargsis_posixccps g/builddir/build/BUILD/cloudlinux-venv-1.0.10/venv/lib64/python3.11/site-packages/numpy/f2py/__init__.pyr r s) x OOOLLL##9#555 fc " " &VW%%
%
GGFOOO dJ/ j# & & A7*H Zx@@J J
^
8
:<@
A * $777B
*bi&&(())) M M M,QCLLLBBB M Ie Ie } sU !F 1B F BF BA1F
E #)F "E1.F 0E11F F$c t j t j t d S )aw
Return the directory that contains the ``fortranobject.c`` and ``.h`` files.
.. note::
This function is not needed when building an extension with
`numpy.distutils` directly from ``.f`` and/or ``.pyf`` files
in one go.
Python extension modules built with f2py-generated code need to use
``fortranobject.c`` as a source file, and include the ``fortranobject.h``
header. This function can be used to obtain the directory containing
both of these files.
Returns
-------
include_path : str
Absolute path to the directory containing ``fortranobject.c`` and
``fortranobject.h``.
Notes
-----
.. versionadded:: 1.21.1
Unless the build system you are using has specific support for f2py,
building a Python extension using a ``.pyf`` signature file is a two-step
process. For a module ``mymod``:
* Step 1: run ``python -m numpy.f2py mymod.pyf --quiet``. This
generates ``_mymodmodule.c`` and (if needed)
``_fblas-f2pywrappers.f`` files next to ``mymod.pyf``.
* Step 2: build your Python extension module. This requires the
following source files:
* ``_mymodmodule.c``
* ``_mymod-f2pywrappers.f`` (if it was generated in Step 1)
* ``fortranobject.c``
See Also
--------
numpy.get_include : function that returns the numpy include directory
src)r pathjoindirname__file__ r r8 r r | s) X 7<<115 9 99r c | dk rddl m} |t }|S t d t | )Ntestr ) PytestTesterz!module {!r} has no attribute {!r})numpy._pytesttesterrB __name__AttributeErrorformat)attrrB rA s r8 __getattr__rH s[ v~~444444|H%% %%+VHd%;%;= = =r c d t t dhz S )NrA )listglobalskeysr? r r8 __dir__rM s% F8+ , ,,r )r r
TNr F)__doc____all__r! r# r r
r r r mainr r rH rM r? r r8 rQ s 1
0
0
?
{ "
g g g g T,: ,: ,:^ = = = - - - - -r