python-docs-fa/extending/newtypes.html at gh-pages · python/python-docs-fa

History

1013 lines (937 loc) · 101 KB

Raw

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

558

559

560

561

562

563

564

565

566

567

568

569

570

571

572

573

574

575

576

577

578

579

580

581

582

583

584

585

586

587

588

589

590

591

592

593

594

595

596

597

598

599

600

601

602

603

604

605

606

607

608

609

610

611

612

613

614

615

616

617

618

619

620

621

622

623

624

625

626

627

628

629

630

631

632

633

634

635

636

637

638

639

640

641

642

643

644

645

646

647

648

649

650

651

652

653

654

655

656

657

658

659

660

661

662

663

664

665

666

667

668

669

670

671

672

673

674

675

676

677

678

679

680

681

682

683

684

685

686

687

688

689

690

691

692

693

694

695

696

697

698

699

700

701

702

703

704

705

706

707

708

709

710

711

712

713

714

715

716

717

718

719

720

721

722

723

724

725

726

727

728

729

730

731

732

733

734

735

736

737

738

739

740

741

742

743

744

745

746

747

748

749

750

751

752

753

754

755

756

757

758

759

760

761

762

763

764

765

766

767

768

769

770

771

772

773

774

775

776

777

778

779

780

781

782

783

784

785

786

787

788

789

790

791

792

793

794

795

796

797

798

799

800

801

802

803

804

805

806

807

808

809

810

811

812

813

814

815

816

817

818

819

820

821

822

823

824

825

826

827

828

829

830

831

832

833

834

835

836

837

838

839

840

841

842

843

844

845

846

847

848

849

850

851

852

853

854

855

856

857

858

859

860

861

862

863

864

865

866

867

868

869

870

871

872

873

874

875

876

877

878

879

880

881

882

883

884

885

886

887

888

889

890

891

892

893

894

895

896

897

898

899

900

901

902

903

904

905

906

907

908

909

910

911

912

913

914

915

916

917

918

919

920

921

922

923

924

925

926

927

928

929

930

931

932

933

934

935

936

937

938

939

940

941

942

943

944

945

946

947

948

949

950

951

952

953

954

955

956

957

958

959

960

961

962

963

964

965

966

967

968

969

970

971

972

973

974

975

976

977

978

979

980

981

982

983

984

985

986

987

988

989

990

991

992

993

994

995

996

997

998

999

1000

<!DOCTYPE html>

<head>

<title>3. Defining Extension Types: Assorted Topics — مستندات Python3.14.6</title><meta name="viewport" content="width=device-width, initial-scale=1.0">

title="جستجو در مستندات Python3.14.6"

href="../_static/opensearch.xml"/>

<style>

