forked from AFPy/python-docs-fr
Make merge (#894)
This commit is contained in:
parent 8b86075fd5
commit dcd871ae78
81 changed files with 10346 additions and 9121 deletions
| | @ -5,7 +5,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2019-09-04 11:33+0200\n" | ||||
"POT-Creation-Date: 2019-10-09 17:54+0200\n" | ||||
"PO-Revision-Date: 2018-10-04 12:18+0200\n" | ||||
"Last-Translator: \n" | ||||
"Language-Team: FRENCH <traductions@lists.afpy.org>\n" | ||||
| | @ -676,44 +676,51 @@ msgstr "" | |||
| ||||
#: ../Doc/c-api/buffer.rst:486 | ||||
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." | ||||
"Copy contiguous *len* bytes from *buf* to *view*. *fort* 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:490 | ||||
#: ../Doc/c-api/buffer.rst:493 | ||||
msgid "" | ||||
"Copy *len* bytes from *src* to its contiguous representation in *buf*. " | ||||
"*order* can be ``'C'`` or ``'F'`` or ``'A'`` (for C-style or Fortran-style " | ||||
"ordering or either one). ``0`` is returned on success, ``-1`` on error." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/buffer.rst:497 | ||||
msgid "This function fails if *len* != *src->len*." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/buffer.rst:495 | ||||
#: ../Doc/c-api/buffer.rst:502 | ||||
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:502 | ||||
#: ../Doc/c-api/buffer.rst:509 | ||||
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:506 | ||||
#: ../Doc/c-api/buffer.rst:513 | ||||
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:510 | ||||
#: ../Doc/c-api/buffer.rst:517 | ||||
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:514 | ||||
#: ../Doc/c-api/buffer.rst:521 | ||||
msgid "" | ||||
"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 " | ||||
| | | |||
426 c-api/init.po
426
c-api/init.po File diff suppressed because it is too large Load diff
File diff suppressed because it is too large Load diff
172 c-api/intro.po
172
c-api/intro.po | | @ -5,7 +5,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2019-09-04 11:33+0200\n" | ||||
"POT-Creation-Date: 2019-10-09 17:54+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: FRENCH <traductions@lists.afpy.org>\n" | ||||
| | @ -104,15 +104,15 @@ msgid "" | |||
"names do not have a reserved prefix." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:72 | ||||
#: ../Doc/c-api/intro.rst:74 | ||||
msgid "" | ||||
"**Important:** user code should never define names that begin with ``Py`` or " | ||||
"``_Py``. This confuses the reader, and jeopardizes the portability of the " | ||||
"user code to future Python versions, which may define additional names " | ||||
"beginning with one of these prefixes." | ||||
"User code should never define names that begin with ``Py`` or ``_Py``. This " | ||||
"confuses the reader, and jeopardizes the portability of the user code to " | ||||
"future Python versions, which may define additional names beginning with one " | ||||
"of these prefixes." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:77 | ||||
#: ../Doc/c-api/intro.rst:79 | ||||
msgid "" | ||||
"The header files are typically installed with Python. On Unix, these are " | ||||
"located in the directories :file:`{prefix}/include/pythonversion/` and :file:" | ||||
| | @ -124,7 +124,7 @@ msgid "" | |||
"specified to the installer." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:86 | ||||
#: ../Doc/c-api/intro.rst:88 | ||||
msgid "" | ||||
"To include the headers, place both directories (if different) on your " | ||||
"compiler's search path for includes. Do *not* place the parent directories " | ||||
| | @ -134,18 +134,18 @@ msgid "" | |||
"`exec_prefix`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:93 | ||||
#: ../Doc/c-api/intro.rst:95 | ||||
msgid "" | ||||
"C++ users should note that though the API is defined entirely using C, the " | ||||
"header files do properly declare the entry points to be ``extern \"C\"``, so " | ||||
"there is no need to do anything special to use the API from C++." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:99 | ||||
msgid "Useful macros" | ||||
"C++ users should note that although the API is defined entirely using C, the " | ||||
"header files properly declare the entry points to be ``extern \"C\"``. As a " | ||||
"result, there is no need to do anything special to use the API from C++." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:101 | ||||
msgid "Useful macros" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:103 | ||||
msgid "" | ||||
"Several useful macros are defined in the Python header files. Many are " | ||||
"defined closer to where they are useful (e.g. :c:macro:`Py_RETURN_NONE`). " | ||||
| | @ -153,7 +153,7 @@ msgid "" | |||
"a complete listing." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:108 | ||||
#: ../Doc/c-api/intro.rst:110 | ||||
msgid "" | ||||
"Use this when you have a code path that you do not expect to be reached. For " | ||||
"example, in the ``default:`` clause in a ``switch`` statement for which all " | ||||
| | @ -161,64 +161,64 @@ msgid "" | |||
"where you might be tempted to put an ``assert(0)`` or ``abort()`` call." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:117 | ||||
#: ../Doc/c-api/intro.rst:119 | ||||
msgid "Return the absolute value of ``x``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:123 | ||||
#: ../Doc/c-api/intro.rst:125 | ||||
msgid "Return the minimum value between ``x`` and ``y``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:129 | ||||
#: ../Doc/c-api/intro.rst:131 | ||||
msgid "Return the maximum value between ``x`` and ``y``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:135 | ||||
#: ../Doc/c-api/intro.rst:137 | ||||
msgid "" | ||||
"Convert ``x`` to a C string. E.g. ``Py_STRINGIFY(123)`` returns ``\"123\"``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:142 | ||||
#: ../Doc/c-api/intro.rst:144 | ||||
msgid "Return the size of a structure (``type``) ``member`` in bytes." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:148 | ||||
#: ../Doc/c-api/intro.rst:150 | ||||
msgid "" | ||||
"Argument must be a character or an integer in the range [-128, 127] or [0, " | ||||
"255]. This macro returns ``c`` cast to an ``unsigned char``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:153 | ||||
#: ../Doc/c-api/intro.rst:155 | ||||
msgid "" | ||||
"Like ``getenv(s)``, but returns *NULL* if :option:`-E` was passed on the " | ||||
"command line (i.e. if ``Py_IgnoreEnvironmentFlag`` is set)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:158 | ||||
#: ../Doc/c-api/intro.rst:160 | ||||
msgid "" | ||||
"Use this for unused arguments in a function definition to silence compiler " | ||||
"warnings. Example: ``int func(int a, int Py_UNUSED(b)) { return a; }``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:165 | ||||
#: ../Doc/c-api/intro.rst:167 | ||||
msgid "" | ||||
"Use this for deprecated declarations. The macro must be placed before the " | ||||
"symbol name." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:168 | ||||
#: ../Doc/c-api/intro.rst:170 | ||||
msgid "Example::" | ||||
msgstr "Exemple ::" | ||||
| ||||
#: ../Doc/c-api/intro.rst:172 | ||||
#: ../Doc/c-api/intro.rst:174 | ||||
msgid "MSVC support was added." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:179 | ||||
#: ../Doc/c-api/intro.rst:181 | ||||
msgid "Objects, Types and Reference Counts" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:183 | ||||
#: ../Doc/c-api/intro.rst:185 | ||||
msgid "" | ||||
"Most Python/C API functions have one or more arguments as well as a return " | ||||
"value of type :c:type:`PyObject\\*`. This type is a pointer to an opaque " | ||||
| | @ -233,7 +233,7 @@ msgid "" | |||
"objects." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:194 | ||||
#: ../Doc/c-api/intro.rst:196 | ||||
msgid "" | ||||
"All Python objects (even Python integers) have a :dfn:`type` and a :dfn:" | ||||
"`reference count`. An object's type determines what kind of object it is (e." | ||||
| | @ -244,11 +244,11 @@ msgid "" | |||
"a Python list." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:205 | ||||
#: ../Doc/c-api/intro.rst:207 | ||||
msgid "Reference Counts" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:207 | ||||
#: ../Doc/c-api/intro.rst:209 | ||||
msgid "" | ||||
"The reference count is important because today's computers have a finite " | ||||
"(and often severely limited) memory size; it counts how many different " | ||||
| | @ -262,7 +262,7 @@ msgid "" | |||
"for now, the solution is \"don't do that.\")" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:222 | ||||
#: ../Doc/c-api/intro.rst:224 | ||||
msgid "" | ||||
"Reference counts are always manipulated explicitly. The normal way is to " | ||||
"use the macro :c:func:`Py_INCREF` to increment an object's reference count " | ||||
| | @ -280,7 +280,7 @@ msgid "" | |||
"reference count increment is a simple operation." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:236 | ||||
#: ../Doc/c-api/intro.rst:238 | ||||
msgid "" | ||||
"It is not necessary to increment an object's reference count for every " | ||||
"local variable that contains a pointer to an object. In theory, the " | ||||
| | @ -297,7 +297,7 @@ msgid "" | |||
"to hold a reference to every argument for the duration of the call." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:250 | ||||
#: ../Doc/c-api/intro.rst:252 | ||||
msgid "" | ||||
"However, a common pitfall is to extract an object from a list and hold on to " | ||||
"it for a while without incrementing its reference count. Some other " | ||||
| | @ -308,7 +308,7 @@ msgid "" | |||
"from a :c:func:`Py_DECREF`, so almost any operation is potentially dangerous." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:258 | ||||
#: ../Doc/c-api/intro.rst:260 | ||||
msgid "" | ||||
"A safe approach is to always use the generic operations (functions whose " | ||||
"name begins with ``PyObject_``, ``PyNumber_``, ``PySequence_`` or " | ||||
| | @ -318,11 +318,11 @@ msgid "" | |||
"becomes second nature." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:268 | ||||
#: ../Doc/c-api/intro.rst:270 | ||||
msgid "Reference Count Details" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:270 | ||||
#: ../Doc/c-api/intro.rst:272 | ||||
msgid "" | ||||
"The reference count behavior of functions in the Python/C API is best " | ||||
"explained in terms of *ownership of references*. Ownership pertains to " | ||||
| | @ -339,7 +339,7 @@ msgid "" | |||
"reference." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:283 | ||||
#: ../Doc/c-api/intro.rst:285 | ||||
msgid "" | ||||
"Conversely, when a calling function passes in a reference to an object, " | ||||
"there are two possibilities: the function *steals* a reference to the " | ||||
| | @ -348,7 +348,7 @@ msgid "" | |||
"reference, and you are not responsible for it any longer." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:293 | ||||
#: ../Doc/c-api/intro.rst:295 | ||||
msgid "" | ||||
"Few functions steal references; the two notable exceptions are :c:func:" | ||||
"`PyList_SetItem` and :c:func:`PyTuple_SetItem`, which steal a reference to " | ||||
| | @ -360,7 +360,7 @@ msgid "" | |||
"below)::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:308 | ||||
#: ../Doc/c-api/intro.rst:310 | ||||
msgid "" | ||||
"Here, :c:func:`PyLong_FromLong` returns a new reference which is immediately " | ||||
"stolen by :c:func:`PyTuple_SetItem`. When you want to keep using an object " | ||||
| | @ -368,7 +368,7 @@ msgid "" | |||
"another reference before calling the reference-stealing function." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:313 | ||||
#: ../Doc/c-api/intro.rst:315 | ||||
msgid "" | ||||
"Incidentally, :c:func:`PyTuple_SetItem` is the *only* way to set tuple " | ||||
"items; :c:func:`PySequence_SetItem` and :c:func:`PyObject_SetItem` refuse to " | ||||
| | @ -376,13 +376,13 @@ msgid "" | |||
"func:`PyTuple_SetItem` for tuples that you are creating yourself." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:318 | ||||
#: ../Doc/c-api/intro.rst:320 | ||||
msgid "" | ||||
"Equivalent code for populating a list can be written using :c:func:" | ||||
"`PyList_New` and :c:func:`PyList_SetItem`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:321 | ||||
#: ../Doc/c-api/intro.rst:323 | ||||
msgid "" | ||||
"However, in practice, you will rarely use these ways of creating and " | ||||
"populating a tuple or list. There's a generic function, :c:func:" | ||||
| | @ -391,7 +391,7 @@ msgid "" | |||
"be replaced by the following (which also takes care of the error checking)::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:332 | ||||
#: ../Doc/c-api/intro.rst:334 | ||||
msgid "" | ||||
"It is much more common to use :c:func:`PyObject_SetItem` and friends with " | ||||
"items whose references you are only borrowing, like arguments that were " | ||||
| | @ -402,7 +402,7 @@ msgid "" | |||
"sequence) to a given item::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:362 | ||||
#: ../Doc/c-api/intro.rst:364 | ||||
msgid "" | ||||
"The situation is slightly different for function return values. While " | ||||
"passing a reference to most functions does not change your ownership " | ||||
| | @ -415,7 +415,7 @@ msgid "" | |||
"becomes the owner of the reference)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:371 | ||||
#: ../Doc/c-api/intro.rst:373 | ||||
msgid "" | ||||
"It is important to realize that whether you own a reference returned by a " | ||||
"function depends on which function you call only --- *the plumage* (the type " | ||||
| | @ -426,18 +426,18 @@ msgid "" | |||
"the same arguments), you do own a reference to the returned object." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:383 | ||||
#: ../Doc/c-api/intro.rst:385 | ||||
msgid "" | ||||
"Here is an example of how you could write a function that computes the sum " | ||||
"of the items in a list of integers; once using :c:func:`PyList_GetItem`, " | ||||
"and once using :c:func:`PySequence_GetItem`. ::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:447 | ||||
#: ../Doc/c-api/intro.rst:449 | ||||
msgid "Types" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:449 | ||||
#: ../Doc/c-api/intro.rst:451 | ||||
msgid "" | ||||
"There are few other data types that play a significant role in the Python/C " | ||||
"API; most are simple C types such as :c:type:`int`, :c:type:`long`, :c:type:" | ||||
| | @ -448,11 +448,11 @@ msgid "" | |||
"that use them." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:461 | ||||
#: ../Doc/c-api/intro.rst:463 | ||||
msgid "Exceptions" | ||||
msgstr "Exceptions" | ||||
| ||||
#: ../Doc/c-api/intro.rst:463 | ||||
#: ../Doc/c-api/intro.rst:465 | ||||
msgid "" | ||||
"The Python programmer only needs to deal with exceptions if specific error " | ||||
"handling is required; unhandled exceptions are automatically propagated to " | ||||
| | @ -461,7 +461,7 @@ msgid "" | |||
"stack traceback." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:471 | ||||
#: ../Doc/c-api/intro.rst:473 | ||||
msgid "" | ||||
"For C programmers, however, error checking always has to be explicit. All " | ||||
"functions in the Python/C API can raise exceptions, unless an explicit claim " | ||||
| | @ -476,7 +476,7 @@ msgid "" | |||
"explicitly documented." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:486 | ||||
#: ../Doc/c-api/intro.rst:488 | ||||
msgid "" | ||||
"Exception state is maintained in per-thread storage (this is equivalent to " | ||||
"using global storage in an unthreaded application). A thread can be in one " | ||||
| | @ -489,7 +489,7 @@ msgid "" | |||
"clears the exception state." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:496 | ||||
#: ../Doc/c-api/intro.rst:498 | ||||
msgid "" | ||||
"The full exception state consists of three objects (all of which can be " | ||||
"*NULL*): the exception type, the corresponding exception value, and the " | ||||
| | @ -502,7 +502,7 @@ msgid "" | |||
"``sys.exc_info()`` and friends." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:508 | ||||
#: ../Doc/c-api/intro.rst:510 | ||||
msgid "" | ||||
"Note that starting with Python 1.5, the preferred, thread-safe way to access " | ||||
"the exception state from Python code is to call the function :func:`sys." | ||||
| | @ -516,7 +516,7 @@ msgid "" | |||
"referenced by the stack frames in the traceback." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:519 | ||||
#: ../Doc/c-api/intro.rst:521 | ||||
msgid "" | ||||
"As a general principle, a function that calls another function to perform " | ||||
"some task should check whether the called function raised an exception, and " | ||||
| | @ -527,7 +527,7 @@ msgid "" | |||
"of the error." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:528 | ||||
#: ../Doc/c-api/intro.rst:530 | ||||
msgid "" | ||||
"A simple example of detecting exceptions and passing them on is shown in " | ||||
"the :c:func:`sum_sequence` example above. It so happens that this example " | ||||
| | @ -536,11 +536,11 @@ msgid "" | |||
"why you like Python, we show the equivalent Python code::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:543 | ||||
#: ../Doc/c-api/intro.rst:545 | ||||
msgid "Here is the corresponding C code, in all its glory::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:595 | ||||
#: ../Doc/c-api/intro.rst:597 | ||||
msgid "" | ||||
"This example represents an endorsed use of the ``goto`` statement in C! It " | ||||
"illustrates the use of :c:func:`PyErr_ExceptionMatches` and :c:func:" | ||||
| | @ -553,11 +553,11 @@ msgid "" | |||
"success after the final call made is successful." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:609 | ||||
#: ../Doc/c-api/intro.rst:611 | ||||
msgid "Embedding Python" | ||||
msgstr "Embarquer Python" | ||||
| ||||
#: ../Doc/c-api/intro.rst:611 | ||||
#: ../Doc/c-api/intro.rst:613 | ||||
msgid "" | ||||
"The one important task that only embedders (as opposed to extension writers) " | ||||
"of the Python interpreter have to worry about is the initialization, and " | ||||
| | @ -565,7 +565,7 @@ msgid "" | |||
"the interpreter can only be used after the interpreter has been initialized." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:624 | ||||
#: ../Doc/c-api/intro.rst:626 | ||||
msgid "" | ||||
"The basic initialization function is :c:func:`Py_Initialize`. This " | ||||
"initializes the table of loaded modules, and creates the fundamental " | ||||
| | @ -573,7 +573,7 @@ msgid "" | |||
"initializes the module search path (``sys.path``)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:631 | ||||
#: ../Doc/c-api/intro.rst:633 | ||||
msgid "" | ||||
":c:func:`Py_Initialize` does not set the \"script argument list\" (``sys." | ||||
"argv``). If this variable is needed by Python code that will be executed " | ||||
| | @ -581,7 +581,7 @@ msgid "" | |||
"argv, updatepath)`` after the call to :c:func:`Py_Initialize`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:636 | ||||
#: ../Doc/c-api/intro.rst:638 | ||||
msgid "" | ||||
"On most systems (in particular, on Unix and Windows, although the details " | ||||
"are slightly different), :c:func:`Py_Initialize` calculates the module " | ||||
| | @ -593,7 +593,7 @@ msgid "" | |||
"on the shell command search path (the environment variable :envvar:`PATH`)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:645 | ||||
#: ../Doc/c-api/intro.rst:647 | ||||
msgid "" | ||||
"For instance, if the Python executable is found in :file:`/usr/local/bin/" | ||||
"python`, it will assume that the libraries are in :file:`/usr/local/lib/" | ||||
| | @ -604,7 +604,7 @@ msgid "" | |||
"in front of the standard path by setting :envvar:`PYTHONPATH`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:660 | ||||
#: ../Doc/c-api/intro.rst:662 | ||||
msgid "" | ||||
"The embedding application can steer the search by calling " | ||||
"``Py_SetProgramName(file)`` *before* calling :c:func:`Py_Initialize`. Note " | ||||
| | @ -615,7 +615,7 @@ msgid "" | |||
"func:`Py_GetProgramFullPath` (all defined in :file:`Modules/getpath.c`)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:670 | ||||
#: ../Doc/c-api/intro.rst:672 | ||||
msgid "" | ||||
"Sometimes, it is desirable to \"uninitialize\" Python. For instance, the " | ||||
"application may want to start over (make another call to :c:func:" | ||||
| | @ -629,18 +629,18 @@ msgid "" | |||
"released." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:684 | ||||
#: ../Doc/c-api/intro.rst:686 | ||||
msgid "Debugging Builds" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:686 | ||||
#: ../Doc/c-api/intro.rst:688 | ||||
msgid "" | ||||
"Python can be built with several macros to enable extra checks of the " | ||||
"interpreter and extension modules. These checks tend to add a large amount " | ||||
"of overhead to the runtime so they are not enabled by default." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:690 | ||||
#: ../Doc/c-api/intro.rst:692 | ||||
msgid "" | ||||
"A full list of the various types of debugging builds is in the file :file:" | ||||
"`Misc/SpecialBuilds.txt` in the Python source distribution. Builds are " | ||||
| | @ -650,7 +650,7 @@ msgid "" | |||
"section." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:696 | ||||
#: ../Doc/c-api/intro.rst:698 | ||||
msgid "" | ||||
"Compiling the interpreter with the :c:macro:`Py_DEBUG` macro defined " | ||||
"produces what is generally meant by \"a debug build\" of Python. :c:macro:" | ||||
| | @ -660,61 +660,61 @@ msgid "" | |||
"enabled in the Unix build, compiler optimization is disabled." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:703 | ||||
#: ../Doc/c-api/intro.rst:705 | ||||
msgid "" | ||||
"In addition to the reference count debugging described below, the following " | ||||
"extra checks are performed:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:706 | ||||
#: ../Doc/c-api/intro.rst:708 | ||||
msgid "Extra checks are added to the object allocator." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:708 | ||||
#: ../Doc/c-api/intro.rst:710 | ||||
msgid "Extra checks are added to the parser and compiler." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:710 | ||||
#: ../Doc/c-api/intro.rst:712 | ||||
msgid "" | ||||
"Downcasts from wide types to narrow types are checked for loss of " | ||||
"information." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:712 | ||||
#: ../Doc/c-api/intro.rst:714 | ||||
msgid "" | ||||
"A number of assertions are added to the dictionary and set implementations. " | ||||
"In addition, the set object acquires a :meth:`test_c_api` method." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:715 | ||||
#: ../Doc/c-api/intro.rst:717 | ||||
msgid "Sanity checks of the input arguments are added to frame creation." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:717 | ||||
#: ../Doc/c-api/intro.rst:719 | ||||
msgid "" | ||||
"The storage for ints is initialized with a known invalid pattern to catch " | ||||
"reference to uninitialized digits." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:720 | ||||
#: ../Doc/c-api/intro.rst:722 | ||||
msgid "" | ||||
"Low-level tracing and extra exception checking are added to the runtime " | ||||
"virtual machine." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:723 | ||||
#: ../Doc/c-api/intro.rst:725 | ||||
msgid "Extra checks are added to the memory arena implementation." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:725 | ||||
#: ../Doc/c-api/intro.rst:727 | ||||
msgid "Extra debugging is added to the thread module." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:727 | ||||
#: ../Doc/c-api/intro.rst:729 | ||||
msgid "There may be additional checks not mentioned here." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:729 | ||||
#: ../Doc/c-api/intro.rst:731 | ||||
msgid "" | ||||
"Defining :c:macro:`Py_TRACE_REFS` enables reference tracing. When defined, " | ||||
"a circular doubly linked list of active objects is maintained by adding two " | ||||
| | @ -724,7 +724,7 @@ msgid "" | |||
"macro:`Py_DEBUG`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/intro.rst:735 | ||||
#: ../Doc/c-api/intro.rst:737 | ||||
msgid "" | ||||
"Please refer to :file:`Misc/SpecialBuilds.txt` in the Python source " | ||||
"distribution for more detailed information." | ||||
| | | |||
| | @ -5,7 +5,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-03-23 09:03+0100\n" | ||||
"POT-Creation-Date: 2019-10-09 17:54+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: FRENCH <traductions@lists.afpy.org>\n" | ||||
| | @ -476,24 +476,36 @@ msgstr "" | |||
msgid "" | ||||
"Add an object to *module* as *name*. This is a convenience function which " | ||||
"can be used from the module's initialization function. This steals a " | ||||
"reference to *value*. Return ``-1`` on error, ``0`` on success." | ||||
"reference to *value* on success. Return ``-1`` on error, ``0`` on success." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:424 | ||||
msgid "" | ||||
"Unlike other functions that steal references, ``PyModule_AddObject()`` only " | ||||
"decrements the reference count of *value* **on success**." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:427 | ||||
msgid "" | ||||
"This means that its return value must be checked, and calling code must :c:" | ||||
"func:`Py_DECREF` *value* manually on error. Example usage::" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:439 | ||||
msgid "" | ||||
"Add an integer constant to *module* as *name*. This convenience function " | ||||
"can be used from the module's initialization function. Return ``-1`` on " | ||||
"error, ``0`` on success." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:431 | ||||
#: ../Doc/c-api/module.rst:446 | ||||
msgid "" | ||||
"Add a string constant to *module* as *name*. This convenience function can " | ||||
"be used from the module's initialization function. The string *value* must " | ||||
"be *NULL*-terminated. Return ``-1`` on error, ``0`` on success." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:438 | ||||
#: ../Doc/c-api/module.rst:453 | ||||
msgid "" | ||||
"Add an int constant to *module*. The name and the value are taken from " | ||||
"*macro*. For example ``PyModule_AddIntMacro(module, AF_INET)`` adds the int " | ||||
| | @ -501,29 +513,29 @@ msgid "" | |||
"error, ``0`` on success." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:446 | ||||
#: ../Doc/c-api/module.rst:461 | ||||
msgid "Add a string constant to *module*." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:450 | ||||
#: ../Doc/c-api/module.rst:465 | ||||
msgid "Module lookup" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:452 | ||||
#: ../Doc/c-api/module.rst:467 | ||||
msgid "" | ||||
"Single-phase initialization creates singleton modules that can be looked up " | ||||
"in the context of the current interpreter. This allows the module object to " | ||||
"be retrieved later with only a reference to the module definition." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:456 | ||||
#: ../Doc/c-api/module.rst:471 | ||||
msgid "" | ||||
"These functions will not work on modules created using multi-phase " | ||||
"initialization, since multiple such modules can be created from a single " | ||||
"definition." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:461 | ||||
#: ../Doc/c-api/module.rst:476 | ||||
msgid "" | ||||
"Returns the module object that was created from *def* for the current " | ||||
"interpreter. This method requires that the module object has been attached " | ||||
| | @ -532,18 +544,18 @@ msgid "" | |||
"to the interpreter state yet, it returns *NULL*." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:468 | ||||
#: ../Doc/c-api/module.rst:483 | ||||
msgid "" | ||||
"Attaches the module object passed to the function to the interpreter state. " | ||||
"This allows the module object to be accessible via :c:func:" | ||||
"`PyState_FindModule`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:471 | ||||
#: ../Doc/c-api/module.rst:486 | ||||
msgid "Only effective on modules created using single-phase initialization." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/module.rst:477 | ||||
#: ../Doc/c-api/module.rst:492 | ||||
msgid "" | ||||
"Removes the module object created from *def* from the interpreter state." | ||||
msgstr "" | ||||
| | | |||
| | @ -5,7 +5,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2018-06-10 11:27+0200\n" | ||||
"POT-Creation-Date: 2019-10-09 17:54+0200\n" | ||||
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: FRENCH <traductions@lists.afpy.org>\n" | ||||
| | @ -140,14 +140,26 @@ msgstr "" | |||
| ||||
#: ../Doc/c-api/sequence.rst:133 | ||||
msgid "" | ||||
"Return the sequence or iterable *o* as a list, unless it is already a tuple " | ||||
"or list, in which case *o* is returned. Use :c:func:" | ||||
"`PySequence_Fast_GET_ITEM` to access the members of the result. Returns " | ||||
"*NULL* on failure. If the object is not a sequence or iterable, raises :exc:" | ||||
"`TypeError` with *m* as the message text." | ||||
"Return the sequence or iterable *o* as an object usable by the other " | ||||
"``PySequence_Fast*`` family of functions. If the object is not a sequence or " | ||||
"iterable, raises :exc:`TypeError` with *m* as the message text. Returns " | ||||
"*NULL* on failure." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/sequence.rst:141 | ||||
#: ../Doc/c-api/sequence.rst:138 | ||||
msgid "" | ||||
"The ``PySequence_Fast*`` functions are thus named because they assume *o* is " | ||||
"a :c:type:`PyTupleObject` or a :c:type:`PyListObject` and access the data " | ||||
"fields of *o* directly." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/sequence.rst:142 | ||||
msgid "" | ||||
"As a CPython implementation detail, if *o* is already a sequence or list, it " | ||||
"will be returned." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/sequence.rst:148 | ||||
msgid "" | ||||
"Returns the length of *o*, assuming that *o* was returned by :c:func:" | ||||
"`PySequence_Fast` and that *o* is not *NULL*. The size can also be gotten " | ||||
| | @ -156,28 +168,28 @@ msgid "" | |||
"tuple." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/sequence.rst:150 | ||||
#: ../Doc/c-api/sequence.rst:157 | ||||
msgid "" | ||||
"Return the *i*\\ th element of *o*, assuming that *o* was returned by :c:" | ||||
"func:`PySequence_Fast`, *o* is not *NULL*, and that *i* is within bounds." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/sequence.rst:156 | ||||
#: ../Doc/c-api/sequence.rst:163 | ||||
msgid "" | ||||
"Return the underlying array of PyObject pointers. Assumes that *o* was " | ||||
"returned by :c:func:`PySequence_Fast` and *o* is not *NULL*." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/sequence.rst:159 | ||||
#: ../Doc/c-api/sequence.rst:166 | ||||
msgid "" | ||||
"Note, if a list gets resized, the reallocation may relocate the items array. " | ||||
"So, only use the underlying array pointer in contexts where the sequence " | ||||
"cannot change." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/sequence.rst:166 | ||||
#: ../Doc/c-api/sequence.rst:173 | ||||
msgid "" | ||||
"Return the *i*\\ th element of *o* or *NULL* on failure. Macro form of :c:" | ||||
"Return the *i*\\ th element of *o* or *NULL* on failure. Faster form of :c:" | ||||
"func:`PySequence_GetItem` but without checking that :c:func:" | ||||
"`PySequence_Check` on *o* is true and without adjustment for negative " | ||||
"indices." | ||||
| | | |||
| | @ -5,7 +5,7 @@ msgid "" | |||
msgstr "" | ||||
"Project-Id-Version: Python 3.6\n" | ||||
"Report-Msgid-Bugs-To: \n" | ||||
"POT-Creation-Date: 2019-09-04 11:33+0200\n" | ||||
"POT-Creation-Date: 2019-10-09 17:54+0200\n" | ||||
"PO-Revision-Date: 2018-02-15 00:33+0100\n" | ||||
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" | ||||
"Language-Team: FRENCH <traductions@lists.afpy.org>\n" | ||||
| | @ -136,74 +136,72 @@ msgid "" | |||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:121 | ||||
msgid "Creates and returns a heap type object from the *spec*." | ||||
msgid "" | ||||
"Creates and returns a heap type object from the *spec* (:const:" | ||||
"`Py_TPFLAGS_HEAPTYPE`)." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:123 | ||||
#: ../Doc/c-api/type.rst:124 | ||||
msgid "" | ||||
"If *bases* is a tuple, the created heap type contains all types contained in " | ||||
"it as base types." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:126 | ||||
#: ../Doc/c-api/type.rst:127 | ||||
msgid "" | ||||
"If *bases* is *NULL*, the *Py_tp_base* slot is used instead. If that also is " | ||||
"*NULL*, the new type derives from :class:`object`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:129 | ||||
#: ../Doc/c-api/type.rst:130 | ||||
msgid "This function calls :c:func:`PyType_Ready` on the new type." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:135 | ||||
#: ../Doc/c-api/type.rst:136 | ||||
msgid "Equivalent to ``PyType_FromSpecWithBases(spec, NULL)``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:139 | ||||
#: ../Doc/c-api/type.rst:140 | ||||
msgid "Structure defining a type's behavior." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:143 | ||||
#: ../Doc/c-api/type.rst:144 | ||||
msgid "Name of the type, used to set :c:member:`PyTypeObject.tp_name`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:147 | ||||
msgid "Type docstring, used to set :c:member:`PyTypeObject.tp_doc`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:152 | ||||
#: ../Doc/c-api/type.rst:149 | ||||
msgid "" | ||||
"Size of the instance in bytes, used to set :c:member:`PyTypeObject." | ||||
"tp_basicsize` and :c:member:`PyTypeObject.tp_itemsize`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:158 | ||||
#: ../Doc/c-api/type.rst:155 | ||||
msgid "Type flags, used to set :c:member:`PyTypeObject.tp_flags`." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:160 | ||||
#: ../Doc/c-api/type.rst:157 | ||||
msgid "" | ||||
"If the ``Py_TPFLAGS_HEAPTYPE`` flag is not set, :c:func:" | ||||
"`PyType_FromSpecWithBases` sets it automatically." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:165 | ||||
#: ../Doc/c-api/type.rst:162 | ||||
msgid "" | ||||
"Array of :c:type:`PyType_Slot` structures. Terminated by the special slot " | ||||
"value ``{0, NULL}``." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:170 | ||||
#: ../Doc/c-api/type.rst:167 | ||||
msgid "" | ||||
"Structure defining optional functionality of a type, containing a slot ID " | ||||
"and a value pointer." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:175 | ||||
#: ../Doc/c-api/type.rst:172 | ||||
msgid "A slot ID." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:177 | ||||
#: ../Doc/c-api/type.rst:174 | ||||
msgid "" | ||||
"Slot IDs are named like the field names of the structures :c:type:" | ||||
"`PyTypeObject`, :c:type:`PyNumberMethods`, :c:type:`PySequenceMethods`, :c:" | ||||
| | @ -211,76 +209,76 @@ msgid "" | |||
"prefix. For example, use:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:183 | ||||
#: ../Doc/c-api/type.rst:180 | ||||
msgid "``Py_tp_dealloc`` to set :c:member:`PyTypeObject.tp_dealloc`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:184 | ||||
#: ../Doc/c-api/type.rst:181 | ||||
msgid "``Py_nb_add`` to set :c:member:`PyNumberMethods.nb_add`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:185 | ||||
#: ../Doc/c-api/type.rst:182 | ||||
msgid "``Py_sq_length`` to set :c:member:`PySequenceMethods.sq_length`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:187 | ||||
#: ../Doc/c-api/type.rst:184 | ||||
msgid "" | ||||
"The following fields cannot be set using *PyType_Spec* and *PyType_Slot*:" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:189 | ||||
#: ../Doc/c-api/type.rst:186 | ||||
msgid ":c:member:`~PyTypeObject.tp_dict`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:190 | ||||
#: ../Doc/c-api/type.rst:187 | ||||
msgid ":c:member:`~PyTypeObject.tp_mro`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:191 | ||||
#: ../Doc/c-api/type.rst:188 | ||||
msgid ":c:member:`~PyTypeObject.tp_cache`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:192 | ||||
#: ../Doc/c-api/type.rst:189 | ||||
msgid ":c:member:`~PyTypeObject.tp_subclasses`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:193 | ||||
#: ../Doc/c-api/type.rst:190 | ||||
msgid ":c:member:`~PyTypeObject.tp_weaklist`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:194 | ||||
#: ../Doc/c-api/type.rst:191 | ||||
msgid ":c:member:`~PyTypeObject.tp_print`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:195 | ||||
#: ../Doc/c-api/type.rst:192 | ||||
msgid ":c:member:`~PyTypeObject.tp_weaklistoffset`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:196 | ||||
#: ../Doc/c-api/type.rst:193 | ||||
msgid ":c:member:`~PyTypeObject.tp_dictoffset`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:197 | ||||
#: ../Doc/c-api/type.rst:194 | ||||
msgid ":c:member:`~PyBufferProcs.bf_getbuffer`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:198 | ||||
#: ../Doc/c-api/type.rst:195 | ||||
msgid ":c:member:`~PyBufferProcs.bf_releasebuffer`" | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:200 | ||||
#: ../Doc/c-api/type.rst:197 | ||||
msgid "" | ||||
"Setting :c:data:`Py_tp_bases` may be problematic on some platforms. To avoid " | ||||
"issues, use the *bases* argument of :py:func:`PyType_FromSpecWithBases` " | ||||
"instead." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:206 | ||||
#: ../Doc/c-api/type.rst:203 | ||||
msgid "" | ||||
"The desired value of the slot. In most cases, this is a pointer to a " | ||||
"function." | ||||
msgstr "" | ||||
| ||||
#: ../Doc/c-api/type.rst:209 | ||||
#: ../Doc/c-api/type.rst:206 | ||||
msgid "May not be *NULL*." | ||||
msgstr "" | ||||
| | | |||
743 c-api/typeobj.po
743
c-api/typeobj.po File diff suppressed because it is too large Load diff
Loading…
Add table
Add a link
Reference in a new issue