From c800d58f427770d70101a929f30ffb02f958c985 Mon Sep 17 00:00:00 2001 From: Hynek Schlawack Date: Thu, 23 Nov 2023 08:29:37 +0100 Subject: [PATCH] docs: typo --- docs/why.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/why.md b/docs/why.md index 34be3029a..eeba9db58 100644 --- a/docs/why.md +++ b/docs/why.md @@ -109,7 +109,7 @@ Other often surprising behaviors include: you end up with a class that has *two* `Point`s in its {attr}`__mro__ `: `[, , , ]`. That's not only confusing, it also has very practical consequences: - for example if you create documentation that includes class hierarchies like *[*Sphinx*'s autodoc](https://www.sphinx-doc.org/en/stable/usage/extensions/autodoc.html) with `show-inheritance`. + for example if you create documentation that includes class hierarchies like [*Sphinx*'s autodoc](https://www.sphinx-doc.org/en/stable/usage/extensions/autodoc.html) with `show-inheritance`. Again: common problem, hacky solution with confusing fallout. All these things make `namedtuple`s a particularly poor choice for public APIs because all your objects are irrevocably tainted.