a hEb@sdZgdZddlZddlZddlZddlmZddlmZejZej Z dd d Z ddZ ej dddkr~ddZ ddZn"ddlmZddlmZeeZ[dS)z(Fortran to Python Interface Generator. )run_maincompile get_includeN)f2py2e)diagnoseuntitledT.fFc Csbddl}ddl}|dur4|j|d\} } t| n|} t|tsLt|d}zt| d} | |Wdn1sx0Ydd|| j g} t|trtj dk} |j || d }| |t j dd g| } ztj| tjtjd }Wn&ty tj| d d d d }Yn0|r t|jW|durNt| n|durLt| 0|rX|S|jSdS)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())stdoutstderr)tempfileshlexmkstemposclose isinstancestropenwritenamesplitextendsys executable subprocessrunPIPEOSErrorCompletedProcessprintrdecoderemove returncode)source modulename extra_argsverboseZ source_fn extensionZ full_outputrrffnameargsZis_posixccpr3S/home/ja/django-apps/lartica_env/lib/python3.9/site-packages/numpy/f2py/__init__.pyrsJ<    (        rcCstjtjtdS)a 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.22.0 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__r3r3r3r4r}s,r)cCsR|dkrddlmm}|S|dkr>ddlm}|t}|Stdt|dS)N f2py_testingrtest PytestTesterz!module {!r} has no attribute {!r})Znumpy.f2py.f2py_testingZf2pyr=numpy._pytesttesterr@__name__AttributeErrorformat)attrr=r@r>r3r3r4 __getattr__s rFcCsttddhBS)Nr=r>)listglobalskeysr3r3r3r4__dir__srJ)r=r?)rr TNr F)__doc____all__rr rr rrrmainrr version_inforFrJr=rAr@rBr>r3r3r3r4s.   k/