|
| 1 | +# Copyright (C) 2001-2018, Python Software Foundation |
| 2 | +# For licence information, see README file. |
| 3 | +# |
| 4 | +msgid "" |
| 5 | +msgstr "" |
| 6 | +"Project-Id-Version: Python 3.8\n" |
| 7 | +"Report-Msgid-Bugs-To: \n" |
| 8 | +"POT-Creation-Date: 2019-09-04 11:33+0200\n" |
| 9 | +"PO-Revision-Date: 2019-09-04 11:44+0200\n" |
| 10 | +"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" |
| 11 | +"Language-Team: FRENCH <traductions@lists.afpy.org>\n" |
| 12 | +"Language: fr\n" |
| 13 | +"MIME-Version: 1.0\n" |
| 14 | +"Content-Type: text/plain; charset=UTF-8\n" |
| 15 | +"Content-Transfer-Encoding: 8bit\n" |
| 16 | + |
| 17 | +#: ../Doc/library/multiprocessing.shared_memory.rst:2 |
| 18 | +msgid "" |
| 19 | +":mod:`multiprocessing.shared_memory` --- Provides shared memory for direct " |
| 20 | +"access across processes" |
| 21 | +msgstr "" |
| 22 | + |
| 23 | +#: ../Doc/library/multiprocessing.shared_memory.rst:7 |
| 24 | +msgid "**Source code:** :source:`Lib/multiprocessing/shared_memory.py`" |
| 25 | +msgstr "" |
| 26 | + |
| 27 | +#: ../Doc/library/multiprocessing.shared_memory.rst:18 |
| 28 | +msgid "" |
| 29 | +"This module provides a class, :class:`SharedMemory`, for the allocation and " |
| 30 | +"management of shared memory to be accessed by one or more processes on a " |
| 31 | +"multicore or symmetric multiprocessor (SMP) machine. To assist with the " |
| 32 | +"life-cycle management of shared memory especially across distinct processes, " |
| 33 | +"a :class:`~multiprocessing.managers.BaseManager` subclass, :class:" |
| 34 | +"`SharedMemoryManager`, is also provided in the ``multiprocessing.managers`` " |
| 35 | +"module." |
| 36 | +msgstr "" |
| 37 | + |
| 38 | +#: ../Doc/library/multiprocessing.shared_memory.rst:26 |
| 39 | +msgid "" |
| 40 | +"In this module, shared memory refers to \"System V style\" shared memory " |
| 41 | +"blocks (though is not necessarily implemented explicitly as such) and does " |
| 42 | +"not refer to \"distributed shared memory\". This style of shared memory " |
| 43 | +"permits distinct processes to potentially read and write to a common (or " |
| 44 | +"shared) region of volatile memory. Processes are conventionally limited to " |
| 45 | +"only have access to their own process memory space but shared memory permits " |
| 46 | +"the sharing of data between processes, avoiding the need to instead send " |
| 47 | +"messages between processes containing that data. Sharing data directly via " |
| 48 | +"memory can provide significant performance benefits compared to sharing data " |
| 49 | +"via disk or socket or other communications requiring the serialization/" |
| 50 | +"deserialization and copying of data." |
| 51 | +msgstr "" |
| 52 | + |
| 53 | +#: ../Doc/library/multiprocessing.shared_memory.rst:41 |
| 54 | +msgid "" |
| 55 | +"Creates a new shared memory block or attaches to an existing shared memory " |
| 56 | +"block. Each shared memory block is assigned a unique name. In this way, one " |
| 57 | +"process can create a shared memory block with a particular name and a " |
| 58 | +"different process can attach to that same shared memory block using that " |
| 59 | +"same name." |
| 60 | +msgstr "" |
| 61 | + |
| 62 | +#: ../Doc/library/multiprocessing.shared_memory.rst:47 |
| 63 | +msgid "" |
| 64 | +"As a resource for sharing data across processes, shared memory blocks may " |
| 65 | +"outlive the original process that created them. When one process no longer " |
| 66 | +"needs access to a shared memory block that might still be needed by other " |
| 67 | +"processes, the :meth:`close()` method should be called. When a shared memory " |
| 68 | +"block is no longer needed by any process, the :meth:`unlink()` method should " |
| 69 | +"be called to ensure proper cleanup." |
| 70 | +msgstr "" |
| 71 | + |
| 72 | +#: ../Doc/library/multiprocessing.shared_memory.rst:54 |
| 73 | +msgid "" |
| 74 | +"*name* is the unique name for the requested shared memory, specified as a " |
| 75 | +"string. When creating a new shared memory block, if ``None`` (the default) " |
| 76 | +"is supplied for the name, a novel name will be generated." |
| 77 | +msgstr "" |
| 78 | + |
| 79 | +#: ../Doc/library/multiprocessing.shared_memory.rst:58 |
| 80 | +msgid "" |
| 81 | +"*create* controls whether a new shared memory block is created (``True``) or " |
| 82 | +"an existing shared memory block is attached (``False``)." |
| 83 | +msgstr "" |
| 84 | + |
| 85 | +#: ../Doc/library/multiprocessing.shared_memory.rst:61 |
| 86 | +msgid "" |
| 87 | +"*size* specifies the requested number of bytes when creating a new shared " |
| 88 | +"memory block. Because some platforms choose to allocate chunks of memory " |
| 89 | +"based upon that platform's memory page size, the exact size of the shared " |
| 90 | +"memory block may be larger or equal to the size requested. When attaching " |
| 91 | +"to an existing shared memory block, the ``size`` parameter is ignored." |
| 92 | +msgstr "" |
| 93 | + |
| 94 | +#: ../Doc/library/multiprocessing.shared_memory.rst:69 |
| 95 | +msgid "" |
| 96 | +"Closes access to the shared memory from this instance. In order to ensure " |
| 97 | +"proper cleanup of resources, all instances should call ``close()`` once the " |
| 98 | +"instance is no longer needed. Note that calling ``close()`` does not cause " |
| 99 | +"the shared memory block itself to be destroyed." |
| 100 | +msgstr "" |
| 101 | + |
| 102 | +#: ../Doc/library/multiprocessing.shared_memory.rst:77 |
| 103 | +msgid "" |
| 104 | +"Requests that the underlying shared memory block be destroyed. In order to " |
| 105 | +"ensure proper cleanup of resources, ``unlink()`` should be called once (and " |
| 106 | +"only once) across all processes which have need for the shared memory " |
| 107 | +"block. After requesting its destruction, a shared memory block may or may " |
| 108 | +"not be immediately destroyed and this behavior may differ across platforms. " |
| 109 | +"Attempts to access data inside the shared memory block after ``unlink()`` " |
| 110 | +"has been called may result in memory access errors. Note: the last process " |
| 111 | +"relinquishing its hold on a shared memory block may call ``unlink()`` and :" |
| 112 | +"meth:`close()` in either order." |
| 113 | +msgstr "" |
| 114 | + |
| 115 | +#: ../Doc/library/multiprocessing.shared_memory.rst:90 |
| 116 | +msgid "A memoryview of contents of the shared memory block." |
| 117 | +msgstr "" |
| 118 | + |
| 119 | +#: ../Doc/library/multiprocessing.shared_memory.rst:94 |
| 120 | +msgid "Read-only access to the unique name of the shared memory block." |
| 121 | +msgstr "" |
| 122 | + |
| 123 | +#: ../Doc/library/multiprocessing.shared_memory.rst:98 |
| 124 | +msgid "Read-only access to size in bytes of the shared memory block." |
| 125 | +msgstr "" |
| 126 | + |
| 127 | +#: ../Doc/library/multiprocessing.shared_memory.rst:101 |
| 128 | +msgid "" |
| 129 | +"The following example demonstrates low-level use of :class:`SharedMemory` " |
| 130 | +"instances::" |
| 131 | +msgstr "" |
| 132 | + |
| 133 | +#: ../Doc/library/multiprocessing.shared_memory.rst:127 |
| 134 | +msgid "" |
| 135 | +"The following example demonstrates a practical use of the :class:" |
| 136 | +"`SharedMemory` class with `NumPy arrays <https://www.numpy.org/>`_, " |
| 137 | +"accessing the same ``numpy.ndarray`` from two distinct Python shells:" |
| 138 | +msgstr "" |
| 139 | + |
| 140 | +#: ../Doc/library/multiprocessing.shared_memory.rst:181 |
| 141 | +msgid "" |
| 142 | +"A subclass of :class:`~multiprocessing.managers.BaseManager` which can be " |
| 143 | +"used for the management of shared memory blocks across processes." |
| 144 | +msgstr "" |
| 145 | + |
| 146 | +#: ../Doc/library/multiprocessing.shared_memory.rst:184 |
| 147 | +msgid "" |
| 148 | +"A call to :meth:`~multiprocessing.managers.BaseManager.start` on a :class:" |
| 149 | +"`SharedMemoryManager` instance causes a new process to be started. This new " |
| 150 | +"process's sole purpose is to manage the life cycle of all shared memory " |
| 151 | +"blocks created through it. To trigger the release of all shared memory " |
| 152 | +"blocks managed by that process, call :meth:`~multiprocessing.managers." |
| 153 | +"BaseManager.shutdown()` on the instance. This triggers a :meth:`SharedMemory." |
| 154 | +"unlink()` call on all of the :class:`SharedMemory` objects managed by that " |
| 155 | +"process and then stops the process itself. By creating ``SharedMemory`` " |
| 156 | +"instances through a ``SharedMemoryManager``, we avoid the need to manually " |
| 157 | +"track and trigger the freeing of shared memory resources." |
| 158 | +msgstr "" |
| 159 | + |
| 160 | +#: ../Doc/library/multiprocessing.shared_memory.rst:196 |
| 161 | +msgid "" |
| 162 | +"This class provides methods for creating and returning :class:`SharedMemory` " |
| 163 | +"instances and for creating a list-like object (:class:`ShareableList`) " |
| 164 | +"backed by shared memory." |
| 165 | +msgstr "" |
| 166 | + |
| 167 | +#: ../Doc/library/multiprocessing.shared_memory.rst:200 |
| 168 | +msgid "" |
| 169 | +"Refer to :class:`multiprocessing.managers.BaseManager` for a description of " |
| 170 | +"the inherited *address* and *authkey* optional input arguments and how they " |
| 171 | +"may be used to connect to an existing ``SharedMemoryManager`` service from " |
| 172 | +"other processes." |
| 173 | +msgstr "" |
| 174 | + |
| 175 | +#: ../Doc/library/multiprocessing.shared_memory.rst:207 |
| 176 | +msgid "" |
| 177 | +"Create and return a new :class:`SharedMemory` object with the specified " |
| 178 | +"``size`` in bytes." |
| 179 | +msgstr "" |
| 180 | + |
| 181 | +#: ../Doc/library/multiprocessing.shared_memory.rst:212 |
| 182 | +msgid "" |
| 183 | +"Create and return a new :class:`ShareableList` object, initialized by the " |
| 184 | +"values from the input ``sequence``." |
| 185 | +msgstr "" |
| 186 | + |
| 187 | +#: ../Doc/library/multiprocessing.shared_memory.rst:216 |
| 188 | +msgid "" |
| 189 | +"The following example demonstrates the basic mechanisms of a :class:" |
| 190 | +"`SharedMemoryManager`:" |
| 191 | +msgstr "" |
| 192 | + |
| 193 | +#: ../Doc/library/multiprocessing.shared_memory.rst:234 |
| 194 | +msgid "" |
| 195 | +"The following example depicts a potentially more convenient pattern for " |
| 196 | +"using :class:`SharedMemoryManager` objects via the :keyword:`with` statement " |
| 197 | +"to ensure that all shared memory blocks are released after they are no " |
| 198 | +"longer needed:" |
| 199 | +msgstr "" |
| 200 | + |
| 201 | +#: ../Doc/library/multiprocessing.shared_memory.rst:253 |
| 202 | +msgid "" |
| 203 | +"When using a :class:`SharedMemoryManager` in a :keyword:`with` statement, " |
| 204 | +"the shared memory blocks created using that manager are all released when " |
| 205 | +"the :keyword:`with` statement's code block finishes execution." |
| 206 | +msgstr "" |
| 207 | + |
| 208 | +#: ../Doc/library/multiprocessing.shared_memory.rst:260 |
| 209 | +msgid "" |
| 210 | +"Provides a mutable list-like object where all values stored within are " |
| 211 | +"stored in a shared memory block. This constrains storable values to only " |
| 212 | +"the ``int``, ``float``, ``bool``, ``str`` (less than 10M bytes each), " |
| 213 | +"``bytes`` (less than 10M bytes each), and ``None`` built-in data types. It " |
| 214 | +"also notably differs from the built-in ``list`` type in that these lists can " |
| 215 | +"not change their overall length (i.e. no append, insert, etc.) and do not " |
| 216 | +"support the dynamic creation of new :class:`ShareableList` instances via " |
| 217 | +"slicing." |
| 218 | +msgstr "" |
| 219 | + |
| 220 | +#: ../Doc/library/multiprocessing.shared_memory.rst:269 |
| 221 | +msgid "" |
| 222 | +"*sequence* is used in populating a new ``ShareableList`` full of values. Set " |
| 223 | +"to ``None`` to instead attach to an already existing ``ShareableList`` by " |
| 224 | +"its unique shared memory name." |
| 225 | +msgstr "" |
| 226 | + |
| 227 | +#: ../Doc/library/multiprocessing.shared_memory.rst:273 |
| 228 | +msgid "" |
| 229 | +"*name* is the unique name for the requested shared memory, as described in " |
| 230 | +"the definition for :class:`SharedMemory`. When attaching to an existing " |
| 231 | +"``ShareableList``, specify its shared memory block's unique name while " |
| 232 | +"leaving ``sequence`` set to ``None``." |
| 233 | +msgstr "" |
| 234 | + |
| 235 | +#: ../Doc/library/multiprocessing.shared_memory.rst:280 |
| 236 | +msgid "Returns the number of occurrences of ``value``." |
| 237 | +msgstr "" |
| 238 | + |
| 239 | +#: ../Doc/library/multiprocessing.shared_memory.rst:284 |
| 240 | +msgid "" |
| 241 | +"Returns first index position of ``value``. Raises :exc:`ValueError` if " |
| 242 | +"``value`` is not present." |
| 243 | +msgstr "" |
| 244 | + |
| 245 | +#: ../Doc/library/multiprocessing.shared_memory.rst:289 |
| 246 | +msgid "" |
| 247 | +"Read-only attribute containing the :mod:`struct` packing format used by all " |
| 248 | +"currently stored values." |
| 249 | +msgstr "" |
| 250 | + |
| 251 | +#: ../Doc/library/multiprocessing.shared_memory.rst:294 |
| 252 | +msgid "The :class:`SharedMemory` instance where the values are stored." |
| 253 | +msgstr "" |
| 254 | + |
| 255 | +#: ../Doc/library/multiprocessing.shared_memory.rst:297 |
| 256 | +msgid "" |
| 257 | +"The following example demonstrates basic use of a :class:`ShareableList` " |
| 258 | +"instance:" |
| 259 | +msgstr "" |
| 260 | + |
| 261 | +#: ../Doc/library/multiprocessing.shared_memory.rst:330 |
| 262 | +msgid "" |
| 263 | +"The following example depicts how one, two, or many processes may access the " |
| 264 | +"same :class:`ShareableList` by supplying the name of the shared memory block " |
| 265 | +"behind it:" |
| 266 | +msgstr "" |
0 commit comments