python-docs-pl/c-api/buffer.po at 3.8 · python/python-docs-pl

Repository navigation

History

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

206

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

222

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

254

255

256

257

258

259

260

261

262

263

264

265

266

267

268

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

286

287

288

289

290

291

292

293

294

295

296

297

298

299

300

301

302

303

304

305

306

307

308

309

310

311

312

313

314

315

316

317

318

319

320

321

322

323

324

325

326

327

328

329

330

331

332

333

334

335

336

337

338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353

354

355

356

357

358

359

360

361

362

363

364

365

366

367

368

369

370

371

372

373

374

375

376

377

378

379

380

381

382

383

384

385

386

387

388

389

390

391

392

393

394

395

396

397

398

399

400

401

402

403

404

405

406

407

408

409

410

411

412

413

414

415

416

417

418

419

420

421

422

423

424

425

426

427

428

429

430

431

432

433

434

435

436

437

438

439

440

441

442

443

444

445

446

447

448

449

450

451

452

453

454

455

456

457

458

459

460

461

462

463

464

465

466

467

468

469

470

471

472

473

474

475

476

477

478

479

480

481

482

483

484

485

486

487

488

489

490

491

492

493

494

495

496

497

498

499

500

501

502

503

504

505

506

507

508

509

510

511

512

513

514

515

516

517

518

519

520

521

522

523

524

525

526

527

528

529

530

531

532

533

534

535

536

537

538

539

540

541

542

543

544

545

546

547

548

549

550

551

552

553

554

555

556

557

# SOME DESCRIPTIVE TITLE.

# This file is distributed under the same license as the Python package.

# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.

# Translators:

# Maciej Olko <maciej.olko@gmail.com>, 2020

#, fuzzy

msgid ""

msgstr ""

"Project-Id-Version: Python 3.8\n"

"Report-Msgid-Bugs-To: \n"

"POT-Creation-Date: 2021-01-01 16:06+0000\n"

"PO-Revision-Date: 2020-05-30 11:47+0000\n"

"Last-Translator: Maciej Olko <maciej.olko@gmail.com>, 2020\n"

"Language-Team: Polish (https://www.transifex.com/python-doc/teams/5390/pl/)\n"

"MIME-Version: 1.0\n"

"Content-Type: text/plain; charset=UTF-8\n"

"Content-Transfer-Encoding: 8bit\n"

"Language: pl\n"

"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "

"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "

"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"

msgid "Buffer Protocol"

msgstr ""

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 ""

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 ""

msgid ""

"Python provides such a facility at the C level in the form of the :ref:"

"`buffer protocol <bufferobjects>`. This protocol has two sides:"

msgstr ""

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 ""

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 ""

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 ""

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 ""

msgid ""

"There are two ways for a consumer of the buffer interface to acquire a "

"buffer over a target object:"

msgstr ""

msgid "call :c:func:`PyObject_GetBuffer` with the right parameters;"

msgstr ""

msgid ""

"call :c:func:`PyArg_ParseTuple` (or one of its siblings) with one of the "

"``y*``, ``w*`` or ``s*`` :ref:`format codes <arg-parsing>`."

msgstr ""

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 ""

msgid "Buffer structure"

msgstr ""

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 ""

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 <memoryview-objects>` object can be "

"created."

msgstr ""

msgid ""

"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`."

msgstr ""

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 ""

msgid ""

"For :term:`contiguous` arrays, the value points to the beginning of the "

"memory block."

msgstr ""

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 ""

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 ""

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 ""

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 ""

msgid ""

"An indicator of whether the buffer is read-only. This field is controlled by "

"the :c:macro:`PyBUF_WRITABLE` flag."

msgstr ""

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 ""

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 ""

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 ""

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 ""

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 ""

msgid "This field is controlled by the :c:macro:`PyBUF_FORMAT` flag."

msgstr ""

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 ""

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 ""

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 ""

msgid ""

"Shape values are restricted to ``shape[n] >= 0``. The case ``shape[n] == 0`` "

"requires special attention. See `complex arrays`_ for further information."

msgstr ""

