Merge changelog marks refactoring changelog entries as discussed in review
This commit is contained in:
parent
bb626fe8a7
commit
5be85a1f55
|
@ -1,3 +1,4 @@
|
|||
Revamp the internals of the ``pytest.mark`` implementation with correct per node handling and introduce a new ``Node.iter_markers``
|
||||
API for mark iteration over nodes which fixes a number of long standing bugs caused by the old approach. More details can be
|
||||
found in `the marks documentation <https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration>`_.
|
||||
Revamp the internals of the ``pytest.mark`` implementation with correct per node handling which fixes a number of
|
||||
long standing bugs caused by the old design. This introduces new ``Node.iter_markers(name)`` and ``Node.get_closest_mark(name)`` APIs.
|
||||
Users are **strongly encouraged** to read `reasons for the revamp in the docs <https://docs.pytest.org/en/latest/mark.html#marker-revamp-and-iteration>`_,
|
||||
or jump over to details about `updating existing code to use the new APIs <https://docs.pytest.org/en/latest/mark.html#updating-code>`_.
|
||||
|
|
|
@ -1 +0,0 @@
|
|||
Introduce ``Node.get_closest_marker(name, default=None)`` to support simple marker usage scenarios.
|
|
@ -1 +0,0 @@
|
|||
Introduce optional name-based filtering for ``Node.iter_markers``.
|
Loading…
Reference in New Issue