From 4dc5f7897d28ac236a50fbdbb3a534095ca962ab Mon Sep 17 00:00:00 2001 From: Bruno Oliveira Date: Thu, 31 May 2018 12:43:48 -0300 Subject: [PATCH] Fix typo in marks.rst --- doc/en/mark.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/en/mark.rst b/doc/en/mark.rst index 7f39fd728..19c11c58a 100644 --- a/doc/en/mark.rst +++ b/doc/en/mark.rst @@ -44,7 +44,7 @@ pytest's marker implementation traditionally worked by simply updating the ``__d This state of things made it technically next to impossible to use data from markers correctly without having a deep understanding of the internals, leading to subtle and hard to understand bugs in more advanced usages. Depending on how a marker got declared/changed one would get either a ``MarkerInfo`` which might contain markers from sibling classes, -``MarkDecorators`` when marks came from parameterization or from a ``node.add_marker`` call, discarding prior marks. Also ``MarkerInfo`` acts like a single mark, when it in fact repressents a merged view on multiple marks with the same name. +``MarkDecorators`` when marks came from parameterization or from a ``node.add_marker`` call, discarding prior marks. Also ``MarkerInfo`` acts like a single mark, when it in fact represents a merged view on multiple marks with the same name. On top of that markers where not accessible the same way for modules, classes, and functions/methods, in fact, markers where only accessible in functions, even if they where declared on classes/modules.