Fix typos in docs

This commit is contained in:
Bruno Oliveira 2018-04-05 14:45:30 -03:00 committed by GitHub
parent 3582e1f6be
commit e534cc81a3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 6 deletions

View File

@ -42,14 +42,11 @@ 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 siebling classes,
MarkDecroators when marks came from parameterization or from a `add_marker` call, while 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.
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.
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
in fact, markers where only accessible in functions, even if they where declared on classes/modules.
A new API to access markers has been introduced in pytest 3.6 in order to solve the problems with the initial design, providing :func:`_pytest.nodes.Node.iter_markers` method to iterate over markers in a consistent manner and reworking the internals, which solved great deal of problems with the initial design.