# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2017, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR , 2017.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.6\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2018-05-26 11:10+0900\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME \n"
"Language-Team: LANGUAGE \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.5.1\n"
#: ../Doc/c-api/buffer.rst:11
msgid "Buffer Protocol"
msgstr ""
#: ../Doc/c-api/buffer.rst:18
msgid ""
"Certain objects available in Python wrap access to an underlying memory "
"array or *buffer*. Such objects include the built-in :class:`bytes` and "
":class:`bytearray`, and some extension types like :class:`array.array`. "
"Third-party libraries may define their own types for special purposes, "
"such as image processing or numeric analysis."
msgstr ""
#: ../Doc/c-api/buffer.rst:24
msgid ""
"While each of these types have their own semantics, they share the common"
" characteristic of being backed by a possibly large memory buffer. It is"
" then desirable, in some situations, to access that buffer directly and "
"without intermediate copying."
msgstr ""
#: ../Doc/c-api/buffer.rst:29
msgid ""
"Python provides such a facility at the C level in the form of the "
":ref:`buffer protocol `. This protocol has two sides:"
msgstr ""
#: ../Doc/c-api/buffer.rst:34
msgid ""
"on the producer side, a type can export a \"buffer interface\" which "
"allows objects of that type to expose information about their underlying "
"buffer. This interface is described in the section :ref:`buffer-structs`;"
msgstr ""
#: ../Doc/c-api/buffer.rst:38
msgid ""
"on the consumer side, several means are available to obtain a pointer to "
"the raw underlying data of an object (for example a method parameter)."
msgstr ""
#: ../Doc/c-api/buffer.rst:41
msgid ""
"Simple objects such as :class:`bytes` and :class:`bytearray` expose their"
" underlying buffer in byte-oriented form. Other forms are possible; for "
"example, the elements exposed by an :class:`array.array` can be multi-"
"byte values."
msgstr ""
#: ../Doc/c-api/buffer.rst:45
msgid ""
"An example consumer of the buffer interface is the "
":meth:`~io.BufferedIOBase.write` method of file objects: any object that "
"can export a series of bytes through the buffer interface can be written "
"to a file. While :meth:`write` only needs read-only access to the "
"internal contents of the object passed to it, other methods such as "
":meth:`~io.BufferedIOBase.readinto` need write access to the contents of "
"their argument. The buffer interface allows objects to selectively allow"
" or reject exporting of read-write and read-only buffers."
msgstr ""
#: ../Doc/c-api/buffer.rst:53
msgid ""
"There are two ways for a consumer of the buffer interface to acquire a "
"buffer over a target object:"
msgstr ""
#: ../Doc/c-api/buffer.rst:56
msgid "call :c:func:`PyObject_GetBuffer` with the right parameters;"
msgstr ""
#: ../Doc/c-api/buffer.rst:58
msgid ""
"call :c:func:`PyArg_ParseTuple` (or one of its siblings) with one of the "
"``y*``, ``w*`` or ``s*`` :ref:`format codes `."
msgstr ""
#: ../Doc/c-api/buffer.rst:61
msgid ""
"In both cases, :c:func:`PyBuffer_Release` must be called when the buffer "
"isn't needed anymore. Failure to do so could lead to various issues such"
" as resource leaks."
msgstr ""
#: ../Doc/c-api/buffer.rst:69
msgid "Buffer structure"
msgstr ""
#: ../Doc/c-api/buffer.rst:71
msgid ""
"Buffer structures (or simply \"buffers\") are useful as a way to expose "
"the binary data from another object to the Python programmer. They can "
"also be used as a zero-copy slicing mechanism. Using their ability to "
"reference a block of memory, it is possible to expose any data to the "
"Python programmer quite easily. The memory could be a large, constant "
"array in a C extension, it could be a raw block of memory for "
"manipulation before passing to an operating system library, or it could "
"be used to pass around structured data in its native, in-memory format."
msgstr ""
#: ../Doc/c-api/buffer.rst:80
msgid ""
"Contrary to most data types exposed by the Python interpreter, buffers "
"are not :c:type:`PyObject` pointers but rather simple C structures. This"
" allows them to be created and copied very simply. When a generic "
"wrapper around a buffer is needed, a :ref:`memoryview ` object can be created."
msgstr ""
#: ../Doc/c-api/buffer.rst:86
msgid ""
"For short instructions how to write an exporting object, see :ref:`Buffer"
" Object Structures `. For obtaining a buffer, see "
":c:func:`PyObject_GetBuffer`."
msgstr ""
#: ../Doc/c-api/buffer.rst:94
msgid ""
"A pointer to the start of the logical structure described by the buffer "
"fields. This can be any location within the underlying physical memory "
"block of the exporter. For example, with negative "
":c:member:`~Py_buffer.strides` the value may point to the end of the "
"memory block."
msgstr ""
#: ../Doc/c-api/buffer.rst:99
msgid ""
"For :term:`contiguous` arrays, the value points to the beginning of the "
"memory block."
msgstr ""
#: ../Doc/c-api/buffer.rst:104
msgid ""
"A new reference to the exporting object. The reference is owned by the "
"consumer and automatically decremented and set to *NULL* by "
":c:func:`PyBuffer_Release`. The field is the equivalent of the return "
"value of any standard C-API function."
msgstr ""
#: ../Doc/c-api/buffer.rst:109
msgid ""
"As a special case, for *temporary* buffers that are wrapped by "
":c:func:`PyMemoryView_FromBuffer` or :c:func:`PyBuffer_FillInfo` this "
"field is *NULL*. In general, exporting objects MUST NOT use this scheme."
msgstr ""
#: ../Doc/c-api/buffer.rst:116
msgid ""
"``product(shape) * itemsize``. For contiguous arrays, this is the length "
"of the underlying memory block. For non-contiguous arrays, it is the "
"length that the logical structure would have if it were copied to a "
"contiguous representation."
msgstr ""
#: ../Doc/c-api/buffer.rst:121
msgid ""
"Accessing ``((char *)buf)[0] up to ((char *)buf)[len-1]`` is only valid "
"if the buffer has been obtained by a request that guarantees contiguity. "
"In most cases such a request will be :c:macro:`PyBUF_SIMPLE` or "
":c:macro:`PyBUF_WRITABLE`."
msgstr ""
#: ../Doc/c-api/buffer.rst:127
msgid ""
"An indicator of whether the buffer is read-only. This field is controlled"
" by the :c:macro:`PyBUF_WRITABLE` flag."
msgstr ""
#: ../Doc/c-api/buffer.rst:132
msgid ""
"Item size in bytes of a single element. Same as the value of "
":func:`struct.calcsize` called on non-NULL :c:member:`~Py_buffer.format` "
"values."
msgstr ""
#: ../Doc/c-api/buffer.rst:135
msgid ""
"Important exception: If a consumer requests a buffer without the "
":c:macro:`PyBUF_FORMAT` flag, :c:member:`~Py_buffer.format` will be set "
"to *NULL*, but :c:member:`~Py_buffer.itemsize` still has the value for "
"the original format."
msgstr ""
#: ../Doc/c-api/buffer.rst:140
msgid ""
"If :c:member:`~Py_buffer.shape` is present, the equality ``product(shape)"
" * itemsize == len`` still holds and the consumer can use "
":c:member:`~Py_buffer.itemsize` to navigate the buffer."
msgstr ""
#: ../Doc/c-api/buffer.rst:144
msgid ""
"If :c:member:`~Py_buffer.shape` is *NULL* as a result of a "
":c:macro:`PyBUF_SIMPLE` or a :c:macro:`PyBUF_WRITABLE` request, the "
"consumer must disregard :c:member:`~Py_buffer.itemsize` and assume "
"``itemsize == 1``."
msgstr ""
#: ../Doc/c-api/buffer.rst:150
msgid ""
"A *NUL* terminated string in :mod:`struct` module style syntax describing"
" the contents of a single item. If this is *NULL*, ``\"B\"`` (unsigned "
"bytes) is assumed."
msgstr ""
#: ../Doc/c-api/buffer.rst:154
msgid "This field is controlled by the :c:macro:`PyBUF_FORMAT` flag."
msgstr ""
#: ../Doc/c-api/buffer.rst:158
msgid ""
"The number of dimensions the memory represents as an n-dimensional array."
" If it is ``0``, :c:member:`~Py_buffer.buf` points to a single item "
"representing a scalar. In this case, :c:member:`~Py_buffer.shape`, "
":c:member:`~Py_buffer.strides` and :c:member:`~Py_buffer.suboffsets` MUST"
" be *NULL*."
msgstr ""
#: ../Doc/c-api/buffer.rst:163
msgid ""
"The macro :c:macro:`PyBUF_MAX_NDIM` limits the maximum number of "
"dimensions to 64. Exporters MUST respect this limit, consumers of multi-"
"dimensional buffers SHOULD be able to handle up to "
":c:macro:`PyBUF_MAX_NDIM` dimensions."
msgstr ""
#: ../Doc/c-api/buffer.rst:169
msgid ""
"An array of :c:type:`Py_ssize_t` of length :c:member:`~Py_buffer.ndim` "
"indicating the shape of the memory as an n-dimensional array. Note that "
"``shape[0] * ... * shape[ndim-1] * itemsize`` MUST be equal to "
":c:member:`~Py_buffer.len`."
msgstr ""
#: ../Doc/c-api/buffer.rst:174
msgid ""
"Shape values are restricted to ``shape[n] >= 0``. The case ``shape[n] == "
"0`` requires special attention. See `complex arrays`_ for further "
"information."
msgstr ""
#: ../Doc/c-api/buffer.rst:178
msgid "The shape array is read-only for the consumer."
msgstr ""
#: ../Doc/c-api/buffer.rst:182
msgid ""
"An array of :c:type:`Py_ssize_t` of length :c:member:`~Py_buffer.ndim` "
"giving the number of bytes to skip to get to a new element in each "
"dimension."
msgstr ""
#: ../Doc/c-api/buffer.rst:186
msgid ""
"Stride values can be any integer. For regular arrays, strides are usually"
" positive, but a consumer MUST be able to handle the case ``strides[n] = 0``, the values stored along the nth dimension are "
"pointers and the suboffset value dictates how many bytes to add to each "
"pointer after de-referencing. A suboffset value that is negative "
"indicates that no de-referencing should occur (striding in a contiguous "
"memory block)."
msgstr ""
#: ../Doc/c-api/buffer.rst:201
msgid ""
"If all suboffsets are negative (i.e. no de-referencing is needed, then "
"this field must be NULL (the default value)."
msgstr ""
#: ../Doc/c-api/buffer.rst:204
msgid ""
"This type of array representation is used by the Python Imaging Library "
"(PIL). See `complex arrays`_ for further information how to access "
"elements of such an array."
msgstr ""
#: ../Doc/c-api/buffer.rst:208
msgid "The suboffsets array is read-only for the consumer."
msgstr ""
#: ../Doc/c-api/buffer.rst:212
msgid ""
"This is for use internally by the exporting object. For example, this "
"might be re-cast as an integer by the exporter and used to store flags "
"about whether or not the shape, strides, and suboffsets arrays must be "
"freed when the buffer is released. The consumer MUST NOT alter this "
"value."
msgstr ""
#: ../Doc/c-api/buffer.rst:221
msgid "Buffer request types"
msgstr ""
#: ../Doc/c-api/buffer.rst:223
msgid ""
"Buffers are usually obtained by sending a buffer request to an exporting "
"object via :c:func:`PyObject_GetBuffer`. Since the complexity of the "
"logical structure of the memory can vary drastically, the consumer uses "
"the *flags* argument to specify the exact buffer type it can handle."
msgstr ""
#: ../Doc/c-api/buffer.rst:228
msgid ""
"All :c:data:`Py_buffer` fields are unambiguously defined by the request "
"type."
msgstr ""
#: ../Doc/c-api/buffer.rst:232
msgid "request-independent fields"
msgstr ""
#: ../Doc/c-api/buffer.rst:233
msgid ""
"The following fields are not influenced by *flags* and must always be "
"filled in with the correct values: :c:member:`~Py_buffer.obj`, "
":c:member:`~Py_buffer.buf`, :c:member:`~Py_buffer.len`, "
":c:member:`~Py_buffer.itemsize`, :c:member:`~Py_buffer.ndim`."
msgstr ""
#: ../Doc/c-api/buffer.rst:239
msgid "readonly, format"
msgstr ""
#: ../Doc/c-api/buffer.rst:243
msgid ""
"Controls the :c:member:`~Py_buffer.readonly` field. If set, the exporter "
"MUST provide a writable buffer or else report failure. Otherwise, the "
"exporter MAY provide either a read-only or writable buffer, but the "
"choice MUST be consistent for all consumers."
msgstr ""
#: ../Doc/c-api/buffer.rst:250
msgid ""
"Controls the :c:member:`~Py_buffer.format` field. If set, this field MUST"
" be filled in correctly. Otherwise, this field MUST be *NULL*."
msgstr ""
#: ../Doc/c-api/buffer.rst:254
msgid ""
":c:macro:`PyBUF_WRITABLE` can be \\|'d to any of the flags in the next "
"section. Since :c:macro:`PyBUF_SIMPLE` is defined as 0, "
":c:macro:`PyBUF_WRITABLE` can be used as a stand-alone flag to request a "
"simple writable buffer."
msgstr ""
#: ../Doc/c-api/buffer.rst:258
msgid ""
":c:macro:`PyBUF_FORMAT` can be \\|'d to any of the flags except "
":c:macro:`PyBUF_SIMPLE`. The latter already implies format ``B`` "
"(unsigned bytes)."
msgstr ""
#: ../Doc/c-api/buffer.rst:263
msgid "shape, strides, suboffsets"
msgstr ""
#: ../Doc/c-api/buffer.rst:265
msgid ""
"The flags that control the logical structure of the memory are listed in "
"decreasing order of complexity. Note that each flag contains all bits of "
"the flags below it."
msgstr ""
#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296
#: ../Doc/c-api/buffer.rst:321
msgid "Request"
msgstr ""
#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296
#: ../Doc/c-api/buffer.rst:321
msgid "shape"
msgstr ""
#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296
#: ../Doc/c-api/buffer.rst:321
msgid "strides"
msgstr ""
#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296
#: ../Doc/c-api/buffer.rst:321
msgid "suboffsets"
msgstr ""
#: ../Doc/c-api/buffer.rst:274 ../Doc/c-api/buffer.rst:276
#: ../Doc/c-api/buffer.rst:278 ../Doc/c-api/buffer.rst:298
#: ../Doc/c-api/buffer.rst:300 ../Doc/c-api/buffer.rst:302
#: ../Doc/c-api/buffer.rst:304 ../Doc/c-api/buffer.rst:323
#: ../Doc/c-api/buffer.rst:325 ../Doc/c-api/buffer.rst:327
#: ../Doc/c-api/buffer.rst:329 ../Doc/c-api/buffer.rst:331
#: ../Doc/c-api/buffer.rst:333 ../Doc/c-api/buffer.rst:335
#: ../Doc/c-api/buffer.rst:337
msgid "yes"
msgstr ""
#: ../Doc/c-api/buffer.rst:274 ../Doc/c-api/buffer.rst:323
#: ../Doc/c-api/buffer.rst:325
msgid "if needed"
msgstr ""
#: ../Doc/c-api/buffer.rst:276 ../Doc/c-api/buffer.rst:278
#: ../Doc/c-api/buffer.rst:280 ../Doc/c-api/buffer.rst:298
#: ../Doc/c-api/buffer.rst:300 ../Doc/c-api/buffer.rst:302
#: ../Doc/c-api/buffer.rst:304 ../Doc/c-api/buffer.rst:327
#: ../Doc/c-api/buffer.rst:329 ../Doc/c-api/buffer.rst:331
#: ../Doc/c-api/buffer.rst:333 ../Doc/c-api/buffer.rst:335
#: ../Doc/c-api/buffer.rst:337
msgid "NULL"
msgstr ""
#: ../Doc/c-api/buffer.rst:287
msgid "contiguity requests"
msgstr ""
#: ../Doc/c-api/buffer.rst:289
msgid ""
"C or Fortran :term:`contiguity ` can be explicitly requested,"
" with and without stride information. Without stride information, the "
"buffer must be C-contiguous."
msgstr ""
#: ../Doc/c-api/buffer.rst:296 ../Doc/c-api/buffer.rst:321
msgid "contig"
msgstr ""
#: ../Doc/c-api/buffer.rst:298 ../Doc/c-api/buffer.rst:304
#: ../Doc/c-api/buffer.rst:335 ../Doc/c-api/buffer.rst:337
msgid "C"
msgstr ""
#: ../Doc/c-api/buffer.rst:300
msgid "F"
msgstr ""
#: ../Doc/c-api/buffer.rst:302
msgid "C or F"
msgstr ""
#: ../Doc/c-api/buffer.rst:309
msgid "compound requests"
msgstr ""
#: ../Doc/c-api/buffer.rst:311
msgid ""
"All possible requests are fully defined by some combination of the flags "
"in the previous section. For convenience, the buffer protocol provides "
"frequently used combinations as single flags."
msgstr ""
#: ../Doc/c-api/buffer.rst:315
msgid ""
"In the following table *U* stands for undefined contiguity. The consumer "
"would have to call :c:func:`PyBuffer_IsContiguous` to determine "
"contiguity."
msgstr ""
#: ../Doc/c-api/buffer.rst:321
msgid "readonly"
msgstr ""
#: ../Doc/c-api/buffer.rst:321
msgid "format"
msgstr ""
#: ../Doc/c-api/buffer.rst:323 ../Doc/c-api/buffer.rst:325
#: ../Doc/c-api/buffer.rst:327 ../Doc/c-api/buffer.rst:329
#: ../Doc/c-api/buffer.rst:331 ../Doc/c-api/buffer.rst:333
msgid "U"
msgstr ""
#: ../Doc/c-api/buffer.rst:323 ../Doc/c-api/buffer.rst:327
#: ../Doc/c-api/buffer.rst:331 ../Doc/c-api/buffer.rst:335
msgid "0"
msgstr ""
#: ../Doc/c-api/buffer.rst:325 ../Doc/c-api/buffer.rst:329
#: ../Doc/c-api/buffer.rst:333 ../Doc/c-api/buffer.rst:337
msgid "1 or 0"
msgstr ""
#: ../Doc/c-api/buffer.rst:342
msgid "Complex arrays"
msgstr ""
#: ../Doc/c-api/buffer.rst:345
msgid "NumPy-style: shape and strides"
msgstr ""
#: ../Doc/c-api/buffer.rst:347
msgid ""
"The logical structure of NumPy-style arrays is defined by "
":c:member:`~Py_buffer.itemsize`, :c:member:`~Py_buffer.ndim`, "
":c:member:`~Py_buffer.shape` and :c:member:`~Py_buffer.strides`."
msgstr ""
#: ../Doc/c-api/buffer.rst:350
msgid ""
"If ``ndim == 0``, the memory location pointed to by "
":c:member:`~Py_buffer.buf` is interpreted as a scalar of size "
":c:member:`~Py_buffer.itemsize`. In that case, both "
":c:member:`~Py_buffer.shape` and :c:member:`~Py_buffer.strides` are "
"*NULL*."
msgstr ""
#: ../Doc/c-api/buffer.rst:354
msgid ""
"If :c:member:`~Py_buffer.strides` is *NULL*, the array is interpreted as "
"a standard n-dimensional C-array. Otherwise, the consumer must access an "
"n-dimensional array as follows:"
msgstr ""
#: ../Doc/c-api/buffer.rst:358
msgid ""
"``ptr = (char *)buf + indices[0] * strides[0] + ... + indices[n-1] * "
"strides[n-1]`` ``item = *((typeof(item) *)ptr);``"
msgstr ""
#: ../Doc/c-api/buffer.rst:362
msgid ""
"As noted above, :c:member:`~Py_buffer.buf` can point to any location "
"within the actual memory block. An exporter can check the validity of a "
"buffer with this function:"
msgstr ""
#: ../Doc/c-api/buffer.rst:396
msgid "PIL-style: shape, strides and suboffsets"
msgstr ""
#: ../Doc/c-api/buffer.rst:398
msgid ""
"In addition to the regular items, PIL-style arrays can contain pointers "
"that must be followed in order to get to the next element in a dimension."
" For example, the regular three-dimensional C-array ``char v[2][2][3]`` "
"can also be viewed as an array of 2 pointers to 2 two-dimensional arrays:"
" ``char (*v[2])[2][3]``. In suboffsets representation, those two pointers"
" can be embedded at the start of :c:member:`~Py_buffer.buf`, pointing to "
"two ``char x[2][3]`` arrays that can be located anywhere in memory."
msgstr ""
#: ../Doc/c-api/buffer.rst:407
msgid ""
"Here is a function that returns a pointer to the element in an N-D array "
"pointed to by an N-dimensional index when there are both non-NULL strides"
" and suboffsets::"
msgstr ""
#: ../Doc/c-api/buffer.rst:426
msgid "Buffer-related functions"
msgstr ""
#: ../Doc/c-api/buffer.rst:430
msgid ""
"Return ``1`` if *obj* supports the buffer interface otherwise ``0``. "
"When ``1`` is returned, it doesn't guarantee that "
":c:func:`PyObject_GetBuffer` will succeed."
msgstr ""
#: ../Doc/c-api/buffer.rst:437
msgid ""
"Send a request to *exporter* to fill in *view* as specified by *flags*. "
"If the exporter cannot provide a buffer of the exact type, it MUST raise "
":c:data:`PyExc_BufferError`, set :c:member:`view->obj` to *NULL* and "
"return ``-1``."
msgstr ""
#: ../Doc/c-api/buffer.rst:442
msgid ""
"On success, fill in *view*, set :c:member:`view->obj` to a new reference "
"to *exporter* and return 0. In the case of chained buffer providers that "
"redirect requests to a single object, :c:member:`view->obj` MAY refer to "
"this object instead of *exporter* (See :ref:`Buffer Object Structures "
"`)."
msgstr ""
#: ../Doc/c-api/buffer.rst:447
msgid ""
"Successful calls to :c:func:`PyObject_GetBuffer` must be paired with "
"calls to :c:func:`PyBuffer_Release`, similar to :c:func:`malloc` and "
":c:func:`free`. Thus, after the consumer is done with the buffer, "
":c:func:`PyBuffer_Release` must be called exactly once."
msgstr ""
#: ../Doc/c-api/buffer.rst:455
msgid ""
"Release the buffer *view* and decrement the reference count for "
":c:member:`view->obj`. This function MUST be called when the buffer is no"
" longer being used, otherwise reference leaks may occur."
msgstr ""
#: ../Doc/c-api/buffer.rst:459
msgid ""
"It is an error to call this function on a buffer that was not obtained "
"via :c:func:`PyObject_GetBuffer`."
msgstr ""
#: ../Doc/c-api/buffer.rst:465
msgid ""
"Return the implied :c:data:`~Py_buffer.itemsize` from "
":c:data:`~Py_buffer.format`. This function is not yet implemented."
msgstr ""
#: ../Doc/c-api/buffer.rst:471
msgid ""
"Return ``1`` if the memory defined by the *view* is C-style (*order* is "
"``'C'``) or Fortran-style (*order* is ``'F'``) :term:`contiguous` or "
"either one (*order* is ``'A'``). Return ``0`` otherwise."
msgstr ""
#: ../Doc/c-api/buffer.rst:478
msgid ""
"Copy *len* bytes from *src* to its contiguous representation in *buf*. "
"*order* can be ``'C'`` or ``'F'`` (for C-style or Fortran-style "
"ordering). ``0`` is returned on success, ``-1`` on error."
msgstr ""
#: ../Doc/c-api/buffer.rst:482
msgid "This function fails if *len* != *src->len*."
msgstr ""
#: ../Doc/c-api/buffer.rst:487
msgid ""
"Fill the *strides* array with byte-strides of a :term:`contiguous` "
"(C-style if *order* is ``'C'`` or Fortran-style if *order* is ``'F'``) "
"array of the given shape with the given number of bytes per element."
msgstr ""
#: ../Doc/c-api/buffer.rst:494
msgid ""
"Handle buffer requests for an exporter that wants to expose *buf* of size"
" *len* with writability set according to *readonly*. *buf* is interpreted"
" as a sequence of unsigned bytes."
msgstr ""
#: ../Doc/c-api/buffer.rst:498
msgid ""
"The *flags* argument indicates the request type. This function always "
"fills in *view* as specified by flags, unless *buf* has been designated "
"as read-only and :c:macro:`PyBUF_WRITABLE` is set in *flags*."
msgstr ""
#: ../Doc/c-api/buffer.rst:502
msgid ""
"On success, set :c:member:`view->obj` to a new reference to *exporter* "
"and return 0. Otherwise, raise :c:data:`PyExc_BufferError`, set "
":c:member:`view->obj` to *NULL* and return ``-1``;"
msgstr ""
#: ../Doc/c-api/buffer.rst:506
msgid ""
"If this function is used as part of a :ref:`getbufferproc `, *exporter* MUST be set to the exporting object and *flags* "
"must be passed unmodified. Otherwise, *exporter* MUST be NULL."
msgstr ""