@media only screen {

table.full-width-table {

width: 100%;

}

</style>

</head>

<body>

<input type="checkbox" id="menuToggler" class="toggler__input" aria-controls="navigation"

aria-pressed="false" aria-expanded="false" role="button" aria-label="Menu">

</label>

</a>

</svg>

</form>

</nav>

Theme

<option value="light">Light</option>

</select>

</label>

<div>

<h3><a href="../contents.html">فهرست عناوین</a></h3>

<ul>

<li><a class="reference internal" href="#">3. Defining Extension Types: Assorted Topics</a><ul>

<li><a class="reference internal" href="#finalization-and-de-allocation">3.1. Finalization and De-allocation</a></li>

<li><a class="reference internal" href="#object-presentation">3.2. Object Presentation</a></li>

<li><a class="reference internal" href="#attribute-management">3.3. Attribute Management</a><ul>

<li><a class="reference internal" href="#generic-attribute-management">3.3.1. Generic Attribute Management</a></li>

<li><a class="reference internal" href="#type-specific-attribute-management">3.3.2. Type-specific Attribute Management</a></li>

</ul>

</li>

<li><a class="reference internal" href="#object-comparison">3.4. Object Comparison</a></li>

<li><a class="reference internal" href="#abstract-protocol-support">3.5. Abstract Protocol Support</a></li>

<li><a class="reference internal" href="#weak-reference-support">3.6. Weak Reference Support</a></li>

<li><a class="reference internal" href="#more-suggestions">3.7. More Suggestions</a></li>

</ul>

</li>

</ul>

</div>

<div>

<h4>موضوع قبلی</h4>

<a href="newtypes_tutorial.html"

title="فصل قبلی">2. Defining Extension Types: Tutorial</a>

</div>

<div>

<h4>موضوع بعدی</h4>

<a href="building.html"

title="فصل بعدی">4. Building C and C++ Extensions</a>

</div>

document.addEventListener('DOMContentLoaded', () => {

const title = document.querySelector('meta[property="og:title"]').content;

const elements = document.querySelectorAll('.improvepage');

const pageurl = window.location.href.split('?')[0];

elements.forEach(element => {

const url = new URL(element.href.split('?')[0].replace("-nojs", ""));

url.searchParams.set('pagetitle', title);

url.searchParams.set('pageurl', pageurl);

url.searchParams.set('pagesource', "extending/newtypes.rst");

element.href = url.toString();

});

</script>

<li><a href="../bugs.html">گزارش یک اشکال</a></li>

<li><a class="improvepage" href="../improve-page-nojs.html">بهبود این صفحه</a></li>

<li>

<a href="https://github.com/python/cpython/blob/main/Doc/extending/newtypes.rst?plain=1"

rel="nofollow">نمایش منبع

</a>

</li>

<li>

<a href="https://github.com/python/python-docs-fa/blob/3.14/extending/newtypes.po?plain=1"

rel="nofollow">نمایش منبع ترجمه</a>

</li>

</ul>

</div>

</nav>

</div>

<h3>ناوبری</h3>

<ul>

<a href="../genindex.html" title="فهرست کلی"

accesskey="I">فهرست</a></li>

<a href="../py-modindex.html" title="نمایه ی ماژول های پایتون"

>ماژول ها</a> |</li>

<a href="building.html" title="4. Building C and C++ Extensions"

accesskey="N">بعدی</a> |</li>

<a href="newtypes_tutorial.html" title="2. Defining Extension Types: Tutorial"

accesskey="P">قبلی</a> |</li>

<li><a href="https://www.python.org/">Python</a> »</li>

</li>

<li>

</li>

<a href="../index.html">3.14.6 Documentation</a> »

</li>

<li class="nav-item nav-item-1"><a href="index.html" accesskey="U">Extending and Embedding the Python Interpreter</a> »</li>

<li class="nav-item nav-item-this"><a href="">3. Defining Extension Types: Assorted Topics</a></li>

</form>

</div>

</li>

Theme

<option value="light">Light</option>

</select>

</label> |</li>

</ul>

</div>

<h1>3. Defining Extension Types: Assorted Topics<a class="headerlink" href="#defining-extension-types-assorted-topics" title="Link to this heading">¶</a></h1>

This section aims to give a quick fly-by on the various type methods you can

implement and what they do.

Here is the definition of <a class="reference internal" href="../c-api/type.html#c.PyTypeObject" title="PyTypeObject"><code class="xref c c-type docutils literal notranslate">PyTypeObject</code></a>, with some fields only used in

<a class="reference internal" href="../using/configure.html#debug-build">debug builds</a> omitted:

<div class="highlight-c notranslate"><div class="highlight"><pre>typedef struct _typeobject {

PyObject_VAR_HEAD

const char *tp_name; /* For printing, in format "<module>.<name>" */

Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */

/* Methods to implement standard operations */

destructor tp_dealloc;

Py_ssize_t tp_vectorcall_offset;

getattrfunc tp_getattr;

setattrfunc tp_setattr;

PyAsyncMethods *tp_as_async; /* formerly known as tp_compare (Python 2)

or tp_reserved (Python 3) */

reprfunc tp_repr;

/* Method suites for standard classes */

PyNumberMethods *tp_as_number;

PySequenceMethods *tp_as_sequence;

PyMappingMethods *tp_as_mapping;

/* More standard operations (here for binary compatibility) */

hashfunc tp_hash;

ternaryfunc tp_call;

reprfunc tp_str;

getattrofunc tp_getattro;

setattrofunc tp_setattro;

/* Functions to access object as input/output buffer */

PyBufferProcs *tp_as_buffer;

/* Flags to define presence of optional/expanded features */

unsigned long tp_flags;

const char *tp_doc; /* Documentation string */

/* Assigned meaning in release 2.0 */

/* call function for all accessible objects */

traverseproc tp_traverse;

/* delete references to contained objects */

inquiry tp_clear;

/* Assigned meaning in release 2.1 */

/* rich comparisons */

richcmpfunc tp_richcompare;

/* weak reference enabler */

Py_ssize_t tp_weaklistoffset;

/* Iterators */

getiterfunc tp_iter;

iternextfunc tp_iternext;

/* Attribute descriptor and subclassing stuff */

PyMethodDef *tp_methods;

PyMemberDef *tp_members;

PyGetSetDef *tp_getset;

// Strong reference on a heap type, borrowed reference on a static type

PyTypeObject *tp_base;

PyObject *tp_dict;

descrgetfunc tp_descr_get;

descrsetfunc tp_descr_set;

Py_ssize_t tp_dictoffset;

initproc tp_init;

allocfunc tp_alloc;

newfunc tp_new;

freefunc tp_free; /* Low-level free-memory routine */

inquiry tp_is_gc; /* For PyObject_IS_GC */

PyObject *tp_bases;

PyObject *tp_mro; /* method resolution order */

PyObject *tp_cache; /* no longer used */

void *tp_subclasses; /* for static builtin types this is an index */

PyObject *tp_weaklist; /* not used for static builtin types */

destructor tp_del;

/* Type attribute cache version tag. Added in version 2.6.

* If zero, the cache is invalid and must be initialized.

*/

unsigned int tp_version_tag;

destructor tp_finalize;

vectorcallfunc tp_vectorcall;

/* bitset of which type-watchers care about this type */

unsigned char tp_watched;

/* Number of tp_version_tag values used.

* Set to _Py_ATTR_CACHE_UNUSED if the attribute cache is

* disabled for this type (e.g. due to custom MRO entries).

* Otherwise, limited to MAX_VERSIONS_PER_CLASS (defined elsewhere).

*/

uint16_t tp_versions_used;

} PyTypeObject;

</pre></div>

</div>

Now that's a lot of methods. Don't worry too much though -- if you have

a type you want to define, the chances are very good that you will only

implement a handful of these.

As you probably expect by now, we're going to go over this and give more

information about the various handlers. We won't go in the order they are

defined in the structure, because there is a lot of historical baggage that

impacts the ordering of the fields. It's often easiest to find an example

that includes the fields you need and then change the values to suit your new

type.

<div class="highlight-c notranslate"><div class="highlight"><pre>const char *tp_name; /* For printing */

</pre></div>

</div>

The name of the type -- as mentioned in the previous chapter, this will appear in

various places, almost entirely for diagnostic purposes. Try to choose something

that will be helpful in such a situation!

<div class="highlight-c notranslate"><div class="highlight"><pre>Py_ssize_t tp_basicsize, tp_itemsize; /* For allocation */

</pre></div>

</div>

These fields tell the runtime how much memory to allocate when new objects of

this type are created. Python has some built-in support for variable length

structures (think: strings, tuples) which is where the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_itemsize" title="PyTypeObject.tp_itemsize"><code class="xref c c-member docutils literal notranslate">tp_itemsize</code></a> field

comes in. This will be dealt with later.

</pre></div>

</div>

Here you can put a string (or its address) that you want returned when the

Python script references <code class="docutils literal notranslate">obj.__doc__</code> to retrieve the doc string.

Now we come to the basic type methods -- the ones most extension types will

implement.

<h2>3.1. Finalization and De-allocation<a class="headerlink" href="#finalization-and-de-allocation" title="Link to this heading">¶</a></h2>

<div class="highlight-c notranslate" id="index-0"><div class="highlight"><pre>destructor tp_dealloc;

</pre></div>

</div>

This function is called when the reference count of the instance of your type is

reduced to zero and the Python interpreter wants to reclaim it. If your type

has memory to free or other clean-up to perform, you can put it here. The

object itself needs to be freed here as well. Here is an example of this

function:

<div class="highlight-c notranslate"><div class="highlight"><pre>static void

newdatatype_dealloc(PyObject *op)

{

newdatatypeobject *self = (newdatatypeobject *) op;

free(self->obj_UnderlyingDatatypePtr);

Py_TYPE(self)->tp_free(self);

}

</pre></div>

</div>

If your type supports garbage collection, the destructor should call

<a class="reference internal" href="../c-api/gcsupport.html#c.PyObject_GC_UnTrack" title="PyObject_GC_UnTrack"><code class="xref c c-func docutils literal notranslate">PyObject_GC_UnTrack()</code></a> before clearing any member fields:

<div class="highlight-c notranslate"><div class="highlight"><pre>static void

newdatatype_dealloc(PyObject *op)

{

PyObject_GC_UnTrack(op);

Py_CLEAR(self->other_obj);

...

}

</pre></div>

</div>

One important requirement of the deallocator function is that it leaves any

pending exceptions alone. This is important since deallocators are frequently

called as the interpreter unwinds the Python stack; when the stack is unwound

due to an exception (rather than normal returns), nothing is done to protect the

deallocators from seeing that an exception has already been set. Any actions

which a deallocator performs which may cause additional Python code to be

executed may detect that an exception has been set. This can lead to misleading

errors from the interpreter. The proper way to protect against this is to save

a pending exception before performing the unsafe action, and restoring it when

done. This can be done using the <a class="reference internal" href="../c-api/exceptions.html#c.PyErr_Fetch" title="PyErr_Fetch"><code class="xref c c-func docutils literal notranslate">PyErr_Fetch()</code></a> and

<a class="reference internal" href="../c-api/exceptions.html#c.PyErr_Restore" title="PyErr_Restore"><code class="xref c c-func docutils literal notranslate">PyErr_Restore()</code></a> functions:

<div class="highlight-c notranslate"><div class="highlight"><pre>static void

my_dealloc(PyObject *obj)

{

MyObject *self = (MyObject *) obj;

PyObject *cbresult;

if (self->my_callback != NULL) {

PyObject *err_type, *err_value, *err_traceback;

/* This saves the current exception state */

PyErr_Fetch(&err_type, &err_value, &err_traceback);

cbresult = PyObject_CallNoArgs(self->my_callback);

if (cbresult == NULL) {

PyErr_WriteUnraisable(self->my_callback);

}

else {

Py_DECREF(cbresult);

}

/* This restores the saved exception state */

PyErr_Restore(err_type, err_value, err_traceback);

Py_DECREF(self->my_callback);

}

}

</pre></div>

</div>

توجه

There are limitations to what you can safely do in a deallocator function.

First, if your type supports garbage collection (using <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_traverse" title="PyTypeObject.tp_traverse"><code class="xref c c-member docutils literal notranslate">tp_traverse</code></a>

and/or <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_clear" title="PyTypeObject.tp_clear"><code class="xref c c-member docutils literal notranslate">tp_clear</code></a>), some of the object's members can have been

cleared or finalized by the time <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_dealloc" title="PyTypeObject.tp_dealloc"><code class="xref c c-member docutils literal notranslate">tp_dealloc</code></a> is called. Second, in

<code class="xref c c-member docutils literal notranslate">tp_dealloc</code>, your object is in an unstable state: its reference

count is equal to zero. Any call to a non-trivial object or API (as in the

example above) might end up calling <code class="xref c c-member docutils literal notranslate">tp_dealloc</code> again, causing a

double free and a crash.

Starting with Python 3.4, it is recommended not to put any complex

finalization code in <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_dealloc" title="PyTypeObject.tp_dealloc"><code class="xref c c-member docutils literal notranslate">tp_dealloc</code></a>, and instead use the new

<a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_finalize" title="PyTypeObject.tp_finalize"><code class="xref c c-member docutils literal notranslate">tp_finalize</code></a> type method.

همچنین ملاحظه نمائید

<a class="pep reference external" href="https://peps.python.org/pep-0442/">PEP 442</a> explains the new finalization scheme.

</div>

</section>

<h2>3.2. Object Presentation<a class="headerlink" href="#object-presentation" title="Link to this heading">¶</a></h2>

In Python, there are two ways to generate a textual representation of an object:

the <a class="reference internal" href="../library/functions.html#repr" title="repr"><code class="xref py py-func docutils literal notranslate">repr()</code></a> function, and the <a class="reference internal" href="../library/stdtypes.html#str" title="str"><code class="xref py py-func docutils literal notranslate">str()</code></a> function. (The <a class="reference internal" href="../library/functions.html#print" title="print"><code class="xref py py-func docutils literal notranslate">print()</code></a>

function just calls <code class="xref py py-func docutils literal notranslate">str()</code>.) These handlers are both optional.

<div class="highlight-c notranslate"><div class="highlight"><pre>reprfunc tp_repr;

reprfunc tp_str;

</pre></div>

</div>

The <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_repr" title="PyTypeObject.tp_repr"><code class="xref c c-member docutils literal notranslate">tp_repr</code></a> handler should return a string object containing a

representation of the instance for which it is called. Here is a simple

example:

<div class="highlight-c notranslate"><div class="highlight"><pre>static PyObject *

newdatatype_repr(PyObject *op)

{

return PyUnicode_FromFormat("Repr-ified_newdatatype{{size:%d}}",

self->obj_UnderlyingDatatypePtr->size);

}

</pre></div>

</div>

If no <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_repr" title="PyTypeObject.tp_repr"><code class="xref c c-member docutils literal notranslate">tp_repr</code></a> handler is specified, the interpreter will supply a

representation that uses the type's <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_name" title="PyTypeObject.tp_name"><code class="xref c c-member docutils literal notranslate">tp_name</code></a> and a uniquely identifying

value for the object.

The <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_str" title="PyTypeObject.tp_str"><code class="xref c c-member docutils literal notranslate">tp_str</code></a> handler is to <a class="reference internal" href="../library/stdtypes.html#str" title="str"><code class="xref py py-func docutils literal notranslate">str()</code></a> what the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_repr" title="PyTypeObject.tp_repr"><code class="xref c c-member docutils literal notranslate">tp_repr</code></a> handler

described above is to <a class="reference internal" href="../library/functions.html#repr" title="repr"><code class="xref py py-func docutils literal notranslate">repr()</code></a>; that is, it is called when Python code calls

<code class="xref py py-func docutils literal notranslate">str()</code> on an instance of your object. Its implementation is very similar

to the <code class="xref c c-member docutils literal notranslate">tp_repr</code> function, but the resulting string is intended for human

consumption. If <code class="xref c c-member docutils literal notranslate">tp_str</code> is not specified, the <code class="xref c c-member docutils literal notranslate">tp_repr</code> handler is

used instead.

Here is a simple example:

newdatatype_str(PyObject *op)

{

return PyUnicode_FromFormat("Stringified_newdatatype{{size:%d}}",

}

</pre></div>

</div>

</section>

<h2>3.3. Attribute Management<a class="headerlink" href="#attribute-management" title="Link to this heading">¶</a></h2>

For every object which can support attributes, the corresponding type must

provide the functions that control how the attributes are resolved. There needs

to be a function which can retrieve attributes (if any are defined), and another

to set attributes (if setting attributes is allowed). Removing an attribute is

a special case, for which the new value passed to the handler is <code class="docutils literal notranslate">NULL</code>.

Python supports two pairs of attribute handlers; a type that supports attributes

only needs to implement the functions for one pair. The difference is that one

pair takes the name of the attribute as a char*, while the other

accepts a <a class="reference internal" href="../c-api/structures.html#c.PyObject" title="PyObject">PyObject</a>*. Each type can use whichever pair makes more

sense for the implementation's convenience.

<div class="highlight-c notranslate"><div class="highlight"><pre>getattrfunc tp_getattr; /* char * version */

setattrfunc tp_setattr;

/* ... */

getattrofunc tp_getattro; /* PyObject * version */

setattrofunc tp_setattro;

</pre></div>

</div>

If accessing attributes of an object is always a simple operation (this will be

explained shortly), there are generic implementations which can be used to

provide the <a class="reference internal" href="../c-api/structures.html#c.PyObject" title="PyObject">PyObject</a>* version of the attribute management functions.

The actual need for type-specific attribute handlers almost completely

disappeared starting with Python 2.2, though there are many examples which have

not been updated to use some of the new generic mechanism that is available.

<h3>3.3.1. Generic Attribute Management<a class="headerlink" href="#generic-attribute-management" title="Link to this heading">¶</a></h3>

Most extension types only use simple attributes. So, what makes the

attributes simple? There are only a couple of conditions that must be met:

<li>The name of the attributes must be known when <a class="reference internal" href="../c-api/type.html#c.PyType_Ready" title="PyType_Ready"><code class="xref c c-func docutils literal notranslate">PyType_Ready()</code></a> is

called.</li>

<li>No special processing is needed to record that an attribute was looked up or

set, nor do actions need to be taken based on the value.</li>

</ol>

Note that this list does not place any restrictions on the values of the

attributes, when the values are computed, or how relevant data is stored.

When <a class="reference internal" href="../c-api/type.html#c.PyType_Ready" title="PyType_Ready"><code class="xref c c-func docutils literal notranslate">PyType_Ready()</code></a> is called, it uses three tables referenced by the

type object to create <a class="reference internal" href="../glossary.html#term-descriptor">descriptor</a>s which are placed in the dictionary of the

type object. Each descriptor controls access to one attribute of the instance

object. Each of the tables is optional; if all three are <code class="docutils literal notranslate">NULL</code>, instances of

the type will only have attributes that are inherited from their base type, and

should leave the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_getattro" title="PyTypeObject.tp_getattro"><code class="xref c c-member docutils literal notranslate">tp_getattro</code></a> and <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_setattro" title="PyTypeObject.tp_setattro"><code class="xref c c-member docutils literal notranslate">tp_setattro</code></a> fields <code class="docutils literal notranslate">NULL</code> as

well, allowing the base type to handle attributes.

The tables are declared as three fields of the type object:

<div class="highlight-c notranslate"><div class="highlight"><pre>struct PyMethodDef *tp_methods;

struct PyMemberDef *tp_members;

struct PyGetSetDef *tp_getset;

</pre></div>

</div>

If <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_methods" title="PyTypeObject.tp_methods"><code class="xref c c-member docutils literal notranslate">tp_methods</code></a> is not <code class="docutils literal notranslate">NULL</code>, it must refer to an array of

<a class="reference internal" href="../c-api/structures.html#c.PyMethodDef" title="PyMethodDef"><code class="xref c c-type docutils literal notranslate">PyMethodDef</code></a> structures. Each entry in the table is an instance of this

structure:

<div class="highlight-c notranslate"><div class="highlight"><pre>typedef struct PyMethodDef {

const char *ml_name; /* method name */

PyCFunction ml_meth; /* implementation function */

int ml_flags; /* flags */

const char *ml_doc; /* docstring */

} PyMethodDef;

</pre></div>

</div>

One entry should be defined for each method provided by the type; no entries are

needed for methods inherited from a base type. One additional entry is needed

at the end; it is a sentinel that marks the end of the array. The

<a class="reference internal" href="../c-api/structures.html#c.PyMethodDef.ml_name" title="PyMethodDef.ml_name"><code class="xref c c-member docutils literal notranslate">ml_name</code></a> field of the sentinel must be <code class="docutils literal notranslate">NULL</code>.

The second table is used to define attributes which map directly to data stored

in the instance. A variety of primitive C types are supported, and access may

be read-only or read-write. The structures in the table are defined as:

<div class="highlight-c notranslate"><div class="highlight"><pre>typedef struct PyMemberDef {

int type;

int offset;

int flags;

} PyMemberDef;

</pre></div>

</div>

For each entry in the table, a <a class="reference internal" href="../glossary.html#term-descriptor">descriptor</a> will be constructed and added to the

type which will be able to extract a value from the instance structure. The

<a class="reference internal" href="../c-api/structures.html#c.PyMemberDef.type" title="PyMemberDef.type"><code class="xref c c-member docutils literal notranslate">type</code></a> field should contain a type code like <a class="reference internal" href="../c-api/structures.html#c.Py_T_INT" title="Py_T_INT"><code class="xref c c-macro docutils literal notranslate">Py_T_INT</code></a> or

<a class="reference internal" href="../c-api/structures.html#c.Py_T_DOUBLE" title="Py_T_DOUBLE"><code class="xref c c-macro docutils literal notranslate">Py_T_DOUBLE</code></a>; the value will be used to determine how to

convert Python values to and from C values. The <a class="reference internal" href="../c-api/structures.html#c.PyMemberDef.flags" title="PyMemberDef.flags"><code class="xref c c-member docutils literal notranslate">flags</code></a> field is used to

store flags which control how the attribute can be accessed: you can set it to

<a class="reference internal" href="../c-api/structures.html#c.Py_READONLY" title="Py_READONLY"><code class="xref c c-macro docutils literal notranslate">Py_READONLY</code></a> to prevent Python code from setting it.

An interesting advantage of using the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_members" title="PyTypeObject.tp_members"><code class="xref c c-member docutils literal notranslate">tp_members</code></a> table to build

descriptors that are used at runtime is that any attribute defined this way can

have an associated doc string simply by providing the text in the table. An

application can use the introspection API to retrieve the descriptor from the

class object, and get the doc string using its <a class="reference internal" href="../reference/datamodel.html#type.__doc__" title="type.__doc__"><code class="xref py py-attr docutils literal notranslate">__doc__</code></a> attribute.

As with the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_methods" title="PyTypeObject.tp_methods"><code class="xref c c-member docutils literal notranslate">tp_methods</code></a> table, a sentinel entry with a <a class="reference internal" href="../c-api/structures.html#c.PyMethodDef.ml_name" title="PyMethodDef.ml_name"><code class="xref c c-member docutils literal notranslate">ml_name</code></a> value

of <code class="docutils literal notranslate">NULL</code> is required.

</section>

<h3>3.3.2. Type-specific Attribute Management<a class="headerlink" href="#type-specific-attribute-management" title="Link to this heading">¶</a></h3>

For simplicity, only the char* version will be demonstrated here; the

type of the name parameter is the only difference between the char*

and <a class="reference internal" href="../c-api/structures.html#c.PyObject" title="PyObject">PyObject</a>* flavors of the interface. This example effectively does

the same thing as the generic example above, but does not use the generic

support added in Python 2.2. It explains how the handler functions are

called, so that if you do need to extend their functionality, you'll understand

what needs to be done.

The <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_getattr" title="PyTypeObject.tp_getattr"><code class="xref c c-member docutils literal notranslate">tp_getattr</code></a> handler is called when the object requires an attribute

look-up. It is called in the same situations where the <a class="reference internal" href="../reference/datamodel.html#object.__getattr__" title="object.__getattr__"><code class="xref py py-meth docutils literal notranslate">__getattr__()</code></a>

method of a class would be called.

Here is an example:

newdatatype_getattr(PyObject *op, char *name)

{

if (strcmp(name, "data") == 0) {

return PyLong_FromLong(self->data);

}

PyErr_Format(PyExc_AttributeError,

"'%.100s' object has no attribute '%.400s'",

Py_TYPE(self)->tp_name, name);

return NULL;

}

</pre></div>

</div>

The <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_setattr" title="PyTypeObject.tp_setattr"><code class="xref c c-member docutils literal notranslate">tp_setattr</code></a> handler is called when the <a class="reference internal" href="../reference/datamodel.html#object.__setattr__" title="object.__setattr__"><code class="xref py py-meth docutils literal notranslate">__setattr__()</code></a> or

<a class="reference internal" href="../reference/datamodel.html#object.__delattr__" title="object.__delattr__"><code class="xref py py-meth docutils literal notranslate">__delattr__()</code></a> method of a class instance would be called. When an

attribute should be deleted, the third parameter will be <code class="docutils literal notranslate">NULL</code>. Here is an

example that simply raises an exception; if this were really all you wanted, the

<code class="xref c c-member docutils literal notranslate">tp_setattr</code> handler should be set to <code class="docutils literal notranslate">NULL</code>.

<div class="highlight-c notranslate"><div class="highlight"><pre>static int

newdatatype_setattr(PyObject *op, char *name, PyObject *v)

{

PyErr_Format(PyExc_RuntimeError, "Read-only attribute: %s", name);

return -1;

}

</pre></div>

</div>

</section>

<h2>3.4. Object Comparison<a class="headerlink" href="#object-comparison" title="Link to this heading">¶</a></h2>

<div class="highlight-c notranslate"><div class="highlight"><pre>richcmpfunc tp_richcompare;

</pre></div>

</div>

The <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_richcompare" title="PyTypeObject.tp_richcompare"><code class="xref c c-member docutils literal notranslate">tp_richcompare</code></a> handler is called when comparisons are needed. It is

analogous to the <a class="reference internal" href="../reference/datamodel.html#richcmpfuncs">rich comparison methods</a>, like

<code class="xref py py-meth docutils literal notranslate">__lt__()</code>, and also called by <a class="reference internal" href="../c-api/object.html#c.PyObject_RichCompare" title="PyObject_RichCompare"><code class="xref c c-func docutils literal notranslate">PyObject_RichCompare()</code></a> and

<a class="reference internal" href="../c-api/object.html#c.PyObject_RichCompareBool" title="PyObject_RichCompareBool"><code class="xref c c-func docutils literal notranslate">PyObject_RichCompareBool()</code></a>.

This function is called with two Python objects and the operator as arguments,

where the operator is one of <code class="docutils literal notranslate">Py_EQ</code>, <code class="docutils literal notranslate">Py_NE</code>, <code class="docutils literal notranslate">Py_LE</code>, <code class="docutils literal notranslate">Py_GE</code>,

<code class="docutils literal notranslate">Py_LT</code> or <code class="docutils literal notranslate">Py_GT</code>. It should compare the two objects with respect to the

specified operator and return <code class="docutils literal notranslate">Py_True</code> or <code class="docutils literal notranslate">Py_False</code> if the comparison is

successful, <code class="docutils literal notranslate">Py_NotImplemented</code> to indicate that comparison is not

implemented and the other object's comparison method should be tried, or <code class="docutils literal notranslate">NULL</code>

if an exception was set.

Here is a sample implementation, for a datatype that is considered equal if the

size of an internal pointer is equal:

newdatatype_richcmp(PyObject *lhs, PyObject *rhs, int op)

{

newdatatypeobject *obj1 = (newdatatypeobject *) lhs;

newdatatypeobject *obj2 = (newdatatypeobject *) rhs;

PyObject *result;

int c, size1, size2;

/* code to make sure that both arguments are of type

newdatatype omitted */

size1 = obj1->obj_UnderlyingDatatypePtr->size;

size2 = obj2->obj_UnderlyingDatatypePtr->size;

switch (op) {

case Py_LT: c = size1 < size2; break;

case Py_LE: c = size1 <= size2; break;

case Py_EQ: c = size1 == size2; break;

case Py_NE: c = size1 != size2; break;

case Py_GT: c = size1 > size2; break;

case Py_GE: c = size1 >= size2; break;

}

result = c ? Py_True : Py_False;

return Py_NewRef(result);

}

</pre></div>

</div>

</section>

<h2>3.5. Abstract Protocol Support<a class="headerlink" href="#abstract-protocol-support" title="Link to this heading">¶</a></h2>

Python supports a variety of abstract 'protocols;' the specific interfaces

provided to use these interfaces are documented in <a class="reference internal" href="../c-api/abstract.html#abstract">لایه اشیاء انتزاعی (Abstract Objects Layer)</a>.

A number of these abstract interfaces were defined early in the development of

the Python implementation. In particular, the number, mapping, and sequence

protocols have been part of Python since the beginning. Other protocols have

been added over time. For protocols which depend on several handler routines

from the type implementation, the older protocols have been defined as optional

blocks of handlers referenced by the type object. For newer protocols there are

additional slots in the main type object, with a flag bit being set to indicate

that the slots are present and should be checked by the interpreter. (The flag

bit does not indicate that the slot values are non-<code class="docutils literal notranslate">NULL</code>. The flag may be set

to indicate the presence of a slot, but a slot may still be unfilled.)

<div class="highlight-c notranslate"><div class="highlight"><pre>PyNumberMethods *tp_as_number;

PySequenceMethods *tp_as_sequence;

PyMappingMethods *tp_as_mapping;

</pre></div>

</div>

If you wish your object to be able to act like a number, a sequence, or a

mapping object, then you place the address of a structure that implements the C

type <a class="reference internal" href="../c-api/typeobj.html#c.PyNumberMethods" title="PyNumberMethods"><code class="xref c c-type docutils literal notranslate">PyNumberMethods</code></a>, <a class="reference internal" href="../c-api/typeobj.html#c.PySequenceMethods" title="PySequenceMethods"><code class="xref c c-type docutils literal notranslate">PySequenceMethods</code></a>, or

<a class="reference internal" href="../c-api/typeobj.html#c.PyMappingMethods" title="PyMappingMethods"><code class="xref c c-type docutils literal notranslate">PyMappingMethods</code></a>, respectively. It is up to you to fill in this

structure with appropriate values. You can find examples of the use of each of

these in the <code class="file docutils literal notranslate">Objects</code> directory of the Python source distribution.

<div class="highlight-c notranslate"><div class="highlight"><pre>hashfunc tp_hash;

</pre></div>

</div>

This function, if you choose to provide it, should return a hash number for an

instance of your data type. Here is a simple example:

<div class="highlight-c notranslate"><div class="highlight"><pre>static Py_hash_t

newdatatype_hash(PyObject *op)

{

Py_hash_t result;

result = self->some_size + 32767 * self->some_number;

if (result == -1) {

result = -2;

}

return result;

}

</pre></div>

</div>

<a class="reference internal" href="../c-api/hash.html#c.Py_hash_t" title="Py_hash_t"><code class="xref c c-type docutils literal notranslate">Py_hash_t</code></a> is a signed integer type with a platform-varying width.

Returning <code class="docutils literal notranslate">-1</code> from <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_hash" title="PyTypeObject.tp_hash"><code class="xref c c-member docutils literal notranslate">tp_hash</code></a> indicates an error,

which is why you should be careful to avoid returning it when hash computation

is successful, as seen above.

<div class="highlight-c notranslate"><div class="highlight"><pre>ternaryfunc tp_call;

</pre></div>

</div>

This function is called when an instance of your data type is "called", for

example, if <code class="docutils literal notranslate">obj1</code> is an instance of your data type and the Python script

contains <code class="docutils literal notranslate">obj1('hello')</code>, the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_call" title="PyTypeObject.tp_call"><code class="xref c c-member docutils literal notranslate">tp_call</code></a> handler is invoked.

This function takes three arguments:

<li>self is the instance of the data type which is the subject of the call.

If the call is <code class="docutils literal notranslate">obj1('hello')</code>, then self is <code class="docutils literal notranslate">obj1</code>.</li>

<li>args is a tuple containing the arguments to the call. You can use

<a class="reference internal" href="../c-api/arg.html#c.PyArg_ParseTuple" title="PyArg_ParseTuple"><code class="xref c c-func docutils literal notranslate">PyArg_ParseTuple()</code></a> to extract the arguments.</li>

<li>kwds is a dictionary of keyword arguments that were passed. If this is

non-<code class="docutils literal notranslate">NULL</code> and you support keyword arguments, use

<a class="reference internal" href="../c-api/arg.html#c.PyArg_ParseTupleAndKeywords" title="PyArg_ParseTupleAndKeywords"><code class="xref c c-func docutils literal notranslate">PyArg_ParseTupleAndKeywords()</code></a> to extract the arguments. If you

do not want to support keyword arguments and this is non-<code class="docutils literal notranslate">NULL</code>, raise a

<a class="reference internal" href="../library/exceptions.html#TypeError" title="TypeError"><code class="xref py py-exc docutils literal notranslate">TypeError</code></a> with a message saying that keyword arguments are not supported.</li>

</ol>

Here is a toy <code class="docutils literal notranslate">tp_call</code> implementation:

newdatatype_call(PyObject *op, PyObject *args, PyObject *kwds)

{

PyObject *result;

if (!PyArg_ParseTuple(args, "sss:call", &arg1, &arg2, &arg3)) {

return NULL;

}

result = PyUnicode_FromFormat(

"Returning -- value: [%d] arg1: [%s] arg2: [%s] arg3: [%s]\n",

arg1, arg2, arg3);

return result;

}

</pre></div>

</div>

<div class="highlight-c notranslate"><div class="highlight"><pre>/* Iterators */

getiterfunc tp_iter;

iternextfunc tp_iternext;

</pre></div>

</div>

These functions provide support for the iterator protocol. Both handlers

take exactly one parameter, the instance for which they are being called,

and return a new reference. In the case of an error, they should set an

exception and return <code class="docutils literal notranslate">NULL</code>. <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_iter" title="PyTypeObject.tp_iter"><code class="xref c c-member docutils literal notranslate">tp_iter</code></a> corresponds

to the Python <a class="reference internal" href="../reference/datamodel.html#object.__iter__" title="object.__iter__"><code class="xref py py-meth docutils literal notranslate">__iter__()</code></a> method, while <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_iternext" title="PyTypeObject.tp_iternext"><code class="xref c c-member docutils literal notranslate">tp_iternext</code></a>

corresponds to the Python <a class="reference internal" href="../library/stdtypes.html#iterator.__next__" title="iterator.__next__"><code class="xref py py-meth docutils literal notranslate">__next__()</code></a> method.

Any <a class="reference internal" href="../glossary.html#term-iterable">iterable</a> object must implement the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_iter" title="PyTypeObject.tp_iter"><code class="xref c c-member docutils literal notranslate">tp_iter</code></a>

handler, which must return an <a class="reference internal" href="../glossary.html#term-iterator">iterator</a> object. Here the same guidelines

apply as for Python classes:

<li>For collections (such as lists and tuples) which can support multiple

independent iterators, a new iterator should be created and returned by

each call to <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_iter" title="PyTypeObject.tp_iter"><code class="xref c c-member docutils literal notranslate">tp_iter</code></a>.</li>

<li>Objects which can only be iterated over once (usually due to side effects of

iteration, such as file objects) can implement <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_iter" title="PyTypeObject.tp_iter"><code class="xref c c-member docutils literal notranslate">tp_iter</code></a>

by returning a new reference to themselves -- and should also therefore

implement the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_iternext" title="PyTypeObject.tp_iternext"><code class="xref c c-member docutils literal notranslate">tp_iternext</code></a> handler.</li>

</ul>

Any <a class="reference internal" href="../glossary.html#term-iterator">iterator</a> object should implement both <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_iter" title="PyTypeObject.tp_iter"><code class="xref c c-member docutils literal notranslate">tp_iter</code></a>

and <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_iternext" title="PyTypeObject.tp_iternext"><code class="xref c c-member docutils literal notranslate">tp_iternext</code></a>. An iterator's

<code class="xref c c-member docutils literal notranslate">tp_iter</code> handler should return a new reference

to the iterator. Its <code class="xref c c-member docutils literal notranslate">tp_iternext</code> handler should

return a new reference to the next object in the iteration, if there is one.

If the iteration has reached the end, <code class="xref c c-member docutils literal notranslate">tp_iternext</code>

may return <code class="docutils literal notranslate">NULL</code> without setting an exception, or it may set

<a class="reference internal" href="../library/exceptions.html#StopIteration" title="StopIteration"><code class="xref py py-exc docutils literal notranslate">StopIteration</code></a> in addition to returning <code class="docutils literal notranslate">NULL</code>; avoiding

the exception can yield slightly better performance. If an actual error

occurs, <code class="xref c c-member docutils literal notranslate">tp_iternext</code> should always set an exception

and return <code class="docutils literal notranslate">NULL</code>.

</section>

<h2>3.6. Weak Reference Support<a class="headerlink" href="#weak-reference-support" title="Link to this heading">¶</a></h2>

One of the goals of Python's weak reference implementation is to allow any type

to participate in the weak reference mechanism without incurring the overhead on

performance-critical objects (such as numbers).

همچنین ملاحظه نمائید

Documentation for the <a class="reference internal" href="../library/weakref.html#module-weakref" title="weakref: Support for weak references and weak dictionaries."><code class="xref py py-mod docutils literal notranslate">weakref</code></a> module.

</div>

For an object to be weakly referenceable, the extension type must set the

<code class="docutils literal notranslate">Py_TPFLAGS_MANAGED_WEAKREF</code> bit of the <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_flags" title="PyTypeObject.tp_flags"><code class="xref c c-member docutils literal notranslate">tp_flags</code></a>

field. The legacy <a class="reference internal" href="../c-api/typeobj.html#c.PyTypeObject.tp_weaklistoffset" title="PyTypeObject.tp_weaklistoffset"><code class="xref c c-member docutils literal notranslate">tp_weaklistoffset</code></a> field should

be left as zero.

Concretely, here is how the statically declared type object would look:

<div class="highlight-c notranslate"><div class="highlight"><pre>static PyTypeObject TrivialType = {

PyVarObject_HEAD_INIT(NULL, 0)

/* ... other members omitted for brevity ... */

.tp_flags = Py_TPFLAGS_MANAGED_WEAKREF | ...,

};

</pre></div>

</div>

The only further addition is that <code class="docutils literal notranslate">tp_dealloc</code> needs to clear any weak

references (by calling <a class="reference internal" href="../c-api/weakref.html#c.PyObject_ClearWeakRefs" title="PyObject_ClearWeakRefs"><code class="xref c c-func docutils literal notranslate">PyObject_ClearWeakRefs()</code></a>):

<div class="highlight-c notranslate"><div class="highlight"><pre>static void

Trivial_dealloc(PyObject *op)

{

/* Clear weakrefs first before calling any destructors */

PyObject_ClearWeakRefs(op);

/* ... remainder of destruction code omitted for brevity ... */

Py_TYPE(op)->tp_free(op);

}

</pre></div>

</div>

</section>

<h2>3.7. More Suggestions<a class="headerlink" href="#more-suggestions" title="Link to this heading">¶</a></h2>

In order to learn how to implement any specific method for your new data type,

get the <a class="reference internal" href="../glossary.html#term-CPython">CPython</a> source code. Go to the <code class="file docutils literal notranslate">Objects</code> directory,

then search the C source files for <code class="docutils literal notranslate">tp_</code> plus the function you want

(for example, <code class="docutils literal notranslate">tp_richcompare</code>). You will find examples of the function

you want to implement.

When you need to verify that an object is a concrete instance of the type you

are implementing, use the <a class="reference internal" href="../c-api/object.html#c.PyObject_TypeCheck" title="PyObject_TypeCheck"><code class="xref c c-func docutils literal notranslate">PyObject_TypeCheck()</code></a> function. A sample of

its use might be something like the following:

<div class="highlight-c notranslate"><div class="highlight"><pre>if (!PyObject_TypeCheck(some_object, &MyType)) {

PyErr_SetString(PyExc_TypeError, "arg #1 not a mything");

return NULL;

}

</pre></div>

</div>

همچنین ملاحظه نمائید

<dt>Download CPython source releases.</dt><dd><a class="reference external" href="https://www.python.org/downloads/source/">https://www.python.org/downloads/source/</a>

</dd>

<dt>The CPython project on GitHub, where the CPython source code is developed.</dt><dd><a class="reference external" href="https://github.com/python/cpython">https://github.com/python/cpython</a>

</dd>

</dl>

</div>

</section>

</div>

<div>

<h3><a href="../contents.html">فهرست عناوین</a></h3>

<ul>

<li><a class="reference internal" href="#">3. Defining Extension Types: Assorted Topics</a><ul>

<li><a class="reference internal" href="#finalization-and-de-allocation">3.1. Finalization and De-allocation</a></li>

<li><a class="reference internal" href="#object-presentation">3.2. Object Presentation</a></li>

<li><a class="reference internal" href="#attribute-management">3.3. Attribute Management</a><ul>

<li><a class="reference internal" href="#generic-attribute-management">3.3.1. Generic Attribute Management</a></li>

<li><a class="reference internal" href="#type-specific-attribute-management">3.3.2. Type-specific Attribute Management</a></li>

</ul>

</li>

<li><a class="reference internal" href="#object-comparison">3.4. Object Comparison</a></li>

<li><a class="reference internal" href="#abstract-protocol-support">3.5. Abstract Protocol Support</a></li>

<li><a class="reference internal" href="#weak-reference-support">3.6. Weak Reference Support</a></li>

<li><a class="reference internal" href="#more-suggestions">3.7. More Suggestions</a></li>

</ul>

</li>

</ul>

</div>

<div>

<h4>موضوع قبلی</h4>

<a href="newtypes_tutorial.html"

title="فصل قبلی">2. Defining Extension Types: Tutorial</a>

</div>

<div>

<h4>موضوع بعدی</h4>

<a href="building.html"

title="فصل بعدی">4. Building C and C++ Extensions</a>

</div>

document.addEventListener('DOMContentLoaded', () => {

const title = document.querySelector('meta[property="og:title"]').content;

const elements = document.querySelectorAll('.improvepage');

const pageurl = window.location.href.split('?')[0];

elements.forEach(element => {

const url = new URL(element.href.split('?')[0].replace("-nojs", ""));

url.searchParams.set('pagetitle', title);

url.searchParams.set('pageurl', pageurl);

url.searchParams.set('pagesource', "extending/newtypes.rst");

element.href = url.toString();

});

</script>

<li><a href="../bugs.html">گزارش یک اشکال</a></li>

<li><a class="improvepage" href="../improve-page-nojs.html">بهبود این صفحه</a></li>

<li>

<a href="https://github.com/python/cpython/blob/main/Doc/extending/newtypes.rst?plain=1"

rel="nofollow">نمایش منبع

</a>

</li>

<li>

<a href="https://github.com/python/python-docs-fa/blob/3.14/extending/newtypes.po?plain=1"

rel="nofollow">نمایش منبع ترجمه</a>

</li>

</ul>

</div>

«

</div>

</div>

<h3>ناوبری</h3>

<ul>

<a href="../genindex.html" title="فهرست کلی"

>فهرست</a></li>

<a href="../py-modindex.html" title="نمایه ی ماژول های پایتون"

>ماژول ها</a> |</li>

<a href="building.html" title="4. Building C and C++ Extensions"

>بعدی</a> |</li>

<a href="newtypes_tutorial.html" title="2. Defining Extension Types: Tutorial"

>قبلی</a> |</li>

<li><a href="https://www.python.org/">Python</a> »</li>

</li>

<li>

</li>

<a href="../index.html">3.14.6 Documentation</a> »

</li>

<li class="nav-item nav-item-1"><a href="index.html" >Extending and Embedding the Python Interpreter</a> »</li>

<li class="nav-item nav-item-this"><a href="">3. Defining Extension Types: Assorted Topics</a></li>

</form>

</div>

</li>

Theme

<option value="light">Light</option>

</select>

</label> |</li>

</ul>

</div>

This page is licensed under the Python Software Foundation License Version 2.

Examples, recipes, and other code in the documentation are additionally licensed under the Zero Clause BSD License.

See <a href="/license.html">History and License</a> for more information.

The Python Software Foundation is a non-profit corporation.

<a href="https://www.python.org/psf/donations/">Please donate.</a>

View remainder of file in raw view

Navigation Menu

Uh oh!

Uh oh!

FilesExpand file tree

newtypes.html

Latest commit

History

newtypes.html

File metadata and controls