mirror of
https://github.com/python/cpython
synced 2026-10-16 20:31:39 +03:00
These slots are marked "should be treated as read-only" in the table at the start of the document. That doesn't say anything about setting them in the static struct. `tp_bases` docs did say that it should be ``NULL`` (TIL!). If you ignore that, seemingly nothing bad happens. However, some slots may not be inherited, depending on which sub-slot structs are present. (FWIW, NumPy sets tp_bases and is affected by the quirk -- though to be fair, its DUAL_INHERIT code probably predates tp_bases docs, and also the result happens to be benign.) This patch makes things explicit. It also makes the summary table legend easier to scan. Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| abstract.rst | ||
| allocation.rst | ||
| apiabiversion.rst | ||
| arg.rst | ||
| bool.rst | ||
| buffer.rst | ||
| bytearray.rst | ||
| bytes.rst | ||
| call.rst | ||
| capsule.rst | ||
| cell.rst | ||
| code.rst | ||
| codec.rst | ||
| complex.rst | ||
| concrete.rst | ||
| contextvars.rst | ||
| conversion.rst | ||
| coro.rst | ||
| datetime.rst | ||
| descriptor.rst | ||
| dict.rst | ||
| exceptions.rst | ||
| file.rst | ||
| float.rst | ||
| frame.rst | ||
| function.rst | ||
| gcsupport.rst | ||
| gen.rst | ||
| import.rst | ||
| index.rst | ||
| init.rst | ||
| init_config.rst | ||
| intro.rst | ||
| iter.rst | ||
| iterator.rst | ||
| list.rst | ||
| long.rst | ||
| mapping.rst | ||
| marshal.rst | ||
| memory.rst | ||
| memoryview.rst | ||
| method.rst | ||
| module.rst | ||
| none.rst | ||
| number.rst | ||
| objbuffer.rst | ||
| object.rst | ||
| objimpl.rst | ||
| refcounting.rst | ||
| reflection.rst | ||
| sequence.rst | ||
| set.rst | ||
| slice.rst | ||
| stable.rst | ||
| structures.rst | ||
| sys.rst | ||
| tuple.rst | ||
| type.rst | ||
| typehints.rst | ||
| typeobj.rst | ||
| unicode.rst | ||
| utilities.rst | ||
| veryhigh.rst | ||
| weakref.rst | ||