From 0d2fd528be22d0a500972329b0e26fcc87530d44 Mon Sep 17 00:00:00 2001 From: Robsdedude Date: Fri, 16 Aug 2024 15:46:24 +0200 Subject: [PATCH] Docs: fix reference --- docs/source/metaclasses.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/metaclasses.rst b/docs/source/metaclasses.rst index cb73c1d13e61..fe82399a3995 100644 --- a/docs/source/metaclasses.rst +++ b/docs/source/metaclasses.rst @@ -90,7 +90,7 @@ so it's better not to combine metaclasses and class hierarchies: For some builtin types, mypy assumes that their metaclass is :py:class:`abc.ABCMeta` even if it's :py:class:`type`. In those cases, you can either -* use :py:class:`abc.ABCMetaclass` instead of :py:class:`type` as the +* use :py:class:`abc.ABCMeta` instead of :py:class:`type` as the superclass of your metaclass if that works in your use case, * mute the error with ``# type: ignore[metaclass]``, or * compute the metaclass' superclass dynamically, which mypy doesn't understand