msgid "The shape array is read-only for the consumer."

msgstr ""

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 ""

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``. See `complex arrays`_ for further information."

msgstr ""

msgid "The strides array is read-only for the consumer."

msgstr ""

msgid ""

"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)."

msgstr ""

msgid ""

"If all suboffsets are negative (i.e. no de-referencing is needed), then this "

"field must be ``NULL`` (the default value)."

msgstr ""

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 ""

msgid "The suboffsets array is read-only for the consumer."

msgstr ""

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 ""

msgid "Buffer request types"

msgstr ""

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 ""

msgid ""

"All :c:data:`Py_buffer` fields are unambiguously defined by the request type."

msgstr ""

msgid "request-independent fields"

msgstr ""

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 ""

msgid "readonly, format"

msgstr ""

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 ""

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 ""

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 ""

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 ""

msgid "shape, strides, suboffsets"

msgstr ""

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 ""

msgid "Request"

msgstr ""

msgid "shape"

msgstr ""

msgid "strides"

msgstr ""

msgid "suboffsets"

msgstr ""

msgid "yes"

msgstr "tak"

msgid "if needed"

msgstr ""

msgid "NULL"

msgstr ""

msgid "contiguity requests"

msgstr ""

msgid ""

"C or Fortran :term:`contiguity <contiguous>` can be explicitly requested, "

"with and without stride information. Without stride information, the buffer "

"must be C-contiguous."

msgstr ""

msgid "contig"

msgstr ""

msgid "C"

msgstr ""

msgid "F"

msgstr ""

msgid "C or F"

msgstr ""

msgid ":c:macro:`PyBUF_ND`"

msgstr ""

msgid "compound requests"

msgstr ""

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 ""

msgid ""

"In the following table *U* stands for undefined contiguity. The consumer "

"would have to call :c:func:`PyBuffer_IsContiguous` to determine contiguity."

msgstr ""

msgid "readonly"

msgstr ""

msgid "format"

msgstr ""

msgid "U"

msgstr ""

msgid "0"

msgstr "0"

msgid "1 or 0"

msgstr ""

msgid "Complex arrays"

msgstr ""

msgid "NumPy-style: shape and strides"

msgstr ""

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 ""

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 ""

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 ""

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 ""

msgid "PIL-style: shape, strides and suboffsets"

msgstr ""

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 ""

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 ""

msgid "Buffer-related functions"

msgstr ""

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. This function always succeeds."

msgstr ""

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 ``view->obj`` to ``NULL`` and return ``-1``."

msgstr ""

msgid ""

"On success, fill in *view*, set ``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, ``view->obj`` MAY refer to this object "

"instead of *exporter* (See :ref:`Buffer Object Structures <buffer-structs>`)."

msgstr ""

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 ""

msgid ""

"Release the buffer *view* and decrement the reference count for ``view-"

">obj``. This function MUST be called when the buffer is no longer being "

"used, otherwise reference leaks may occur."

msgstr ""

msgid ""

"It is an error to call this function on a buffer that was not obtained via :"

"c:func:`PyObject_GetBuffer`."

msgstr ""

msgid ""

"Return the implied :c:data:`~Py_buffer.itemsize` from :c:data:`~Py_buffer."

"format`. This function is not yet implemented."

msgstr ""

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. This function always "

"succeeds."

msgstr ""

msgid ""

"Get the memory area pointed to by the *indices* inside the given *view*. "

"*indices* must point to an array of ``view->ndim`` indices."

msgstr ""

msgid ""

"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 ""

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 ""

msgid "This function fails if *len* != *src->len*."

msgstr ""

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 ""

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 ""

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 ""

msgid ""

"On success, set ``view->obj`` to a new reference to *exporter* and return 0. "

"Otherwise, raise :c:data:`PyExc_BufferError`, set ``view->obj`` to ``NULL`` "

"and return ``-1``;"

msgstr ""

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 "

"unmodified. Otherwise, *exporter* MUST be ``NULL``."

msgstr ""

FilesExpand file tree

buffer.po

Latest commit

History

buffer.po

File metadata and controls