iframe-proxy | Sunbelt Computer Software

709 lines (610 loc) · 25.6 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2016, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
"Project-Id-Version: Python 3.5\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2016-10-30 10:42+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../Doc/c-api/buffer.rst:11
msgid "Buffer Protocol"
msgstr "Protocole tampon"
#: ../Doc/c-api/buffer.rst:18
"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."
"Certains objets Python enveloppent l'accès à un tableau de mémoire sous-"
"jacente (nommée zone tampon ou simplement tampon, *buffer* en anglais). Les "
"objets natifs :class:`bytes` et :class:`bytearray` en sont des exemples, "
"ainsi que quelques types d'extension comme :class:`array.array`. Les "
"bibliothèques tierces peuvent définir leurs propres types à des fins "
"spéciales, telles que le traitement d'image ou l'analyse numérique."
#: ../Doc/c-api/buffer.rst:24
"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."
"Alors que chacun de ces types a sa propre sémantique, ils partagent la "
"caractéristique commune d'être soutenus par un tampon de mémoire important.  "
"Il est donc souhaitable, dans certains cas, d'accéder à cette mémoire "
"directement sans l'étape intermédiaire de copie."
#: ../Doc/c-api/buffer.rst:29
"Python provides such a facility at the C level in the form of the :ref:"
"`buffer protocol <bufferobjects>`.  This protocol has two sides:"
"Python fournit une telle facilité au niveau du C sous la forme de :ref:"
"`protocole tampon <bufferobjects>`.  Ce protocole comporte deux aspects :"
#: ../Doc/c-api/buffer.rst:34
"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`;"
"du côté producteur, un type peut exporter une \"interface tampon\" qui "
"permet aux objets de ce type d'exposer des informations concernant leur "
"tampon sous-jacent. Cette interface est décrite dans la section :ref:`buffer-"
"structs` ;"
#: ../Doc/c-api/buffer.rst:38
"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)."
"du côté consommateur, plusieurs moyens sont disponibles pour obtenir un "
"pointeur vers les données sous-jacentes brutes d'un objet (par exemple un "
"paramètre de méthode)."
#: ../Doc/c-api/buffer.rst:41
"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 "
"Des objets simples tels que :class:`bytes` et :class:`bytearray` exposent "
"leur tampon sous-jacent dans un format orienté octet. D'autres formes sont "
"possibles ; par exemple, les éléments exposés par un :class:`array.array` "
"peuvent être des valeurs multi-octets."
#: ../Doc/c-api/buffer.rst:45
"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 "
"Un exemple de consommateur de l'interface tampon est la méthode :meth:`~io."
"BufferedIOBase.write` des objets fichiers : tout objet qui peut exporter une "
"série d'octets à travers l'interface tampon peut être écrit dans un fichier. "
"Alors que :meth:`write` n'a besoin que d'un accès  lecture au contenu "
"interne de l'objet qui lui est passé, d'autres méthodes telles que :meth:"
"`~io.BufferedIOBase.readinto` nécessitent un accès écriture au contenu de "
"leur argument. L'interface *buffer* permet aux objets d'autoriser ou de "
"rejeter sélectivement l'exportation de tampons en mode lecture-écriture et "
"en mode lecture seule."
#: ../Doc/c-api/buffer.rst:53
"There are two ways for a consumer of the buffer interface to acquire a "
"buffer over a target object:"
"Un consommateur de l'interface tampon peut acquérir un tampon sur un objet "
"cible de deux manières :"
#: ../Doc/c-api/buffer.rst:56
msgid "call :c:func:`PyObject_GetBuffer` with the right parameters;"
msgstr "appelez :c:func:`PyObject_GetBuffer` avec les paramètres appropriés ;"
#: ../Doc/c-api/buffer.rst:58
"call :c:func:`PyArg_ParseTuple` (or one of its siblings) with one of the "
"``y*``, ``w*`` or ``s*`` :ref:`format codes <arg-parsing>`."
"appelez :c:func:`PyArg_ParseTuple` (ou l'un de ses fonctions sœurs) avec "
"l'un des ``y*``, ``w*`` ou ``s*``  :ref:`format codes <arg-parsing>`."
#: ../Doc/c-api/buffer.rst:61
"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."
"Dans les deux cas, :c:func:`PyBuffer_Release` doit être appelée quand le "
"tampon n'est plus nécessaire. Ne pas le faire peut conduire à divers "
"problèmes tels que des fuites de ressources."
#: ../Doc/c-api/buffer.rst:69
msgid "Buffer structure"
msgstr "La structure *buffer*"
#: ../Doc/c-api/buffer.rst:71
"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."
"Les structures tampons (ou simplement les \"tampons\", *buffers* en anglais) "
"sont utiles pour exposer les données binaires d'un autre objet au "
"programmeur Python. Elles peuvent également être utilisées comme un "
"mécanisme de découpage sans copie. En utilisant leur capacité à référencer "
"un bloc de mémoire, il est possible d'exposer toutes les données au "
"programmeur Python assez facilement. La mémoire peut être un grand tableau "
"constant dans une extension C, il peut s'agir d'un bloc brut de mémoire à "
"manipuler avant de passer à une bibliothèque de système d'exploitation ou "
"être utilisé pour transmettre des données structurées dans son format natif "
"en mémoire."
#: ../Doc/c-api/buffer.rst:80
"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 <memoryview-objects>` object can be "
"Contrairement à la plupart des types de données exposés par l'interpréteur "
"Python, les tampons ne sont pas de simples pointeurs vers :c:type:`PyObject` "
"mais plutôt des structures C simples. Cela leur permet d'être créés et "
"copiés très simplement. lorsque vous avez besoin d'une enveloppe générique "
"(*wrapper* en anglais) pour un tampon, un objet :ref:`memoryview <memoryview-"
"objects>` peut être créé."
#: ../Doc/c-api/buffer.rst:86
"For short instructions how to write an exporting object, see :ref:`Buffer "
"Object Structures <buffer-structs>`. For obtaining a buffer, see :c:func:"
"`PyObject_GetBuffer`."
#: ../Doc/c-api/buffer.rst:94
"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."
#: ../Doc/c-api/buffer.rst:99
"For :term:`contiguous` arrays, the value points to the beginning of the "
"memory block."
#: ../Doc/c-api/buffer.rst:104
"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."
#: ../Doc/c-api/buffer.rst:109
"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."
#: ../Doc/c-api/buffer.rst:116
"``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."
#: ../Doc/c-api/buffer.rst:121
"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`."
#: ../Doc/c-api/buffer.rst:127
"An indicator of whether the buffer is read-only. This field is controlled by "
"the :c:macro:`PyBUF_WRITABLE` flag."
#: ../Doc/c-api/buffer.rst:132
"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."
#: ../Doc/c-api/buffer.rst:135
"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 "
#: ../Doc/c-api/buffer.rst:140
"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."
#: ../Doc/c-api/buffer.rst:144
"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``."
#: ../Doc/c-api/buffer.rst:150
"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."
#: ../Doc/c-api/buffer.rst:154
msgid "This field is controlled by the :c:macro:`PyBUF_FORMAT` flag."
#: ../Doc/c-api/buffer.rst:158
"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*."
#: ../Doc/c-api/buffer.rst:163
"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."
#: ../Doc/c-api/buffer.rst:169
"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`."
#: ../Doc/c-api/buffer.rst:174
"Shape values are restricted to ``shape[n] >= 0``. The case ``shape[n] == 0`` "
"requires special attention. See `complex arrays`_ for further information."
#: ../Doc/c-api/buffer.rst:178
msgid "The shape array is read-only for the consumer."
#: ../Doc/c-api/buffer.rst:182
"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."
#: ../Doc/c-api/buffer.rst:186
"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``. See `complex arrays`_ for further information."
#: ../Doc/c-api/buffer.rst:190
msgid "The strides array is read-only for the consumer."
#: ../Doc/c-api/buffer.rst:194
"An array of :c:type:`Py_ssize_t` of length :c:member:`~Py_buffer.ndim`. If "
"``suboffsets[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)."
#: ../Doc/c-api/buffer.rst:201
"If all suboffsets are negative (i.e. no de-referencing is needed, then this "
"field must be NULL (the default value)."
#: ../Doc/c-api/buffer.rst:204
"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."
#: ../Doc/c-api/buffer.rst:208
msgid "The suboffsets array is read-only for the consumer."
#: ../Doc/c-api/buffer.rst:212
"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."
#: ../Doc/c-api/buffer.rst:221
msgid "Buffer request types"
#: ../Doc/c-api/buffer.rst:223
"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."
#: ../Doc/c-api/buffer.rst:228
"All :c:data:`Py_buffer` fields are unambiguously defined by the request type."
#: ../Doc/c-api/buffer.rst:232
msgid "request-independent fields"
#: ../Doc/c-api/buffer.rst:233
"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`."
#: ../Doc/c-api/buffer.rst:239
msgid "readonly, format"
#: ../Doc/c-api/buffer.rst:243
"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."
#: ../Doc/c-api/buffer.rst:250
"Controls the :c:member:`~Py_buffer.format` field. If set, this field MUST be "
"filled in correctly. Otherwise, this field MUST be *NULL*."
#: ../Doc/c-api/buffer.rst:254
":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."
#: ../Doc/c-api/buffer.rst:258
":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)."
#: ../Doc/c-api/buffer.rst:263
msgid "shape, strides, suboffsets"
#: ../Doc/c-api/buffer.rst:265
"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."
#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296
#: ../Doc/c-api/buffer.rst:321
msgid "Request"
#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296
#: ../Doc/c-api/buffer.rst:321
msgid "shape"
#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296
#: ../Doc/c-api/buffer.rst:321
msgid "strides"
#: ../Doc/c-api/buffer.rst:272 ../Doc/c-api/buffer.rst:296
#: ../Doc/c-api/buffer.rst:321
msgid "suboffsets"
#: ../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 "oui"
#: ../Doc/c-api/buffer.rst:274 ../Doc/c-api/buffer.rst:323
#: ../Doc/c-api/buffer.rst:325
msgid "if needed"
#: ../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"
#: ../Doc/c-api/buffer.rst:287
msgid "contiguity requests"
#: ../Doc/c-api/buffer.rst:289
"C or Fortran :term:`contiguity <contiguous>` can be explicitly requested, "
"with and without stride information. Without stride information, the buffer "
"must be C-contiguous."
#: ../Doc/c-api/buffer.rst:296 ../Doc/c-api/buffer.rst:321
msgid "contig"
#: ../Doc/c-api/buffer.rst:298 ../Doc/c-api/buffer.rst:304
#: ../Doc/c-api/buffer.rst:335 ../Doc/c-api/buffer.rst:337
#: ../Doc/c-api/buffer.rst:300
#: ../Doc/c-api/buffer.rst:302
msgid "C or F"
#: ../Doc/c-api/buffer.rst:309
msgid "compound requests"
#: ../Doc/c-api/buffer.rst:311
"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."
#: ../Doc/c-api/buffer.rst:315
"In the following table *U* stands for undefined contiguity. The consumer "
"would have to call :c:func:`PyBuffer_IsContiguous` to determine contiguity."
#: ../Doc/c-api/buffer.rst:321
msgid "readonly"
#: ../Doc/c-api/buffer.rst:321
msgid "format"
msgstr "format"
#: ../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:323 ../Doc/c-api/buffer.rst:327
#: ../Doc/c-api/buffer.rst:331 ../Doc/c-api/buffer.rst:335
#: ../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"
#: ../Doc/c-api/buffer.rst:342
msgid "Complex arrays"
#: ../Doc/c-api/buffer.rst:345
msgid "NumPy-style: shape and strides"
#: ../Doc/c-api/buffer.rst:347
"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`."
#: ../Doc/c-api/buffer.rst:350
"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*."
#: ../Doc/c-api/buffer.rst:354
"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:"
#: ../Doc/c-api/buffer.rst:358
"``ptr = (char *)buf + indices[0] * strides[0] + ... + indices[n-1] * "
"strides[n-1]`` ``item = *((typeof(item) *)ptr);``"
#: ../Doc/c-api/buffer.rst:362
"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:"
#: ../Doc/c-api/buffer.rst:396
msgid "PIL-style: shape, strides and suboffsets"
#: ../Doc/c-api/buffer.rst:398
"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."
#: ../Doc/c-api/buffer.rst:407
"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::"
#: ../Doc/c-api/buffer.rst:426
msgid "Buffer-related functions"
msgstr "Fonctions relatives aux tampons"
#: ../Doc/c-api/buffer.rst:430
"Return 1 if *obj* supports the buffer interface otherwise 0.  When 1 is "
"returned, it doesn't guarantee that :c:func:`PyObject_GetBuffer` will "
#: ../Doc/c-api/buffer.rst:437
"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."
#: ../Doc/c-api/buffer.rst:442
"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 "
"<buffer-structs>`)."
#: ../Doc/c-api/buffer.rst:447
"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."
#: ../Doc/c-api/buffer.rst:455
"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."
#: ../Doc/c-api/buffer.rst:459
"It is an error to call this function on a buffer that was not obtained via :"
"c:func:`PyObject_GetBuffer`."
#: ../Doc/c-api/buffer.rst:465
"Return the implied :c:data:`~Py_buffer.itemsize` from :c:data:`~Py_buffer."
"format`. This function is not yet implemented."
#: ../Doc/c-api/buffer.rst:471
"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."
#: ../Doc/c-api/buffer.rst:478
"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."
#: ../Doc/c-api/buffer.rst:485
"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."
#: ../Doc/c-api/buffer.rst:489
"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*."
#: ../Doc/c-api/buffer.rst:493
"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;"
#: ../Doc/c-api/buffer.rst:497
"If this function is used as part of a :ref:`getbufferproc <buffer-structs>`, "
"*exporter* MUST be set to the exporting object and *flags* must be passed "
"unmodified. Otherwise, *exporter* MUST be NULL."
Sunbelt Computer Software

PL/B Language Development and Support

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sunbelt Computer Software

PL/B Language Development and Support

FilesExpand file tree

buffer.po

Latest commit

History

buffer.po

File metadata and controls
