|
7 | 7 | msgstr "" |
8 | 8 | "Project-Id-Version: Python 3.11\n" |
9 | 9 | "Report-Msgid-Bugs-To: \n" |
10 | | -"POT-Creation-Date: 2022-12-17 01:28+0300\n" |
| 10 | +"POT-Creation-Date: 2023-09-18 19:05+0000\n" |
11 | 11 | "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" |
12 | 12 | "Last-Translator: \n" |
13 | 13 | "Language-Team: TURKISH <python.docs.tr@gmail.com>\n" |
@@ -38,44 +38,46 @@ msgstr "" |
38 | 38 | #: c-api/allocation.rst:32 |
39 | 39 | msgid "" |
40 | 40 | "Allocate a new Python object using the C structure type *TYPE* and the " |
41 | | -"Python type object *type*. Fields not defined by the Python object header " |
42 | | -"are not initialized; the object's reference count will be one. The size of " |
| 41 | +"Python type object *typeobj* (``PyTypeObject*``). Fields not defined by the " |
| 42 | +"Python object header are not initialized. The caller will own the only " |
| 43 | +"reference to the object (i.e. its reference count will be one). The size of " |
43 | 44 | "the memory allocation is determined from the :c:member:`~PyTypeObject." |
44 | 45 | "tp_basicsize` field of the type object." |
45 | 46 | msgstr "" |
46 | 47 |
|
47 | | -#: c-api/allocation.rst:41 |
| 48 | +#: c-api/allocation.rst:43 |
48 | 49 | msgid "" |
49 | 50 | "Allocate a new Python object using the C structure type *TYPE* and the " |
50 | | -"Python type object *type*. Fields not defined by the Python object header " |
51 | | -"are not initialized. The allocated memory allows for the *TYPE* structure " |
52 | | -"plus *size* fields of the size given by the :c:member:`~PyTypeObject." |
53 | | -"tp_itemsize` field of *type*. This is useful for implementing objects like " |
54 | | -"tuples, which are able to determine their size at construction time. " |
55 | | -"Embedding the array of fields into the same allocation decreases the number " |
56 | | -"of allocations, improving the memory management efficiency." |
| 51 | +"Python type object *typeobj* (``PyTypeObject*``). Fields not defined by the " |
| 52 | +"Python object header are not initialized. The allocated memory allows for " |
| 53 | +"the *TYPE* structure plus *size* (``Py_ssize_t``) fields of the size given " |
| 54 | +"by the :c:member:`~PyTypeObject.tp_itemsize` field of *typeobj*. This is " |
| 55 | +"useful for implementing objects like tuples, which are able to determine " |
| 56 | +"their size at construction time. Embedding the array of fields into the " |
| 57 | +"same allocation decreases the number of allocations, improving the memory " |
| 58 | +"management efficiency." |
57 | 59 | msgstr "" |
58 | 60 |
|
59 | | -#: c-api/allocation.rst:53 |
| 61 | +#: c-api/allocation.rst:57 |
60 | 62 | msgid "" |
61 | | -"Releases memory allocated to an object using :c:func:`PyObject_New` or :c:" |
62 | | -"func:`PyObject_NewVar`. This is normally called from the :c:member:" |
| 63 | +"Releases memory allocated to an object using :c:macro:`PyObject_New` or :c:" |
| 64 | +"macro:`PyObject_NewVar`. This is normally called from the :c:member:" |
63 | 65 | "`~PyTypeObject.tp_dealloc` handler specified in the object's type. The " |
64 | 66 | "fields of the object should not be accessed after this call as the memory is " |
65 | 67 | "no longer a valid Python object." |
66 | 68 | msgstr "" |
67 | 69 |
|
68 | | -#: c-api/allocation.rst:62 |
| 70 | +#: c-api/allocation.rst:66 |
69 | 71 | msgid "" |
70 | 72 | "Object which is visible in Python as ``None``. This should only be accessed " |
71 | 73 | "using the :c:macro:`Py_None` macro, which evaluates to a pointer to this " |
72 | 74 | "object." |
73 | 75 | msgstr "" |
74 | 76 |
|
75 | | -#: c-api/allocation.rst:69 |
| 77 | +#: c-api/allocation.rst:73 |
76 | 78 | msgid ":c:func:`PyModule_Create`" |
77 | 79 | msgstr "" |
78 | 80 |
|
79 | | -#: c-api/allocation.rst:70 |
| 81 | +#: c-api/allocation.rst:74 |
80 | 82 | msgid "To allocate and create extension modules." |
81 | 83 | msgstr "" |
0 commit comments