Edit File: memmap.cpython-311.pyc
� u�d�- � � � d dl mZ d dlZddlmZ ddlmZmZm Z d dl m Z m Z dgZ e Zg d �Zd d gZd d d d d�Z ed� � G d� de� � � � ZdS )� )� nullcontextN� )� set_module� )�uint8�ndarray�dtype)� os_fspath�is_pathlib_path�memmap)�r�c�r+�w+r r r r )�readonly� copyonwrite� readwrite�write�numpyc �P � � e Zd ZdZdZeddddfd�Zd� Zd � Zd � fd � Z � fd �Z � xZ S ) r a� Create a memory-map to an array stored in a *binary* file on disk. Memory-mapped files are used for accessing small segments of large files on disk, without reading the entire file into memory. NumPy's memmap's are array-like objects. This differs from Python's ``mmap`` module, which uses file-like objects. This subclass of ndarray has some unpleasant interactions with some operations, because it doesn't quite fit properly as a subclass. An alternative to using this subclass is to create the ``mmap`` object yourself, then create an ndarray with ndarray.__new__ directly, passing the object created in its 'buffer=' parameter. This class may at some point be turned into a factory function which returns a view into an mmap buffer. Flush the memmap instance to write the changes to the file. Currently there is no API to close the underlying ``mmap``. It is tricky to ensure the resource is actually closed, since it may be shared between different memmap instances. Parameters ---------- filename : str, file-like object, or pathlib.Path instance The file name or file object to be used as the array data buffer. dtype : data-type, optional The data-type used to interpret the file contents. Default is `uint8`. mode : {'r+', 'r', 'w+', 'c'}, optional The file is opened in this mode: +------+-------------------------------------------------------------+ | 'r' | Open existing file for reading only. | +------+-------------------------------------------------------------+ | 'r+' | Open existing file for reading and writing. | +------+-------------------------------------------------------------+ | 'w+' | Create or overwrite existing file for reading and writing. | | | If ``mode == 'w+'`` then `shape` must also be specified. | +------+-------------------------------------------------------------+ | 'c' | Copy-on-write: assignments affect data in memory, but | | | changes are not saved to disk. The file on disk is | | | read-only. | +------+-------------------------------------------------------------+ Default is 'r+'. offset : int, optional In the file, array data starts at this offset. Since `offset` is measured in bytes, it should normally be a multiple of the byte-size of `dtype`. When ``mode != 'r'``, even positive offsets beyond end of file are valid; The file will be extended to accommodate the additional data. By default, ``memmap`` will start at the beginning of the file, even if ``filename`` is a file pointer ``fp`` and ``fp.tell() != 0``. shape : tuple, optional The desired shape of the array. If ``mode == 'r'`` and the number of remaining bytes after `offset` is not a multiple of the byte-size of `dtype`, you must specify `shape`. By default, the returned array will be 1-D with the number of elements determined by file size and data-type. order : {'C', 'F'}, optional Specify the order of the ndarray memory layout: :term:`row-major`, C-style or :term:`column-major`, Fortran-style. This only has an effect if the shape is greater than 1-D. The default order is 'C'. Attributes ---------- filename : str or pathlib.Path instance Path to the mapped file. offset : int Offset position in the file. mode : str File mode. Methods ------- flush Flush any changes in memory to file on disk. When you delete a memmap object, flush is called first to write changes to disk. See also -------- lib.format.open_memmap : Create or load a memory-mapped ``.npy`` file. Notes ----- The memmap object can be used anywhere an ndarray is accepted. Given a memmap ``fp``, ``isinstance(fp, numpy.ndarray)`` returns ``True``. Memory-mapped files cannot be larger than 2GB on 32-bit systems. When a memmap causes a file to be created or extended beyond its current size in the filesystem, the contents of the new part are unspecified. On systems with POSIX filesystem semantics, the extended part will be filled with zero bytes. Examples -------- >>> data = np.arange(12, dtype='float32') >>> data.resize((3,4)) This example uses a temporary file so that doctest doesn't write files to your directory. You would use a 'normal' filename. >>> from tempfile import mkdtemp >>> import os.path as path >>> filename = path.join(mkdtemp(), 'newfile.dat') Create a memmap with dtype and shape that matches our data: >>> fp = np.memmap(filename, dtype='float32', mode='w+', shape=(3,4)) >>> fp memmap([[0., 0., 0., 0.], [0., 0., 0., 0.], [0., 0., 0., 0.]], dtype=float32) Write data to memmap array: >>> fp[:] = data[:] >>> fp memmap([[ 0., 1., 2., 3.], [ 4., 5., 6., 7.], [ 8., 9., 10., 11.]], dtype=float32) >>> fp.filename == path.abspath(filename) True Flushes memory changes to disk in order to read them back >>> fp.flush() Load the memmap and verify data was stored: >>> newfp = np.memmap(filename, dtype='float32', mode='r', shape=(3,4)) >>> newfp memmap([[ 0., 1., 2., 3.], [ 4., 5., 6., 7.], [ 8., 9., 10., 11.]], dtype=float32) Read-only memmap: >>> fpr = np.memmap(filename, dtype='float32', mode='r', shape=(3,4)) >>> fpr.flags.writeable False Copy-on-write memmap: >>> fpc = np.memmap(filename, dtype='float32', mode='c', shape=(3,4)) >>> fpc.flags.writeable True It's possible to assign to copy-on-write array, but values are only written into the memory copy of the array, and not written to disk: >>> fpc memmap([[ 0., 1., 2., 3.], [ 4., 5., 6., 7.], [ 8., 9., 10., 11.]], dtype=float32) >>> fpc[0,:] = 0 >>> fpc memmap([[ 0., 0., 0., 0.], [ 4., 5., 6., 7.], [ 8., 9., 10., 11.]], dtype=float32) File on disk is unchanged: >>> fpr memmap([[ 0., 1., 2., 3.], [ 4., 5., 6., 7.], [ 8., 9., 10., 11.]], dtype=float32) Offset into a memmap: >>> fpo = np.memmap(filename, dtype='float32', mode='r', offset=16) >>> fpo memmap([ 4., 5., 6., 7., 8., 9., 10., 11.], dtype=float32) g Y�r r N�Cc �" � dd l }dd l} t | }np# t $ rc} |t vrPt d� t t t � � � � � z |� � � � d �Y d } ~ nd } ~ ww xY w|dk r|�t d� � �t |d� � rt |� � } n(t t |� � |dk rdn|dz � � } | 5 } | � dd � � | � � � } t |� � } | j }|�"| |z }||z rt d � � �||z }|f}n6t# |t$ � � s|f}t' j d � � }|D ]}||z }�t+ |||z z � � }|d v rH| |k rB| � |d z d� � | � d � � | � � � |dk r|j }n|dk r|j }n|j }|||j z z }||z }||z }|� | � � � |||�� � }t; j | || |||�� � }||_ ||_ ||_! tE |� � r|�# � � |_$ nVt | d� � r?t# | j% tL � � r%|j' �( | j% � � |_$ nd |_$ d d d � � n # 1 swxY w Y |S )Nr z#mode must be one of {!r} (got {!r})r z#shape must be given if mode == 'w+'�readr r �br z?Size of available data is not a multiple of the data-type size.r )r r � )�access�offset)r �bufferr �order�name))�mmap�os.path�mode_equivalents�KeyError�valid_filemodes� ValueError�format�list�keys�hasattrr �openr �seek�tell� dtypedescr�itemsize� isinstance�tuple�np�intp�intr �flush� ACCESS_COPY� ACCESS_READ� ACCESS_WRITE�ALLOCATIONGRANULARITY�filenor �__new__�_mmapr �moder �resolve�filenamer �str�path�abspath)�subtyper? r r= r �shaper r! �os�e�f_ctx�fid�flen�descr�_dbytes�bytes�size�k�acc�start� array_offset�mm�selfs �H/opt/cloudlinux/venv/lib64/python3.11/site-packages/numpy/core/memmap.pyr; zmemmap.__new__� s� � � � � � ����� �#�D�)�D�D��� � � ��?�*�*� �9��V�O�d�3C�3H�3H�3J�3J�.K�.K� K�T�R�R�� � � � +�*�*�*�*����� ���� �4�<�<�E�M� � B�C�C� C� �8�V� $� $� R� ��)�)�E�E���8�,�,�d�c�k�k�s�s�t�S�.P�Q�Q�E� � 6 %�c� �H�H�Q��N�N�N��8�8�:�:�D� �u�%�%�E��n�G��}� �v� ���7�?� ?�$� &>� ?� ?� ?� ��'�� ����!�%��/�/� %� "�H�E��w�q�z�z�� � � �A��A�I�D�D����g� �-�.�.�E��|�#�#��u� � �������A�&�&�&�� � �%� � � �� � � � � ��s�{�{��&��������&����'���V�d�&@� @�@�E� �U�N�E�!�E�>�L����3�:�:�<�<��s�5��I�I�B��?�7�E��r�*6�e�E� E� E�D��D�J� �D�K� �D�I� �x�(�(� %� !)� 0� 0� 2� 2�� � ���f�%�%� %�*�S�X�s�*C�*C� %� "������ 9� 9�� � � !%�� �m6 %� 6 %� 6 %� 6 %� 6 %� 6 %� 6 %� 6 %� 6 %� 6 %� 6 %���� 6 %� 6 %� 6 %� 6 %�p � s( � � B�AB � B�)HL�L� Lc �� � t |d� � rGt j | |� � r2|j | _ |j | _ |j | _ |j | _ d S d | _ d | _ d | _ d | _ d S )Nr< )r* r2 �may_share_memoryr< r? r r= )rS �objs rT �__array_finalize__zmemmap.__array_finalize__! sp � � �3�� � � �R�%8��s�%C�%C� � ��D�J� �L�D�M� �*�D�K���D�I�I�I� �D�J� �D�M� �D�K� �D�I�I�I� c �x � | j �0t | j d� � r | j � � � dS dS dS )z� Write any changes in the array to the file on disk. For further information, see `memmap`. Parameters ---------- None See Also -------- memmap Nr5 )�baser* r5 )rS s rT r5 z memmap.flush- sC � � �9� �W�T�Y��%@�%@� � �I�O�O� � � � � � !� � � rY c �� �� t � � � ||� � }| |u st | � � t ur|S |j dk r|d S |� t j � � S )N� )�super�__array_wrap__�typer rD �viewr2 r )rS �arr�context� __class__s �rT r_ zmemmap.__array_wrap__? sf �� ��g�g�$�$�S�'�2�2�� �3�;�;�$�t�*�*�F�2�2��J� �9��?�?��r�7�N��x�x�� �#�#�#rY c � �� t � � � |� � }t |� � t u r"|j �|� t �� � S |S )N)r` )r^ � __getitem__r` r r< ra r )rS �index�resrd s �rT rf zmemmap.__getitem__N sK �� ��g�g�!�!�%�(�(�� ��9�9�� � �3�9�#4��8�8��8�)�)� )�� rY )N) �__name__� __module__� __qualname__�__doc__�__array_priority__r r; rX r5 r_ rf � __classcell__)rd s @rT r r s� �� � � � � �u� u�n ��).�T�!��#�N� N� N� N�` � � � � � �$ $� $� $� $� $� $� � � � � � � � � rY )� contextlibr r r2 �_utilsr �numericr r r � numpy.compatr r �__all__r. r% �writeable_filemodesr# r r] rY rT �<module>ru s� �� "� "� "� "� "� "� � � � � � � � � � � *� *� *� *� *� *� *� *� *� *� 3� 3� 3� 3� 3� 3� 3� 3� �*�� � �(�(�(���T�l� � ��� � � � � ��G���{� {� {� {� {�W� {� {� ��{� {� {rY