[docs] [issue9307] Py_TPFLAGS_LONG_SUBCLASS is not documented

Alexander Belopolsky report at bugs.python.org
Mon Jul 19 20:07:59 CEST 2010

Alexander Belopolsky <belopolsky at users.sourceforge.net> added the comment:

Here are other similar flags that are not documented:

/* These flags are used to determine if a type is a subclass. */
#define Py_TPFLAGS_INT_SUBCLASS         (1L<<23)
#define Py_TPFLAGS_LONG_SUBCLASS        (1L<<24)
#define Py_TPFLAGS_LIST_SUBCLASS        (1L<<25)
#define Py_TPFLAGS_TUPLE_SUBCLASS       (1L<<26)
#define Py_TPFLAGS_BYTES_SUBCLASS       (1L<<27)
#define Py_TPFLAGS_UNICODE_SUBCLASS     (1L<<28)
#define Py_TPFLAGS_DICT_SUBCLASS        (1L<<29)
#define Py_TPFLAGS_BASE_EXC_SUBCLASS    (1L<<30)
#define Py_TPFLAGS_TYPE_SUBCLASS        (1L<<31)

On a similar note, TPFLAGS_IS_ABSTRACT is exposed in the inspect module, but is not documented in either inspect module documentation or C API documentation.

I believe that as long as these flags are available from the type objects as __flags__, all valid bits should be exposed in inspect module and properly documented.

components: +Library (Lib)
versions: +Python 2.7, Python 3.2

Python tracker <report at bugs.python.org>

More information about the docs mailing list