Current File : //proc/self/root/proc/self/root/lib64/python2.7/site-packages/numpy/lib/format.pyc
�
E�`Qc@s�dZddlZddlZddlZddlmZddlmZmZed�Z	e
e	�dZd�Zd�Z
d	�Zd
�Zd�Zd�Zdd�Zd�Zdddedd�ZdS(s`
Define 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 create a solution in his 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 length of
``magic string + 4 + HEADER_LEN`` be evenly divisible by 16 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``.

Notes
-----
The ``.npy`` format, including reasons for creating it and a comparison of
alternatives, is described fully in the "npy-format" NEP.

i����N(t	safe_eval(tasbytest	isfileobjs�NUMPYicCs�|dks|dkr'td��n|dks?|dkrNtd��ntjddkrytt|�t|�Stt||g�SdS(s
 Return the magic string for the given file format version.

    Parameters
    ----------
    major : int in [0, 255]
    minor : int in [0, 255]

    Returns
    -------
    magic : str

    Raises
    ------
    ValueError if the version cannot be formatted.
    ii�s&major version must be 0 <= major < 256s&minor version must be 0 <= minor < 256iN(t
ValueErrortsystversion_infotMAGIC_PREFIXtchrtbytes(tmajortminor((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pytmagic�scCs�|jt�}t|�tkr@d}t|t|f��n|d tkrsd}t|t|d f��ntjddkr�tt|d�\}}n|d\}}||fS(s� Read the magic string to get the version of the file format.

    Parameters
    ----------
    fp : filelike object

    Returns
    -------
    major : int
    minor : int
    s9could not read %d characters for the magic string; got %ri����s4the magic string is not correct; expected %r, got %rii(	treadt	MAGIC_LENtlenRRRRtmaptord(tfpt	magic_strtmsgR	R
((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pyt
read_magic�scCs!|jdk	r|jS|jSdS(s�
    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.

    N(tnamestNonetdescrtstr(tdtype((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pytdtype_to_descr�scCsfi}|j|d<|jjr,t|d<n#|jjrEt|d<n
t|d<t|j�|d<|S(s Get the dictionary of header metadata from a numpy.ndarray.

    Parameters
    ----------
    array : numpy.ndarray

    Returns
    -------
    d : dict
        This has the appropriate entries for writing its string representation
        to the header of the file.
    tshapet
fortran_orderR(Rtflagstc_contiguoustFalsetf_contiguoustTrueRR(tarraytd((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pytheader_data_from_array_1_0�s




c	Cs
ddl}dg}x=t|j��D])\}}|jd|t|�f�q(W|jd�dj|�}tdt|�d}d	|d	}t|d
|d�}t|�dkr�t	d
d��n|j
dt|��}|j|�|j|�dS(s� 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.
    i����Nt{s
'%s': %s, t}tiiit s
is#header does not fit inside %s bytess<Hii(tstructtsortedtitemstappendtreprtjoinR
RRRtpacktwrite(	RR#R)theadertkeytvaluetcurrent_header_lenttopadtheader_len_str((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pytwrite_array_header_1_0s
	!

cCsIddl}|jd�}t|�dkrLd}t||j���n|jd|�d}|j|�}t|�|kr�td|j���nyt|�}Wn/tk
r�}d}t|||f��nXt|t	�sd	}t||��n|j
�}|j�|d
ddgkrMd
}t||f��nt|dt�s�t
jg|dD]}	t|	ttf�^qr�r�d}t||df��nt|dt�s�d}t||df��nyt
j|d
�}
Wn0tk
r3}d}t||d
f��nX|d|d|
fS(s�
    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.

    i����Nis,EOF at %s before reading array header lengths<His%EOF at %s before reading array headers%Cannot parse header: %r
Exception: %rsHeader is not a dictionary: %rRRRs,Header does not contain the correct keys: %rsshape is not valid: %rs%fortran_order is not a valid bool: %rs)descr is not a valid dtype descriptor: %r(R)RRRttelltunpackRtSyntaxErrort
isinstancetdicttkeystsortttupletnumpytalltinttlongtboolRt	TypeError(RR)thlength_strRt
header_lengthR1R#teR=txR((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pytread_array_header_1_0 sF
6iicCs�|dkr(d}t||f��n|jt|��t|t|��|jjrstj||dd�n�|j	j
r�|j	jr�t|�r�|j
j|�q�|j|j
jd��n2t|�r�|j|�n|j|jd��dS(	s*
    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), optional
        The version number of the format.  Default: (1, 0)

    Raises
    ------
    ValueError
        If the array cannot be persisted.
    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.

    iis,we only support format version (1,0), not %stprotocolitCN(ii(RR0RR7R$Rt	hasobjecttcPickletdumpRR RRtTttofilettostring(RR"tversionR((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pytwrite_arraymsc	Cs*t|�}|dkr4d}t||f��nt|�\}}}t|�dkrdd}ntjj|�}|jr�tj	|�}n�t
|�r�tj|d|d|�}n7|jt
||j��}tj|d|d|�}|r|ddd�|_|j�}n	||_|S(	s\
    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.

    Returns
    -------
    array : ndarray
        The array from the data on disk.

    Raises
    ------
    ValueError
        If the data is invalid.

    iis1only support version (1,0) of file format, not %rRtcountNi����(ii(RRRJRR@tmultiplytreduceRMRNtloadRtfromfileRRBtitemsizet
fromstringRt	transpose(	RRSRRRRRUR"tdata((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pyt
read_array�s&			sr+cCs�t|t�std��nd|kr�|dkrRd}t||f��ntj|�}|jrd}t|��ntdt|�d|d	|�}t||d
�}z0|j	t
|��t||�|j�}	Wd|j
�Xn�t|d�}zwt|�}|dkr:d}t||f��nt|�\}}}|jrmd}t|��n|j�}	Wd|j
�X|r�d
}
nd}
|dkr�d}ntj|d|d	|d|
d|d|	�}|S(s6
    Open a .npy file as a memory-mapped array.

    This may be used to read an existing file or create a new one.

    Parameters
    ----------
    filename : str
        The name of the file on disk.  This may *not* be a file-like
        object.
    mode : str, optional
        The mode in which to open the file; the default is 'r+'.  In
        addition to the standard file modes, 'c' is also accepted to
        mean "copy on write."  See `memmap` for the available mode strings.
    dtype : data-type, optional
        The data type of the array if we are creating a new file in "write"
        mode, if not, `dtype` is ignored.  The default value is None,
        which results in a data-type of `float64`.
    shape : tuple of int
        The shape of the array if we are creating a new file in "write"
        mode, in which case this parameter is required.  Otherwise, this
        parameter is ignored and is thus optional.
    fortran_order : bool, optional
        Whether the array should be Fortran-contiguous (True) or
        C-contiguous (False, the default) if we are creating a new file
        in "write" mode.
    version : tuple of int (major, minor)
        If the mode is a "write" mode, then this is the version of the file
        format used to create the file.  Default: (1,0)

    Returns
    -------
    marray : memmap
        The memory-mapped array.

    Raises
    ------
    ValueError
        If the data or the mode is invalid.
    IOError
        If the file is not found or cannot be opened correctly.

    See Also
    --------
    memmap

    sDFilename must be a string.  Memmap cannot use existing file handles.twiis1only support version (1,0) of file format, not %rs6Array can't be memory-mapped: Python objects in dtype.RRRtbNtrbtFRLsw+sr+Rtordertmodetoffset(ii(ii(R;t
basestringRR@RRMR<RtopenR0RR7R8tcloseRRJtmemmap(tfilenameRdRRRRSRR#RReRctmarray((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pytopen_memmap�sP1		
			(ii(ii(t__doc__RNR@Rtnumpy.lib.utilsRtnumpy.compatRRRRR
RRRR$R7RJRTR^RRRl(((s6/usr/lib64/python2.7/site-packages/numpy/lib/format.pyt<module>�s"			 			M2	7