2ikdZgdZddlZddlZddlZddlmZddlmZejZejZ d dZ dZ d Z d Z y) z(Fortran to Python Interface Generator. )run_maincompile get_includeN)f2py2e)diagnosec>ddl}ddl}|+|j|\} } tj| n|} t |t s t |d} t| d5} | j|ddddd| jg} t |t r&tjdk(} |j|| }| j|tjdd g| z} tj| d }|r$t!|j"j% |tj*|  |r|S|j,S#1swYxYw#t&$rtj(| d dd}YXwxYw#|tj*| wwxYw)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 rN)suffixzutf-8wz-cz-mposix)r z)import numpy.f2py as f2py2e;f2py2e.main()T)capture_output)stdoutstderr)tempfileshlexmkstemposclose isinstancestropenwritenamesplitextendsys executable subprocessrunprintrdecodeOSErrorCompletedProcessremove returncode)source modulename extra_argsverbose source_fn extension full_outputrrffnameargsis_posixccps J/var/www/html/acx/venv/lib/python3.12/site-packages/numpy/f2py/__init__.pyrrs}x##9#55   fc "VW% %   GGFO dJ/ j# &7*HZx@J J ^^  8 :<@ A *$7B bii&&()   IIe  }};    M,,QCLB M   IIe  sI F!E3A5F)E&FEF"E?<F>E??FFctjjtjjtdS)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)rpathjoindirname__file__rr5rr|s'X 77<<15 99rcr|dk(rddlm}|t}|Stdj t|)Ntestr) PytestTesterz!module {!r} has no attribute {!r})numpy._pytesttesterr?__name__AttributeErrorformat)attrr?r>s r5 __getattr__rEs= v~4H% %%+VHd%;= =rcLttjdhzS)Nr>)listglobalskeysr<rr5__dir__rJs   F8+ ,,r)untitledTNz.fF)__doc____all__rr rrLrrrmainrrrErJr<rr5rPs] 1   ?? {{" gT,:^ =-r