/usr/local/lib64/python3.6/site-packages/numpy/lib/__pycache__
Edit: /usr/local/lib64/python3.6/site-packages/numpy/lib/__pycache__/format.cpython-36.pyc (25179B)
3
EgPy @ s d Z ddlZddlZddlZddlmZ ddlmZmZm Z g Z
dZ e e d Z
dZd;Zd
d?d@dAiZdd Zdd Zdd Zdd Zdd Zdd Zdd Zd d Zd d ZdBd!d"Zd#d$ Zd%d& Z d'd( Z d)d* Z d+d, Z d-d. Z dCd0d1Z!dDd3d4Z"dEd6d7Z#dFd9d:Z$dS )Ga
Binary serialization
NPY format
==========
A simple format for saving numpy arrays to disk with the full
information about them.
The ``.npy`` format is the standard binary file format in NumPy for
persisting a *single* arbitrary NumPy array on disk. The format stores all
of the shape and dtype information necessary to reconstruct the array
correctly even on another machine with a different architecture.
The format is designed to be as simple as possible while achieving
its limited goals.
The ``.npz`` format is the standard format for persisting *multiple* NumPy
arrays on disk. A ``.npz`` file is a zip file containing multiple ``.npy``
files, one for each array.
Capabilities
------------
- Can represent all NumPy arrays including nested record arrays and
object arrays.
- Represents the data in its native binary form.
- Supports Fortran-contiguous arrays directly.
- Stores all of the necessary information to reconstruct the array
including shape and dtype on a machine of a different
architecture. Both little-endian and big-endian arrays are
supported, and a file with little-endian numbers will yield
a little-endian array on any machine reading the file. The
types are described in terms of their actual sizes. For example,
if a machine with a 64-bit C "long int" writes out an array with
"long ints", a reading machine with 32-bit C "long ints" will yield
an array with 64-bit integers.
- Is straightforward to reverse engineer. Datasets often live longer than
the programs that created them. A competent developer should be
able to create a solution in their preferred programming language to
read most ``.npy`` files that he has been given without much
documentation.
- Allows memory-mapping of the data. See `open_memmep`.
- Can be read from a filelike stream object instead of an actual file.
- Stores object arrays, i.e. arrays containing elements that are arbitrary
Python objects. Files with object arrays are not to be mmapable, but
can be read and written to disk.
Limitations
-----------
- Arbitrary subclasses of numpy.ndarray are not completely preserved.
Subclasses will be accepted for writing, but only the array data will
be written out. A regular numpy.ndarray object will be created
upon reading the file.
.. warning::
Due to limitations in the interpretation of structured dtypes, dtypes
with fields with empty names will have the names replaced by 'f0', 'f1',
etc. Such arrays will not round-trip through the format entirely
accurately. The data is intact; only the field names will differ. We are
working on a fix for this. This fix will not require a change in the
file format. The arrays with such structures can still be saved and
restored, and the correct dtype may be restored by using the
``loadedarray.view(correct_dtype)`` method.
File extensions
---------------
We recommend using the ``.npy`` and ``.npz`` extensions for files saved
in this format. This is by no means a requirement; applications may wish
to use these file formats but use an extension specific to the
application. In the absence of an obvious alternative, however,
we suggest using ``.npy`` and ``.npz``.
Version numbering
-----------------
The version numbering of these formats is independent of NumPy version
numbering. If the format is upgraded, the code in `numpy.io` will still
be able to read and write Version 1.0 files.
Format Version 1.0
------------------
The first 6 bytes are a magic string: exactly ``\x93NUMPY``.
The next 1 byte is an unsigned byte: the major version number of the file
format, e.g. ``\x01``.
The next 1 byte is an unsigned byte: the minor version number of the file
format, e.g. ``\x00``. Note: the version of the file format is not tied
to the version of the numpy package.
The next 2 bytes form a little-endian unsigned short int: the length of
the header data HEADER_LEN.
The next HEADER_LEN bytes form the header data describing the array's
format. It is an ASCII string which contains a Python literal expression
of a dictionary. It is terminated by a newline (``\n``) and padded with
spaces (``\x20``) to make the total of
``len(magic string) + 2 + len(length) + HEADER_LEN`` be evenly divisible
by 64 for alignment purposes.
The dictionary contains three keys:
"descr" : dtype.descr
An object that can be passed as an argument to the `numpy.dtype`
constructor to create the array's dtype.
"fortran_order" : bool
Whether the array data is Fortran-contiguous or not. Since
Fortran-contiguous arrays are a common form of non-C-contiguity,
we allow them to be written directly to disk for efficiency.
"shape" : tuple of int
The shape of the array.
For repeatability and readability, the dictionary keys are sorted in
alphabetic order. This is for convenience only. A writer SHOULD implement
this if possible. A reader MUST NOT depend on this.
Following the header comes the array data. If the dtype contains Python
objects (i.e. ``dtype.hasobject is True``), then the data is a Python
pickle of the array. Otherwise the data is the contiguous (either C-
or Fortran-, depending on ``fortran_order``) bytes of the array.
Consumers can figure out the number of bytes by multiplying the number
of elements given by the shape (noting that ``shape=()`` means there is
1 element) by ``dtype.itemsize``.
Format Version 2.0
------------------
The version 1.0 format only allowed the array header to have a total size of
65535 bytes. This can be exceeded by structured arrays with a large number of
columns. The version 2.0 format extends the header size to 4 GiB.
`numpy.save` will automatically save in 2.0 format if the data requires it,
else it will always use the more compatible 1.0 format.
The description of the fourth element of the header therefore has become:
"The next 4 bytes form a little-endian unsigned int: the length of the header
data HEADER_LEN."
Format Version 3.0
------------------
This version replaces the ASCII string (which in practice was latin1) with
a utf8-encoded string, so supports structured types with any unicode field
names.
Notes
-----
The ``.npy`` format, including motivation for creating it and a comparison of
alternatives, is described in the `"npy-format" NEP
`_, however details have
evolved with time and this document is more current.
N) safe_eval) isfileobj os_fspathpickles NUMPY @ we only support format version (1,0), (2,0), and (3,0), not %sr r r r r
r )r r r N)
ValueError)versionmsg r s z _has_metadata..F)metadatanamesanyZsubdtyper# base)r& r )r& r r# s
r# c C s2 t | rtjdtdd | jdk r(| jS | jS dS )a
Get a serializable descriptor from the dtype.
The .descr attribute of a dtype object cannot be round-tripped through
the dtype() constructor. Simple types, like dtype('float32'), have
a descr which looks like a record array with one field with '' as
a name. The dtype() constructor interprets this as a request to give
a default name. Instead, we construct descriptor that can be passed to
dtype().
Parameters
----------
dtype : dtype
The dtype of the array that will be written to disk.
Returns
-------
descr : object
An object that can be passed to `numpy.dtype()` in order to
replicate the input dtype.
zlmetadata on a dtype may be saved or ignored, but will raise if saved when read. Use another form of storage.r )
stacklevelN)r# warningswarn UserWarningr) descrstr)dtyper r r dtype_to_descr s
r3 c
C s t | trtj| S t | trStored array in format 2.0. It can only beread by NumPy >= 1.9)r, r
z@Stored array in format 3.0. It can only be read by NumPy >= 1.17)r r )r r )r
r )r[ r UnicodeEncodeErrorr- r. r/ )rX retr r r _wrap_header_guess_version{ s
r^ c C s| dg}x.t |j D ] \}}|jd|t|f qW |jd dj|}t|}|dkrdt|}n
t||}| j| dS )a Write the header for an array and returns the version used
Parameters
----------
fp : filelike object
d : dict
This has the appropriate entries for writing its string representation
to the header of the file.
version: tuple or None
None means use oldest that works
explicit version will raise a ValueError if the format does not
allow saving this data. Default: None
{z
'%s': %s, }r4 N) sorteditemsr@ reprjoin_filter_headerr^ r[ write)r! rK r rX keyvaluer r r _write_array_header s
ri c C s t | |d dS )z Write the header for an array using the 1.0 format.
Parameters
----------
fp : filelike object
d : dict
This has the appropriate entries for writing its string
representation to the header of the file.
r r N)r r )ri )r! rK r r r write_array_header_1_0 s
rj c C s t | |d dS )aQ Write the header for an array using the 2.0 format.
The 2.0 format allows storing very large structured arrays.
.. versionadded:: 1.9.0
Parameters
----------
fp : filelike object
d : dict
This has the appropriate entries for writing its string
representation to the header of the file.
r r N)r r )ri )r! rK r r r write_array_header_2_0 s
rk c C s t | ddS )a
Read an array header from a filelike object using the 1.0 file format
version.
This will leave the file object located just after the header.
Parameters
----------
fp : filelike object
A file object or something with a `.read()` method like a file.
Returns
-------
shape : tuple of int
The shape of the array.
fortran_order : bool
The array data will be written out directly if it is either
C-contiguous or Fortran-contiguous. Otherwise, it will be made
contiguous before writing it out.
dtype : dtype
The dtype of the file's data.
Raises
------
ValueError
If the data is invalid.
r r )r )r r )_read_array_header)r! r r r read_array_header_1_0 s rm c C s t | ddS )a
Read an array header from a filelike object using the 2.0 file format
version.
This will leave the file object located just after the header.
.. versionadded:: 1.9.0
Parameters
----------
fp : filelike object
A file object or something with a `.read()` method like a file.
Returns
-------
shape : tuple of int
The shape of the array.
fortran_order : bool
The array data will be written out directly if it is either
C-contiguous or Fortran-contiguous. Otherwise, it will be made
contiguous before writing it out.
dtype : dtype
The dtype of the file's data.
Raises
------
ValueError
If the data is invalid.
r r )r )r r )rl )r! r r r read_array_header_2_0 s rn c C s~ ddl }ddlm} g }d}xV|j|| jD ]B}|d }|d }|r\||jkr\|dkr\q.n
|j| ||jk}q.W |j|S )a6 Clean up 'L' in npz header ints.
Cleans up the 'L' in strings representing integers. Needed to allow npz
headers produced in Python2 to be read in Python3.
Parameters
----------
s : string
Npy file header.
Returns
-------
header : str
Cleaned up header.
r N)StringIOFr L) tokenizeioro generate_tokensreadlineNAMEr@ NUMBER
untokenize)srq ro tokensZlast_token_was_numbertoken
token_typeZ token_stringr r r re s
re c C s ddl }tj|}|dkr(tdj||\}}t| |j|d}|j||d }t| |d}|j|}t |}y t
|} W n6 t k
r }
zd} t| j||
W Y dd}
~
X nX t | t
sd} t| j| t| j } | dd d
gkrd } t| j| t | d
t s*tjd d
| d
D r@d} t| j| d
t | d tsfd} t| j| d yt| d }
W n, tk
r d} t| j| d Y nX | d
| d |
fS )z#
see read_array_header_1_0
r NzInvalid version {!r}zarray header lengthz array headerz)Cannot parse header: {!r}
Exception: {!r}z Header is not a dictionary: {!r}r0 rF rD z.Header does not contain the correct keys: {!r}c S s g | ]}t |tqS r )r9 int)r$ xr r r
U s z&_read_array_header..zshape is not valid: {!r}z'fortran_order is not a valid bool: {!r}z+descr is not a valid dtype descriptor: {!r})rO rQ getr rW r rT unpackdecodere r SyntaxErrorr9 dictra keysr; r: allboolr< TypeError)r! r rO ZhinfoZ hlength_typerZ Z hlength_str
header_lengthrX rK er r r2 r r r rl . sF
"
rl Tc C s t | t| t|| |jdkr(d}ntd|j d}|jjrr|sLtd|dkrXi }tj || fdd i| n|j
j r|j
j rt
| r|jj| n2xztj|d
d d g|d
dD ]}| j|jd qW nHt
| r|j| n4x2tj|d
d d g|ddD ]}| j|jd qW dS )a'
Write an array to an NPY file, including a header.
If the array is neither C-contiguous nor Fortran-contiguous AND the
file_like object is not a real file object, this function will have to
copy data in memory.
Parameters
----------
fp : file_like object
An open, writable file object, or similar object with a
``.write()`` method.
array : ndarray
The array to write to disk.
version : (int, int) or None, optional
The version number of the format. None means use the oldest
supported version that is able to store the data. Default: None
allow_pickle : bool, optional
Whether to allow writing pickled data. Default: True
pickle_kwargs : dict, optional
Additional keyword arguments to pass to pickle.dump, excluding
'protocol'. These are only useful when pickling objects in object
arrays on Python 3 to Python 2 compatible format.
Raises
------
ValueError
If the array cannot be persisted. This includes the case of
allow_pickle=False and array being an object array.
Various other errors
If the array contains Python objects as part of its dtype, the
process of pickling them may raise various errors if the objects
are not picklable.
r i r r z5Object arrays cannot be saved when allow_pickle=FalseNprotocolr
Z
external_loopZbufferedZ zerosize_okF)rG
buffersizeorderCi i )r ri rL r8 maxr2 hasobjectr r dumprG rI rH r Ttofiler: Znditerrf tobytes)r! rJ r allow_pickle
pickle_kwargsr chunkr r r write_arrayc s0 $
r Fc C sp t | }t| t| |\}}}t|dkr2d}ntjj|tjd}|jr|sVt d|dkrbi }yt
j | f|}W n0 t k
r } zt d| f W Y dd} ~ X nX nt
| rtj| ||d}ntj||d}|jdkrFttt|j }
xXtd||
D ]H} t|
|| } t| |j }
t| |
d}tj||| d|| | | < qW |rf|ddd |_|j }n||_|S )
a!
Read an array from an NPY file.
Parameters
----------
fp : file_like object
If this is not a real file object, then this may take extra memory
and time.
allow_pickle : bool, optional
Whether to allow writing pickled data. Default: False
.. versionchanged:: 1.16.3
Made default False in response to CVE-2019-6446.
pickle_kwargs : dict
Additional keyword arguments to pass to pickle.load. These are only
useful when loading object arrays saved on Python 2 when using
Python 3.
Returns
-------
array : ndarray
The array from the data on disk.
Raises
------
ValueError
If the data is invalid, or allow_pickle=False and the file contains
an object array.
r r )r2 z6Object arrays cannot be loaded when allow_pickle=FalseNz]Unpickling a python object failed: %r
You may need to pass the encoding= option to numpy.load)r2 countz
array data)r" r rl r= r: multiplyreduceZint64r r r load UnicodeErrorr fromfileZndarrayr8 BUFFER_SIZEminranger| r Z
frombufferrD Z transpose)r! r r r rD rF r2 r rJ errZmax_read_countiZ
read_count read_sizedatar r r
read_array s@
r r+c C s
t | rtdd|krt| tj|}|jr 2
r ran out of datac C s t }xTy8| j|t| }||7 }t|dksP W q tjk
rV Y qX qW t||krd}t|||t|f n|S dS )a+
Read from file-like object until size bytes are read.
Raises ValueError if not EOF is encountered before size bytes are read.
Non-blocking objects only supported if they derive from io objects.
Required as e.g. ZipExtFile in python 2.6 can return less data than
requested.
r z)EOF: reading %s, expected %d bytes got %dN)r readr= rr BlockingIOErrorr )r! sizeerror_templater rr r r r r m s
r i )r r )r
r )r r )r r )r
r )r r )N)NTN)FN)r NNFN)r )%__doc__r: rr r- Znumpy.lib.utilsr Z numpy.compatr r r __all__r r= r rS r rQ r r r" r# r3 r< rL r[ r^ ri rj rk rm rn re rl r r r r r r r r sD
$,
"#5
H
]
d