1jJ/ @dZddlZddlZddlmZddlmZddlmZdZ e gdZ dZ e \Z Z d e d e d Zd Zed gdedgdedgdedgdedgdedgdedgdedgdedgdedgd ed!gd"ed#gd$ed%gd&ed'd(gd)ed*d+gd,ed-d.gd/ed0d1d2gd3ed4d5d6gd7ed8gd9ed:d;gd<ed=d>gd?ed@gdAedBgdCedDgdEedFdGdHdID]>ZedFedJdKeLfedFedMdNedOedPedQf?dRD]CZedFedSdNedTedUeejrdVedWndXzfDdS)Yz This file is separate from ``_add_newdocs.py`` so that it can be mocked out by our sphinx ``conf.py`` during doc builds, where we want to avoid showing platform-dependent information. N)dtype) numerictypes) add_newdocc<fd}t|S)Nc3vKD]2\}} tt|}|||fV##t$rY/wxYwdS)N)getattr _numerictypesAttributeError)aliasdoc alias_typealiasess V/opt/cloudlinux/venv/lib64/python3.11/site-packages/numpy/core/_add_newdocs_scalars.pytype_aliases_genz.numeric_type_aliases..type_aliases_gensr! / /JE3 /$]E:: "5#..... "     / /s ) 66)list)rrs` rnumeric_type_aliasesrs6/////   "" # ##))int8z*8-bit signed integer (``-128`` to ``127``))int16z116-bit signed integer (``-32_768`` to ``32_767``))int32z?32-bit signed integer (``-2_147_483_648`` to ``2_147_483_647``))int64zW64-bit signed integer (``-9_223_372_036_854_775_808`` to ``9_223_372_036_854_775_807``))intpzJSigned integer large enough to fit pointer, compatible with C ``intptr_t``)uint8z)8-bit unsigned integer (``0`` to ``255``))uint16z-16-bit unsigned integer (``0`` to ``65_535``))uint32z432-bit unsigned integer (``0`` to ``4_294_967_295``))uint64zA64-bit unsigned integer (``0`` to ``18_446_744_073_709_551_615``))uintpzMUnsigned integer large enough to fit pointer, compatible with C ``uintptr_t``)float16zX16-bit-precision floating-point number type: sign bit, 5 bits exponent, 10 bits mantissa)float32zX32-bit-precision floating-point number type: sign bit, 8 bits exponent, 23 bits mantissa)float64zY64-bit precision floating-point number type: sign bit, 11 bits exponent, 52 bits mantissa)float96z496-bit extended-precision floating-point number type)float128z5128-bit extended-precision floating-point number type) complex64zIComplex number type composed of 2 32-bit-precision floating-point numbers) complex128zIComplex number type composed of 2 64-bit-precision floating-point numbers) complex192zRComplex number type composed of 2 96-bit extended-precision floating-point numbers) complex256zSComplex number type composed of 2 128-bit extended-precision floating-point numbersc  tj\}}}}}ne#t$rXtj}|dkrAtjddptjdd}nd}YnwxYw||fS)Nwin32PROCESSOR_ARCHITEW6432PROCESSOR_ARCHITECTUREunknown)osunamer sysplatformenvironget)system_machines r_get_platform_and_machiner66s #%8:: 1a     W  jnn%=rBBDz~~&>CC G G   7?sAA>=A>z:Alias on this platform ( z):c|tt|tj}|jkrdnd|d}|r dd|D}nd}|dfdt Dz }d|d|d||d}td ||dS) Nr*z:Canonical name: `numpy.` c3"K|] }d|dV dS)z:Alias: `numpy.r9N).0r s r z-add_newdoc_for_scalar_type..OsA88 %=e<<<888888rc3HK|]\}}}|u td|d|dVdS)z `numpy.z`: z. N)_doc_alias_string)r<r r r os rr=z-add_newdoc_for_scalar_type..SsX^^5j%Z[\__.MMuMMMMMM\___^^rz z :Character code: ``'z'`` numpy.core.numerictypes) rr rchar__name__joinpossible_aliasesstripr)obj fixed_aliasesr character_codecanonical_name_doc alias_doc docstringr@s @radd_newdoc_for_scalar_typerMGs1 s##A1XX]N"aj00?3???GG88)688888   ^^^^9I^^^^^^IYY[[( # I(#y99999rbool_aD Boolean type (True or False), stored as a byte. .. warning:: The :class:`bool_` type is not a subclass of the :class:`int_` type (the :class:`bool_` is not even a number type). This is different than Python's default implementation of :class:`bool` as a sub-class of :class:`int`. bytez: Signed integer type, compatible with C ``char``. shortz; Signed integer type, compatible with C ``short``. intcz9 Signed integer type, compatible with C ``int``. int_zK Signed integer type, compatible with Python `int` and C ``long``. longlongz? Signed integer type, compatible with C ``long long``. ubytezE Unsigned integer type, compatible with C ``unsigned char``. ushortzF Unsigned integer type, compatible with C ``unsigned short``. uintczD Unsigned integer type, compatible with C ``unsigned int``. uintzE Unsigned integer type, compatible with C ``unsigned long``. ulonglongzH Signed integer type, compatible with C ``unsigned long long``. halfz4 Half-precision floating-point number type. singlezS Single-precision floating-point number type, compatible with C ``float``. doublefloat_zk Double-precision floating-point number type, compatible with Python `float` and C ``double``. longdouble longfloatz Extended-precision floating-point number type, compatible with C ``long double`` but not necessarily with IEEE 754 quadruple-precision. csingle singlecomplexzZ Complex number type composed of two single-precision floating-point numbers. cdoublecfloatcomplex_z| Complex number type composed of two double-precision floating-point numbers, compatible with Python `complex`. clongdouble clongfloat longcomplexz\ Complex number type composed of two extended-precision floating-point numbers. object_z Any Python object. str_unicode_au A unicode string. This type strips trailing null codepoints. >>> s = np.str_("abc\x00") >>> s 'abc' Unlike the builtin `str`, this supports the :ref:`python:bufferobjects`, exposing its contents as UCS4: >>> m = memoryview(np.str_("abc")) >>> m.format '3w' >>> m.tobytes() b'a\x00\x00\x00b\x00\x00\x00c\x00\x00\x00' bytes_string_zX A byte string. When used in arrays, this type strips trailing null bytes. voida np.void(length_or_data, /, dtype=None) Create a new structured or unstructured void scalar. Parameters ---------- length_or_data : int, array-like, bytes-like, object One of multiple meanings (see notes). The length or bytes data of an unstructured void. Or alternatively, the data to be stored in the new scalar when `dtype` is provided. This can be an array-like, in which case an array may be returned. dtype : dtype, optional If provided the dtype of the new scalar. This dtype must be "void" dtype (i.e. a structured or unstructured void, see also :ref:`defining-structured-types`). ..versionadded:: 1.24 Notes ----- For historical reasons and because void scalars can represent both arbitrary byte data and structured dtypes, the void constructor has three calling conventions: 1. ``np.void(5)`` creates a ``dtype="V5"`` scalar filled with five ``\0`` bytes. The 5 can be a Python or NumPy integer. 2. ``np.void(b"bytes-like")`` creates a void scalar from the byte string. The dtype itemsize will match the byte string length, here ``"V10"``. 3. When a ``dtype=`` is passed the call is roughly the same as an array creation. However, a void scalar rather than array is returned. Please see the examples which show all three different conventions. Examples -------- >>> np.void(5) void(b'\x00\x00\x00\x00\x00') >>> np.void(b'abcd') void(b'\x61\x62\x63\x64') >>> np.void((5, 3.2, "eggs"), dtype="i,d,S5") (5, 3.2, b'eggs') # looks like a tuple, but is `np.void` >>> np.void(3, dtype=[('x', np.int8), ('y', np.int8)]) (3, 3) # looks like a tuple, but is `np.void` datetime64a If created from a 64-bit integer, it represents an offset from ``1970-01-01T00:00:00``. If created from string, the string can be in ISO 8601 date or datetime format. >>> np.datetime64(10, 'Y') numpy.datetime64('1980') >>> np.datetime64('1980', 'Y') numpy.datetime64('1980') >>> np.datetime64(10, 'D') numpy.datetime64('1970-01-11') See :ref:`arrays.datetime` for more information. timedelta64zg A timedelta stored as a 64-bit integer. See :ref:`arrays.datetime` for more information. rAinteger) is_integerz integer.is_integer() -> bool Return ``True`` if the number is finite with integral value. .. versionadded:: 1.22 Examples -------- >>> np.int64(-2).is_integer() True >>> np.uint32(5).is_integer() True )rYrZr[r]as_integer_ratioa {ftype}.as_integer_ratio() -> (int, int) Return a pair of integers, whose ratio is exactly equal to the original floating point number, and with a positive denominator. Raise `OverflowError` on infinities and a `ValueError` on NaNs. >>> np.{ftype}(10.0).as_integer_ratio() (10, 1) >>> np.{ftype}(0.0).as_integer_ratio() (0, 1) >>> np.{ftype}(-.25).as_integer_ratio() (-1, 4) )ftyperpz z.is_integer() -> bool Return ``True`` if the floating point number is finite with integral value, and ``False`` otherwise. .. versionadded:: 1.22 Examples -------- >>> np.z0(-2.0).is_integer() True >>> np.z)(3.2).is_integer() False ) rrrrrrrrrrrr bit_countz.bit_count() -> int Computes the number of 1-bits in the absolute value of the input. Analogous to the builtin `int.bit_count` or ``popcount`` in C++. Examples -------- >>> np.z(127).bit_count() 7z >>> np.z%(-127).bit_count() 7 r*)__doc__r/r- numpy.corerrr numpy.core.function_baserrrEr6_system_machiner?rM float_nameformatint_namerBislowerr;rrr}sb  444444////// $ $ $('))).   .-//FFF(FFF:::27B     62   7B   62   62   :r   7B   8R   7B   62   ;   62   8R   8hZ   <+   9&7   9x&<   =<*G   9b   6J<   (8i[   62/0 0 0 d<   "="    $i2    "=  JJ(*7I  FF $ $7&''' J(*|        7 "A99HJ(([   uX#++-- 6     46 758999999r