{"action":"created","issue":{"url":"https://api.github.com/repos/inhumantsar/python-ansible-vault-rekey/issues/251","repository_url":"https://api.github.com/repos/inhumantsar/python-ansible-vault-rekey","labels_url":"https://api.github.com/repos/inhumantsar/python-ansible-vault-rekey/issues/251/labels{/name}","comments_url":"https://api.github.com/repos/inhumantsar/python-ansible-vault-rekey/issues/251/comments","events_url":"https://api.github.com/repos/inhumantsar/python-ansible-vault-rekey/issues/251/events","html_url":"https://github.com/inhumantsar/python-ansible-vault-rekey/pull/251","id":529548580,"node_id":"MDExOlB1bGxSZXF1ZXN0MzQ2NDA1NzA3","number":251,"title":"Update pytest to 5.3.1","user":{"login":"pyup-bot","id":16239342,"node_id":"MDQ6VXNlcjE2MjM5MzQy","avatar_url":"https://avatars0.githubusercontent.com/u/16239342?v=4","gravatar_id":"","url":"https://api.github.com/users/pyup-bot","html_url":"https://github.com/pyup-bot","followers_url":"https://api.github.com/users/pyup-bot/followers","following_url":"https://api.github.com/users/pyup-bot/following{/other_user}","gists_url":"https://api.github.com/users/pyup-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/pyup-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyup-bot/subscriptions","organizations_url":"https://api.github.com/users/pyup-bot/orgs","repos_url":"https://api.github.com/users/pyup-bot/repos","events_url":"https://api.github.com/users/pyup-bot/events{/privacy}","received_events_url":"https://api.github.com/users/pyup-bot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2019-11-27T20:01:17Z","updated_at":"2019-12-15T02:11:45Z","closed_at":null,"author_association":"CONTRIBUTOR","pull_request":{"url":"https://api.github.com/repos/inhumantsar/python-ansible-vault-rekey/pulls/251","html_url":"https://github.com/inhumantsar/python-ansible-vault-rekey/pull/251","diff_url":"https://github.com/inhumantsar/python-ansible-vault-rekey/pull/251.diff","patch_url":"https://github.com/inhumantsar/python-ansible-vault-rekey/pull/251.patch"},"body":"\nThis PR updates [pytest](https://pypi.org/project/pytest) from **3.6.0** to **5.3.1**.\n\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 5.3.1\n   ```\n   =========================\n\nImprovements\n------------\n\n- `6231 &lt;https://github.com/pytest-dev/pytest/issues/6231&gt;`_: Improve check for misspelling of ``pytest.mark.parametrize``.\n\n\n- `6257 &lt;https://github.com/pytest-dev/pytest/issues/6257&gt;`_: Handle `exit.Exception` raised in `notify_exception` (via `pytest_internalerror`), e.g. when quitting pdb from post mortem.\n\n\n\nBug Fixes\n---------\n\n- `5914 &lt;https://github.com/pytest-dev/pytest/issues/5914&gt;`_: pytester: fix ``no_fnmatch_line`` when used after positive matching.\n\n\n- `6082 &lt;https://github.com/pytest-dev/pytest/issues/6082&gt;`_: Fix line detection for doctest samples inside ``property`` docstrings, as a workaround to `bpo-17446 &lt;https://bugs.python.org/issue17446&gt;`__.\n\n\n- `6254 &lt;https://github.com/pytest-dev/pytest/issues/6254&gt;`_: Fix compatibility with pytest-parallel (regression in pytest 5.3.0).\n\n\n- `6255 &lt;https://github.com/pytest-dev/pytest/issues/6255&gt;`_: Clear the ``sys.last_traceback``, ``sys.last_type`` and ``sys.last_value``\n  attributes by deleting them instead of setting them to ``None``. This better\n  matches the behaviour of the Python standard library.\n   ```\n   \n  \n  \n   ### 5.3.0\n   ```\n   =========================\n\nDeprecations\n------------\n\n- `6179 &lt;https://github.com/pytest-dev/pytest/issues/6179&gt;`_: The default value of ``junit_family`` option will change to ``xunit2`` in pytest 6.0, given\n  that this is the version supported by default in modern tools that manipulate this type of file.\n\n  In order to smooth the transition, pytest will issue a warning in case the ``--junitxml`` option\n  is given in the command line but ``junit_family`` is not explicitly configured in ``pytest.ini``.\n\n  For more information, `see the docs &lt;https://docs.pytest.org/en/latest/deprecations.htmljunit-family-default-value-change-to-xunit2&gt;`__.\n\n\n\nFeatures\n--------\n\n- `4488 &lt;https://github.com/pytest-dev/pytest/issues/4488&gt;`_: The pytest team has created the `pytest-reportlog &lt;https://github.com/pytest-dev/pytest-reportlog&gt;`__\n  plugin, which provides a new ``--report-log=FILE`` option that writes *report logs* into a file as the test session executes.\n\n  Each line of the report log contains a self contained JSON object corresponding to a testing event,\n  such as a collection or a test result report. The file is guaranteed to be flushed after writing\n  each line, so systems can read and process events in real-time.\n\n  The plugin is meant to replace the ``--resultlog`` option, which is deprecated and meant to be removed\n  in a future release. If you use ``--resultlog``, please try out ``pytest-reportlog`` and\n  provide feedback.\n\n\n- `4730 &lt;https://github.com/pytest-dev/pytest/issues/4730&gt;`_: When ``sys.pycache_prefix`` (Python 3.8+) is set, it will be used by pytest to cache test files changed by the assertion rewriting mechanism.\n\n  This makes it easier to benefit of cached ``.pyc`` files even on file systems without permissions.\n\n\n- `5515 &lt;https://github.com/pytest-dev/pytest/issues/5515&gt;`_: Allow selective auto-indentation of multiline log messages.\n\n  Adds command line option ``--log-auto-indent``, config option\n  ``log_auto_indent`` and support for per-entry configuration of\n  indentation behavior on calls to ``logging.log()``.\n\n  Alters the default for auto-indention from ``on`` to ``off``. This\n  restores the older behavior that existed prior to v4.6.0. This\n  reversion to earlier behavior was done because it is better to\n  activate new features that may lead to broken tests explicitly\n  rather than implicitly.\n\n\n- `5914 &lt;https://github.com/pytest-dev/pytest/issues/5914&gt;`_: `testdir &lt;https://docs.pytest.org/en/latest/reference.htmltestdir&gt;`__ learned two new functions, `no_fnmatch_line &lt;https://docs.pytest.org/en/latest/reference.html_pytest.pytester.LineMatcher.no_fnmatch_line&gt;`_ and\n  `no_re_match_line &lt;https://docs.pytest.org/en/latest/reference.html_pytest.pytester.LineMatcher.no_re_match_line&gt;`_.\n\n  The functions are used to ensure the captured text *does not* match the given\n  pattern.\n\n  The previous idiom was to use ``re.match``:\n\n  .. code-block:: python\n\n      result = testdir.runpytest()\n      assert re.match(pat, result.stdout.str()) is None\n\n  Or the ``in`` operator:\n\n  .. code-block:: python\n\n      result = testdir.runpytest()\n      assert text in result.stdout.str()\n\n  But the new functions produce best output on failure.\n\n\n- `6057 &lt;https://github.com/pytest-dev/pytest/issues/6057&gt;`_: Added tolerances to complex values when printing ``pytest.approx``.\n\n  For example, ``repr(pytest.approx(3+4j))`` returns ``(3+4j) ± 5e-06 ∠ ±180°``. This is polar notation indicating a circle around the expected value, with a radius of 5e-06. For ``approx`` comparisons to return ``True``, the actual value should fall within this circle.\n\n\n- `6061 &lt;https://github.com/pytest-dev/pytest/issues/6061&gt;`_: Added the pluginmanager as an argument to ``pytest_addoption``\n  so that hooks can be invoked when setting up command line options. This is\n  useful for having one plugin communicate things to another plugin,\n  such as default values or which set of command line options to add.\n\n\n\nImprovements\n------------\n\n- `5061 &lt;https://github.com/pytest-dev/pytest/issues/5061&gt;`_: Use multiple colors with terminal summary statistics.\n\n\n- `5630 &lt;https://github.com/pytest-dev/pytest/issues/5630&gt;`_: Quitting from debuggers is now properly handled in ``doctest`` items.\n\n\n- `5924 &lt;https://github.com/pytest-dev/pytest/issues/5924&gt;`_: Improved verbose diff output with sequences.\n\n  Before:\n\n  ::\n\n      E   AssertionError: assert [&#39;version&#39;, &#39;...version_info&#39;] == [&#39;version&#39;, &#39;...version&#39;, ...]\n      E     Right contains 3 more items, first extra item: &#39; &#39;\n      E     Full diff:\n      E     - [&#39;version&#39;, &#39;version_info&#39;, &#39;sys.version&#39;, &#39;sys.version_info&#39;]\n      E     + [&#39;version&#39;,\n      E     +  &#39;version_info&#39;,\n      E     +  &#39;sys.version&#39;,\n      E     +  &#39;sys.version_info&#39;,\n      E     +  &#39; &#39;,\n      E     +  &#39;sys.version&#39;,\n      E     +  &#39;sys.version_info&#39;]\n\n  After:\n\n  ::\n\n      E   AssertionError: assert [&#39;version&#39;, &#39;...version_info&#39;] == [&#39;version&#39;, &#39;...version&#39;, ...]\n      E     Right contains 3 more items, first extra item: &#39; &#39;\n      E     Full diff:\n      E       [\n      E        &#39;version&#39;,\n      E        &#39;version_info&#39;,\n      E        &#39;sys.version&#39;,\n      E        &#39;sys.version_info&#39;,\n      E     +  &#39; &#39;,\n      E     +  &#39;sys.version&#39;,\n      E     +  &#39;sys.version_info&#39;,\n      E       ]\n\n\n- `5934 &lt;https://github.com/pytest-dev/pytest/issues/5934&gt;`_: ``repr`` of ``ExceptionInfo`` objects has been improved to honor the ``__repr__`` method of the underlying exception.\n\n- `5936 &lt;https://github.com/pytest-dev/pytest/issues/5936&gt;`_: Display untruncated assertion message with ``-vv``.\n\n\n- `5990 &lt;https://github.com/pytest-dev/pytest/issues/5990&gt;`_: Fixed plurality mismatch in test summary (e.g. display &quot;1 error&quot; instead of &quot;1 errors&quot;).\n\n\n- `6008 &lt;https://github.com/pytest-dev/pytest/issues/6008&gt;`_: ``Config.InvocationParams.args`` is now always a ``tuple`` to better convey that it should be\n  immutable and avoid accidental modifications.\n\n\n- `6023 &lt;https://github.com/pytest-dev/pytest/issues/6023&gt;`_: ``pytest.main`` returns a ``pytest.ExitCode`` instance now, except for when custom exit codes are used (where it returns ``int`` then still).\n\n\n- `6026 &lt;https://github.com/pytest-dev/pytest/issues/6026&gt;`_: Align prefixes in output of pytester&#39;s ``LineMatcher``.\n\n\n- `6059 &lt;https://github.com/pytest-dev/pytest/issues/6059&gt;`_: Collection errors are reported as errors (and not failures like before) in the terminal&#39;s short test summary.\n\n\n- `6069 &lt;https://github.com/pytest-dev/pytest/issues/6069&gt;`_: ``pytester.spawn`` does not skip/xfail tests on FreeBSD anymore unconditionally.\n\n\n- `6097 &lt;https://github.com/pytest-dev/pytest/issues/6097&gt;`_: The &quot;[...%]&quot; indicator in the test summary is now colored according to the final (new) multi-colored line&#39;s main color.\n\n\n- `6116 &lt;https://github.com/pytest-dev/pytest/issues/6116&gt;`_: Added ``--co`` as a synonym to ``--collect-only``.\n\n\n- `6148 &lt;https://github.com/pytest-dev/pytest/issues/6148&gt;`_: ``atomicwrites`` is now only used on Windows, fixing a performance regression with assertion rewriting on Unix.\n\n\n- `6152 &lt;https://github.com/pytest-dev/pytest/issues/6152&gt;`_: Now parametrization will use the ``__name__`` attribute of any object for the id, if present. Previously it would only use ``__name__`` for functions and classes.\n\n\n- `6176 &lt;https://github.com/pytest-dev/pytest/issues/6176&gt;`_: Improved failure reporting with pytester&#39;s ``Hookrecorder.assertoutcome``.\n\n\n- `6181 &lt;https://github.com/pytest-dev/pytest/issues/6181&gt;`_: The reason for a stopped session, e.g. with ``--maxfail`` / ``-x``, now gets reported in the test summary.\n\n\n- `6206 &lt;https://github.com/pytest-dev/pytest/issues/6206&gt;`_: Improved ``cache.set`` robustness and performance.\n\n\n\nBug Fixes\n---------\n\n- `2049 &lt;https://github.com/pytest-dev/pytest/issues/2049&gt;`_: Fixed ``--setup-plan`` showing inaccurate information about fixture lifetimes.\n\n\n- `2548 &lt;https://github.com/pytest-dev/pytest/issues/2548&gt;`_: Fixed line offset mismatch of skipped tests in terminal summary.\n\n\n- `6039 &lt;https://github.com/pytest-dev/pytest/issues/6039&gt;`_: The ``PytestDoctestRunner`` is now properly invalidated when unconfiguring the doctest plugin.\n\n  This is important when used with ``pytester``&#39;s ``runpytest_inprocess``.\n\n\n- `6047 &lt;https://github.com/pytest-dev/pytest/issues/6047&gt;`_: BaseExceptions are now handled in ``saferepr``, which includes ``pytest.fail.Exception`` etc.\n\n\n- `6074 &lt;https://github.com/pytest-dev/pytest/issues/6074&gt;`_: pytester: fixed order of arguments in ``rm_rf`` warning when cleaning up temporary directories, and do not emit warnings for errors with ``os.open``.\n\n\n- `6189 &lt;https://github.com/pytest-dev/pytest/issues/6189&gt;`_: Fixed result of ``getmodpath`` method.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4901 &lt;https://github.com/pytest-dev/pytest/issues/4901&gt;`_: ``RunResult`` from ``pytester`` now displays the mnemonic of the ``ret`` attribute when it is a\n  valid ``pytest.ExitCode`` value.\n   ```\n   \n  \n  \n   ### 5.2.4\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `6194 &lt;https://github.com/pytest-dev/pytest/issues/6194&gt;`_: Fix incorrect discovery of non-test ``__init__.py`` files.\n\n\n- `6197 &lt;https://github.com/pytest-dev/pytest/issues/6197&gt;`_: Revert &quot;The first test in a package (``__init__.py``) marked with ``pytest.mark.skip`` is now correctly skipped.&quot;.\n   ```\n   \n  \n  \n   ### 5.2.3\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5830 &lt;https://github.com/pytest-dev/pytest/issues/5830&gt;`_: The first test in a package (``__init__.py``) marked with ``pytest.mark.skip`` is now correctly skipped.\n\n\n- `6099 &lt;https://github.com/pytest-dev/pytest/issues/6099&gt;`_: Fix ``--trace`` when used with parametrized functions.\n\n\n- `6183 &lt;https://github.com/pytest-dev/pytest/issues/6183&gt;`_: Using ``request`` as a parameter name in ``pytest.mark.parametrize`` now produces a more\n  user-friendly error.\n   ```\n   \n  \n  \n   ### 5.2.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5206 &lt;https://github.com/pytest-dev/pytest/issues/5206&gt;`_: Fix ``--nf`` to not forget about known nodeids with partial test selection.\n\n\n- `5906 &lt;https://github.com/pytest-dev/pytest/issues/5906&gt;`_: Fix crash with ``KeyboardInterrupt`` during ``--setup-show``.\n\n\n- `5946 &lt;https://github.com/pytest-dev/pytest/issues/5946&gt;`_: Fixed issue when parametrizing fixtures with numpy arrays (and possibly other sequence-like types).\n\n\n- `6044 &lt;https://github.com/pytest-dev/pytest/issues/6044&gt;`_: Properly ignore ``FileNotFoundError`` exceptions when trying to remove old temporary directories,\n  for instance when multiple processes try to remove the same directory (common with ``pytest-xdist``\n  for example).\n   ```\n   \n  \n  \n   ### 5.2.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5902 &lt;https://github.com/pytest-dev/pytest/issues/5902&gt;`_: Fix warnings about deprecated ``cmp`` attribute in ``attrs&gt;=19.2``.\n   ```\n   \n  \n  \n   ### 5.2.0\n   ```\n   =========================\n\nDeprecations\n------------\n\n- `1682 &lt;https://github.com/pytest-dev/pytest/issues/1682&gt;`_: Passing arguments to pytest.fixture() as positional arguments is deprecated - pass them\n  as a keyword argument instead.\n\n\n\nFeatures\n--------\n\n- `1682 &lt;https://github.com/pytest-dev/pytest/issues/1682&gt;`_: The ``scope`` parameter of ``pytest.fixture`` can now be a callable that receives\n  the fixture name and the ``config`` object as keyword-only parameters.\n  See `the docs &lt;https://docs.pytest.org/en/latest/fixture.htmldynamic-scope&gt;`__ for more information.\n\n\n- `5764 &lt;https://github.com/pytest-dev/pytest/issues/5764&gt;`_: New behavior of the ``--pastebin`` option: failures to connect to the pastebin server are reported, without failing the pytest run\n\n\n\nBug Fixes\n---------\n\n- `5806 &lt;https://github.com/pytest-dev/pytest/issues/5806&gt;`_: Fix &quot;lexer&quot; being used when uploading to bpaste.net from ``--pastebin`` to &quot;text&quot;.\n\n\n- `5884 &lt;https://github.com/pytest-dev/pytest/issues/5884&gt;`_: Fix ``--setup-only`` and ``--setup-show`` for custom pytest items.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `5056 &lt;https://github.com/pytest-dev/pytest/issues/5056&gt;`_: The HelpFormatter uses ``py.io.get_terminal_width`` for better width detection.\n   ```\n   \n  \n  \n   ### 5.1.3\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5807 &lt;https://github.com/pytest-dev/pytest/issues/5807&gt;`_: Fix pypy3.6 (nightly) on windows.\n\n\n- `5811 &lt;https://github.com/pytest-dev/pytest/issues/5811&gt;`_: Handle ``--fulltrace`` correctly with ``pytest.raises``.\n\n\n- `5819 &lt;https://github.com/pytest-dev/pytest/issues/5819&gt;`_: Windows: Fix regression with conftest whose qualified name contains uppercase\n  characters (introduced by 5792).\n   ```\n   \n  \n  \n   ### 5.1.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `2270 &lt;https://github.com/pytest-dev/pytest/issues/2270&gt;`_: Fixed ``self`` reference in function-scoped fixtures defined plugin classes: previously ``self``\n  would be a reference to a *test* class, not the *plugin* class.\n\n\n- `570 &lt;https://github.com/pytest-dev/pytest/issues/570&gt;`_: Fixed long standing issue where fixture scope was not respected when indirect fixtures were used during\n  parametrization.\n\n\n- `5782 &lt;https://github.com/pytest-dev/pytest/issues/5782&gt;`_: Fix decoding error when printing an error response from ``--pastebin``.\n\n\n- `5786 &lt;https://github.com/pytest-dev/pytest/issues/5786&gt;`_: Chained exceptions in test and collection reports are now correctly serialized, allowing plugins like\n  ``pytest-xdist`` to display them properly.\n\n\n- `5792 &lt;https://github.com/pytest-dev/pytest/issues/5792&gt;`_: Windows: Fix error that occurs in certain circumstances when loading\n  ``conftest.py`` from a working directory that has casing other than the one stored\n  in the filesystem (e.g., ``c:\\test`` instead of ``C:\\test``).\n   ```\n   \n  \n  \n   ### 5.1.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5751 &lt;https://github.com/pytest-dev/pytest/issues/5751&gt;`_: Fixed ``TypeError`` when importing pytest on Python 3.5.0 and 3.5.1.\n   ```\n   \n  \n  \n   ### 5.1.0\n   ```\n   =========================\n\nRemovals\n--------\n\n- `5180 &lt;https://github.com/pytest-dev/pytest/issues/5180&gt;`_: As per our policy, the following features have been deprecated in the 4.X series and are now\n  removed:\n\n  * ``Request.getfuncargvalue``: use ``Request.getfixturevalue`` instead.\n\n  * ``pytest.raises`` and ``pytest.warns`` no longer support strings as the second argument.\n\n  * ``message`` parameter of ``pytest.raises``.\n\n  * ``pytest.raises``, ``pytest.warns`` and ``ParameterSet.param`` now use native keyword-only\n    syntax. This might change the exception message from previous versions, but they still raise\n    ``TypeError`` on unknown keyword arguments as before.\n\n  * ``pytest.config`` global variable.\n\n  * ``tmpdir_factory.ensuretemp`` method.\n\n  * ``pytest_logwarning`` hook.\n\n  * ``RemovedInPytest4Warning`` warning type.\n\n  * ``request`` is now a reserved name for fixtures.\n\n\n  For more information consult\n  `Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`__ in the docs.\n\n\n- `5565 &lt;https://github.com/pytest-dev/pytest/issues/5565&gt;`_: Removed unused support code for `unittest2 &lt;https://pypi.org/project/unittest2/&gt;`__.\n\n  The ``unittest2`` backport module is no longer\n  necessary since Python 3.3+, and the small amount of code in pytest to support it also doesn&#39;t seem\n  to be used: after removed, all tests still pass unchanged.\n\n  Although our policy is to introduce a deprecation period before removing any features or support\n  for third party libraries, because this code is apparently not used\n  at all (even if ``unittest2`` is used by a test suite executed by pytest), it was decided to\n  remove it in this release.\n\n  If you experience a regression because of this, please\n  `file an issue &lt;https://github.com/pytest-dev/pytest/issues/new&gt;`__.\n\n\n- `5615 &lt;https://github.com/pytest-dev/pytest/issues/5615&gt;`_: ``pytest.fail``, ``pytest.xfail`` and ``pytest.skip`` no longer support bytes for the message argument.\n\n  This was supported for Python 2 where it was tempting to use ``&quot;message&quot;``\n  instead of ``u&quot;message&quot;``.\n\n  Python 3 code is unlikely to pass ``bytes`` to these functions. If you do,\n  please decode it to an ``str`` beforehand.\n\n\n\nFeatures\n--------\n\n- `5564 &lt;https://github.com/pytest-dev/pytest/issues/5564&gt;`_: New ``Config.invocation_args`` attribute containing the unchanged arguments passed to ``pytest.main()``.\n\n\n- `5576 &lt;https://github.com/pytest-dev/pytest/issues/5576&gt;`_: New `NUMBER &lt;https://docs.pytest.org/en/latest/doctest.htmlusing-doctest-options&gt;`__\n  option for doctests to ignore irrelevant differences in floating-point numbers.\n  Inspired by Sébastien Boisgérault&#39;s `numtest &lt;https://github.com/boisgera/numtest&gt;`__\n  extension for doctest.\n\n\n\nImprovements\n------------\n\n- `5471 &lt;https://github.com/pytest-dev/pytest/issues/5471&gt;`_: JUnit XML now includes a timestamp and hostname in the testsuite tag.\n\n\n- `5707 &lt;https://github.com/pytest-dev/pytest/issues/5707&gt;`_: Time taken to run the test suite now includes a human-readable representation when it takes over\n  60 seconds, for example::\n\n      ===== 2 failed in 102.70s (0:01:42) =====\n\n\n\nBug Fixes\n---------\n\n- `4344 &lt;https://github.com/pytest-dev/pytest/issues/4344&gt;`_: Fix RuntimeError/StopIteration when trying to collect package with &quot;__init__.py&quot; only.\n\n\n- `5115 &lt;https://github.com/pytest-dev/pytest/issues/5115&gt;`_: Warnings issued during ``pytest_configure`` are explicitly not treated as errors, even if configured as such, because it otherwise completely breaks pytest.\n\n\n- `5477 &lt;https://github.com/pytest-dev/pytest/issues/5477&gt;`_: The XML file produced by ``--junitxml`` now correctly contain a ``&lt;testsuites&gt;`` root element.\n\n\n- `5524 &lt;https://github.com/pytest-dev/pytest/issues/5524&gt;`_: Fix issue where ``tmp_path`` and ``tmpdir`` would not remove directories containing files marked as read-only,\n  which could lead to pytest crashing when executed a second time with the ``--basetemp`` option.\n\n\n- `5537 &lt;https://github.com/pytest-dev/pytest/issues/5537&gt;`_: Replace ``importlib_metadata`` backport with ``importlib.metadata`` from the\n  standard library on Python 3.8+.\n\n\n- `5578 &lt;https://github.com/pytest-dev/pytest/issues/5578&gt;`_: Improve type checking for some exception-raising functions (``pytest.xfail``, ``pytest.skip``, etc)\n  so they provide better error messages when users meant to use marks (for example ``pytest.xfail``\n  instead of ``pytest.mark.xfail``).\n\n\n- `5606 &lt;https://github.com/pytest-dev/pytest/issues/5606&gt;`_: Fixed internal error when test functions were patched with objects that cannot be compared\n  for truth values against others, like ``numpy`` arrays.\n\n\n- `5634 &lt;https://github.com/pytest-dev/pytest/issues/5634&gt;`_: ``pytest.exit`` is now correctly handled in ``unittest`` cases.\n  This makes ``unittest`` cases handle ``quit`` from pytest&#39;s pdb correctly.\n\n\n- `5650 &lt;https://github.com/pytest-dev/pytest/issues/5650&gt;`_: Improved output when parsing an ini configuration file fails.\n\n\n- `5701 &lt;https://github.com/pytest-dev/pytest/issues/5701&gt;`_: Fix collection of ``staticmethod`` objects defined with ``functools.partial``.\n\n\n- `5734 &lt;https://github.com/pytest-dev/pytest/issues/5734&gt;`_: Skip async generator test functions, and update the warning message to refer to ``async def`` functions.\n\n\n\nImproved Documentation\n----------------------\n\n- `5669 &lt;https://github.com/pytest-dev/pytest/issues/5669&gt;`_: Add docstring for ``Testdir.copy_example``.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `5095 &lt;https://github.com/pytest-dev/pytest/issues/5095&gt;`_: XML files of the ``xunit2`` family are now validated against the schema by pytest&#39;s own test suite\n  to avoid future regressions.\n\n\n- `5516 &lt;https://github.com/pytest-dev/pytest/issues/5516&gt;`_: Cache node splitting function which can improve collection performance in very large test suites.\n\n\n- `5603 &lt;https://github.com/pytest-dev/pytest/issues/5603&gt;`_: Simplified internal ``SafeRepr`` class and removed some dead code.\n\n\n- `5664 &lt;https://github.com/pytest-dev/pytest/issues/5664&gt;`_: When invoking pytest&#39;s own testsuite with ``PYTHONDONTWRITEBYTECODE=1``,\n  the ``test_xfail_handling`` test no longer fails.\n\n\n- `5684 &lt;https://github.com/pytest-dev/pytest/issues/5684&gt;`_: Replace manual handling of ``OSError.errno`` in the codebase by new ``OSError`` subclasses (``PermissionError``, ``FileNotFoundError``, etc.).\n   ```\n   \n  \n  \n   ### 5.0.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5479 &lt;https://github.com/pytest-dev/pytest/issues/5479&gt;`_: Improve quoting in ``raises`` match failure message.\n\n\n- `5523 &lt;https://github.com/pytest-dev/pytest/issues/5523&gt;`_: Fixed using multiple short options together in the command-line (for example ``-vs``) in Python 3.8+.\n\n\n- `5547 &lt;https://github.com/pytest-dev/pytest/issues/5547&gt;`_: ``--step-wise`` now handles ``xfail(strict=True)`` markers properly.\n\n\n\nImproved Documentation\n----------------------\n\n- `5517 &lt;https://github.com/pytest-dev/pytest/issues/5517&gt;`_: Improve &quot;Declaring new hooks&quot; section in chapter &quot;Writing Plugins&quot;\n   ```\n   \n  \n  \n   ### 5.0.0\n   ```\n   =========================\n\nImportant\n---------\n\nThis release is a Python3.5+ only release.\n\nFor more details, see our `Python 2.7 and 3.4 support plan &lt;https://docs.pytest.org/en/latest/py27-py34-deprecation.html&gt;`__.\n\nRemovals\n--------\n\n- `1149 &lt;https://github.com/pytest-dev/pytest/issues/1149&gt;`_: Pytest no longer accepts prefixes of command-line arguments, for example\n  typing ``pytest --doctest-mod`` inplace of ``--doctest-modules``.\n  This was previously allowed where the ``ArgumentParser`` thought it was unambiguous,\n  but this could be incorrect due to delayed parsing of options for plugins.\n  See for example issues `1149 &lt;https://github.com/pytest-dev/pytest/issues/1149&gt;`__,\n  `3413 &lt;https://github.com/pytest-dev/pytest/issues/3413&gt;`__, and\n  `4009 &lt;https://github.com/pytest-dev/pytest/issues/4009&gt;`__.\n\n\n- `5402 &lt;https://github.com/pytest-dev/pytest/issues/5402&gt;`_: **PytestDeprecationWarning are now errors by default.**\n\n  Following our plan to remove deprecated features with as little disruption as\n  possible, all warnings of type ``PytestDeprecationWarning`` now generate errors\n  instead of warning messages.\n\n  **The affected features will be effectively removed in pytest 5.1**, so please consult the\n  `Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`__\n  section in the docs for directions on how to update existing code.\n\n  In the pytest ``5.0.X`` series, it is possible to change the errors back into warnings as a stop\n  gap measure by adding this to your ``pytest.ini`` file:\n\n  .. code-block:: ini\n\n      [pytest]\n      filterwarnings =\n          ignore::pytest.PytestDeprecationWarning\n\n  But this will stop working when pytest ``5.1`` is released.\n\n  **If you have concerns** about the removal of a specific feature, please add a\n  comment to `5402 &lt;https://github.com/pytest-dev/pytest/issues/5402&gt;`__.\n\n\n- `5412 &lt;https://github.com/pytest-dev/pytest/issues/5412&gt;`_: ``ExceptionInfo`` objects (returned by ``pytest.raises``) now have the same ``str`` representation as ``repr``, which\n  avoids some confusion when users use ``print(e)`` to inspect the object.\n\n  This means code like:\n\n  .. code-block:: python\n\n        with pytest.raises(SomeException) as e:\n            ...\n        assert &quot;some message&quot; in str(e)\n\n\n  Needs to be changed to:\n\n  .. code-block:: python\n\n        with pytest.raises(SomeException) as e:\n            ...\n        assert &quot;some message&quot; in str(e.value)\n\n\n\n\nDeprecations\n------------\n\n- `4488 &lt;https://github.com/pytest-dev/pytest/issues/4488&gt;`_: The removal of the ``--result-log`` option and module has been postponed to (tentatively) pytest 6.0 as\n  the team has not yet got around to implement a good alternative for it.\n\n\n- `466 &lt;https://github.com/pytest-dev/pytest/issues/466&gt;`_: The ``funcargnames`` attribute has been an alias for ``fixturenames`` since\n  pytest 2.3, and is now deprecated in code too.\n\n\n\nFeatures\n--------\n\n- `3457 &lt;https://github.com/pytest-dev/pytest/issues/3457&gt;`_: New `pytest_assertion_pass &lt;https://docs.pytest.org/en/latest/reference.html_pytest.hookspec.pytest_assertion_pass&gt;`__\n  hook, called with context information when an assertion *passes*.\n\n  This hook is still **experimental** so use it with caution.\n\n\n- `5440 &lt;https://github.com/pytest-dev/pytest/issues/5440&gt;`_: The `faulthandler &lt;https://docs.python.org/3/library/faulthandler.html&gt;`__ standard library\n  module is now enabled by default to help users diagnose crashes in C modules.\n\n  This functionality was provided by integrating the external\n  `pytest-faulthandler &lt;https://github.com/pytest-dev/pytest-faulthandler&gt;`__ plugin into the core,\n  so users should remove that plugin from their requirements if used.\n\n  For more information see the docs: https://docs.pytest.org/en/latest/usage.htmlfault-handler\n\n\n- `5452 &lt;https://github.com/pytest-dev/pytest/issues/5452&gt;`_: When warnings are configured as errors, pytest warnings now appear as originating from ``pytest.`` instead of the internal ``_pytest.warning_types.`` module.\n\n\n- `5125 &lt;https://github.com/pytest-dev/pytest/issues/5125&gt;`_: ``Session.exitcode`` values are now coded in ``pytest.ExitCode``, an ``IntEnum``. This makes the exit code available for consumer code and are more explicit other than just documentation. User defined exit codes are still valid, but should be used with caution.\n\n  The team doesn&#39;t expect this change to break test suites or plugins in general, except in esoteric/specific scenarios.\n\n  **pytest-xdist** users should upgrade to ``1.29.0`` or later, as ``pytest-xdist`` required a compatibility fix because of this change.\n\n\n\nBug Fixes\n---------\n\n- `1403 &lt;https://github.com/pytest-dev/pytest/issues/1403&gt;`_: Switch from ``imp`` to ``importlib``.\n\n\n- `1671 &lt;https://github.com/pytest-dev/pytest/issues/1671&gt;`_: The name of the ``.pyc`` files cached by the assertion writer now includes the pytest version\n  to avoid stale caches.\n\n\n- `2761 &lt;https://github.com/pytest-dev/pytest/issues/2761&gt;`_: Honor PEP 235 on case-insensitive file systems.\n\n\n- `5078 &lt;https://github.com/pytest-dev/pytest/issues/5078&gt;`_: Test module is no longer double-imported when using ``--pyargs``.\n\n\n- `5260 &lt;https://github.com/pytest-dev/pytest/issues/5260&gt;`_: Improved comparison of byte strings.\n\n  When comparing bytes, the assertion message used to show the byte numeric value when showing the differences::\n\n          def test():\n      &gt;       assert b&#39;spam&#39; == b&#39;eggs&#39;\n      E       AssertionError: assert b&#39;spam&#39; == b&#39;eggs&#39;\n      E         At index 0 diff: 115 != 101\n      E         Use -v to get the full diff\n\n  It now shows the actual ascii representation instead, which is often more useful::\n\n          def test():\n      &gt;       assert b&#39;spam&#39; == b&#39;eggs&#39;\n      E       AssertionError: assert b&#39;spam&#39; == b&#39;eggs&#39;\n      E         At index 0 diff: b&#39;s&#39; != b&#39;e&#39;\n      E         Use -v to get the full diff\n\n\n- `5335 &lt;https://github.com/pytest-dev/pytest/issues/5335&gt;`_: Colorize level names when the level in the logging format is formatted using\n  &#39;%(levelname).Xs&#39; (truncated fixed width alignment), where X is an integer.\n\n\n- `5354 &lt;https://github.com/pytest-dev/pytest/issues/5354&gt;`_: Fix ``pytest.mark.parametrize`` when the argvalues is an iterator.\n\n\n- `5370 &lt;https://github.com/pytest-dev/pytest/issues/5370&gt;`_: Revert unrolling of ``all()`` to fix ``NameError`` on nested comprehensions.\n\n\n- `5371 &lt;https://github.com/pytest-dev/pytest/issues/5371&gt;`_: Revert unrolling of ``all()`` to fix incorrect handling of generators with ``if``.\n\n\n- `5372 &lt;https://github.com/pytest-dev/pytest/issues/5372&gt;`_: Revert unrolling of ``all()`` to fix incorrect assertion when using ``all()`` in an expression.\n\n\n- `5383 &lt;https://github.com/pytest-dev/pytest/issues/5383&gt;`_: ``-q`` has again an impact on the style of the collected items\n  (``--collect-only``) when ``--log-cli-level`` is used.\n\n\n- `5389 &lt;https://github.com/pytest-dev/pytest/issues/5389&gt;`_: Fix regressions of `5063 &lt;https://github.com/pytest-dev/pytest/pull/5063&gt;`__ for ``importlib_metadata.PathDistribution`` which have their ``files`` attribute being ``None``.\n\n\n- `5390 &lt;https://github.com/pytest-dev/pytest/issues/5390&gt;`_: Fix regression where the ``obj`` attribute of ``TestCase`` items was no longer bound to methods.\n\n\n- `5404 &lt;https://github.com/pytest-dev/pytest/issues/5404&gt;`_: Emit a warning when attempting to unwrap a broken object raises an exception,\n  for easier debugging (`5080 &lt;https://github.com/pytest-dev/pytest/issues/5080&gt;`__).\n\n\n- `5432 &lt;https://github.com/pytest-dev/pytest/issues/5432&gt;`_: Prevent &quot;already imported&quot; warnings from assertion rewriter when invoking pytest in-process multiple times.\n\n\n- `5433 &lt;https://github.com/pytest-dev/pytest/issues/5433&gt;`_: Fix assertion rewriting in packages (``__init__.py``).\n\n\n- `5444 &lt;https://github.com/pytest-dev/pytest/issues/5444&gt;`_: Fix ``--stepwise`` mode when the first file passed on the command-line fails to collect.\n\n\n- `5482 &lt;https://github.com/pytest-dev/pytest/issues/5482&gt;`_: Fix bug introduced in 4.6.0 causing collection errors when passing\n  more than 2 positional arguments to ``pytest.mark.parametrize``.\n\n\n- `5505 &lt;https://github.com/pytest-dev/pytest/issues/5505&gt;`_: Fix crash when discovery fails while using ``-p no:terminal``.\n\n\n\nImproved Documentation\n----------------------\n\n- `5315 &lt;https://github.com/pytest-dev/pytest/issues/5315&gt;`_: Expand docs on mocking classes and dictionaries with ``monkeypatch``.\n\n\n- `5416 &lt;https://github.com/pytest-dev/pytest/issues/5416&gt;`_: Fix PytestUnknownMarkWarning in run/skip example.\n   ```\n   \n  \n  \n   ### 4.6.6\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5523 &lt;https://github.com/pytest-dev/pytest/issues/5523&gt;`_: Fixed using multiple short options together in the command-line (for example ``-vs``) in Python 3.8+.\n\n\n- `5537 &lt;https://github.com/pytest-dev/pytest/issues/5537&gt;`_: Replace ``importlib_metadata`` backport with ``importlib.metadata`` from the\n  standard library on Python 3.8+.\n\n\n- `5806 &lt;https://github.com/pytest-dev/pytest/issues/5806&gt;`_: Fix &quot;lexer&quot; being used when uploading to bpaste.net from ``--pastebin`` to &quot;text&quot;.\n\n\n- `5902 &lt;https://github.com/pytest-dev/pytest/issues/5902&gt;`_: Fix warnings about deprecated ``cmp`` attribute in ``attrs&gt;=19.2``.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `5801 &lt;https://github.com/pytest-dev/pytest/issues/5801&gt;`_: Fixes python version checks (detected by ``flake8-2020``) in case python4 becomes a thing.\n   ```\n   \n  \n  \n   ### 4.6.5\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `4344 &lt;https://github.com/pytest-dev/pytest/issues/4344&gt;`_: Fix RuntimeError/StopIteration when trying to collect package with &quot;__init__.py&quot; only.\n\n\n- `5478 &lt;https://github.com/pytest-dev/pytest/issues/5478&gt;`_: Fix encode error when using unicode strings in exceptions with ``pytest.raises``.\n\n\n- `5524 &lt;https://github.com/pytest-dev/pytest/issues/5524&gt;`_: Fix issue where ``tmp_path`` and ``tmpdir`` would not remove directories containing files marked as read-only,\n  which could lead to pytest crashing when executed a second time with the ``--basetemp`` option.\n\n\n- `5547 &lt;https://github.com/pytest-dev/pytest/issues/5547&gt;`_: ``--step-wise`` now handles ``xfail(strict=True)`` markers properly.\n\n\n- `5650 &lt;https://github.com/pytest-dev/pytest/issues/5650&gt;`_: Improved output when parsing an ini configuration file fails.\n   ```\n   \n  \n  \n   ### 4.6.4\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5404 &lt;https://github.com/pytest-dev/pytest/issues/5404&gt;`_: Emit a warning when attempting to unwrap a broken object raises an exception,\n  for easier debugging (`5080 &lt;https://github.com/pytest-dev/pytest/issues/5080&gt;`__).\n\n\n- `5444 &lt;https://github.com/pytest-dev/pytest/issues/5444&gt;`_: Fix ``--stepwise`` mode when the first file passed on the command-line fails to collect.\n\n\n- `5482 &lt;https://github.com/pytest-dev/pytest/issues/5482&gt;`_: Fix bug introduced in 4.6.0 causing collection errors when passing\n  more than 2 positional arguments to ``pytest.mark.parametrize``.\n\n\n- `5505 &lt;https://github.com/pytest-dev/pytest/issues/5505&gt;`_: Fix crash when discovery fails while using ``-p no:terminal``.\n   ```\n   \n  \n  \n   ### 4.6.3\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5383 &lt;https://github.com/pytest-dev/pytest/issues/5383&gt;`_: ``-q`` has again an impact on the style of the collected items\n  (``--collect-only``) when ``--log-cli-level`` is used.\n\n\n- `5389 &lt;https://github.com/pytest-dev/pytest/issues/5389&gt;`_: Fix regressions of `5063 &lt;https://github.com/pytest-dev/pytest/pull/5063&gt;`__ for ``importlib_metadata.PathDistribution`` which have their ``files`` attribute being ``None``.\n\n\n- `5390 &lt;https://github.com/pytest-dev/pytest/issues/5390&gt;`_: Fix regression where the ``obj`` attribute of ``TestCase`` items was no longer bound to methods.\n   ```\n   \n  \n  \n   ### 4.6.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5370 &lt;https://github.com/pytest-dev/pytest/issues/5370&gt;`_: Revert unrolling of ``all()`` to fix ``NameError`` on nested comprehensions.\n\n\n- `5371 &lt;https://github.com/pytest-dev/pytest/issues/5371&gt;`_: Revert unrolling of ``all()`` to fix incorrect handling of generators with ``if``.\n\n\n- `5372 &lt;https://github.com/pytest-dev/pytest/issues/5372&gt;`_: Revert unrolling of ``all()`` to fix incorrect assertion when using ``all()`` in an expression.\n   ```\n   \n  \n  \n   ### 4.6.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5354 &lt;https://github.com/pytest-dev/pytest/issues/5354&gt;`_: Fix ``pytest.mark.parametrize`` when the argvalues is an iterator.\n\n\n- `5358 &lt;https://github.com/pytest-dev/pytest/issues/5358&gt;`_: Fix assertion rewriting of ``all()`` calls to deal with non-generators.\n   ```\n   \n  \n  \n   ### 4.6.0\n   ```\n   =========================\n\nImportant\n---------\n\nThe ``4.6.X`` series will be the last series to support **Python 2 and Python 3.4**.\n\nFor more details, see our `Python 2.7 and 3.4 support plan &lt;https://docs.pytest.org/en/latest/py27-py34-deprecation.html&gt;`__.\n\n\nFeatures\n--------\n\n- `4559 &lt;https://github.com/pytest-dev/pytest/issues/4559&gt;`_: Added the ``junit_log_passing_tests`` ini value which can be used to enable or disable logging of passing test output in the Junit XML file.\n\n\n- `4956 &lt;https://github.com/pytest-dev/pytest/issues/4956&gt;`_: pytester&#39;s ``testdir.spawn`` uses ``tmpdir`` as HOME/USERPROFILE directory.\n\n\n- `5062 &lt;https://github.com/pytest-dev/pytest/issues/5062&gt;`_: Unroll calls to ``all`` to full for-loops with assertion rewriting for better failure messages, especially when using Generator Expressions.\n\n\n- `5063 &lt;https://github.com/pytest-dev/pytest/issues/5063&gt;`_: Switch from ``pkg_resources`` to ``importlib-metadata`` for entrypoint detection for improved performance and import time.\n\n\n- `5091 &lt;https://github.com/pytest-dev/pytest/issues/5091&gt;`_: The output for ini options in ``--help`` has been improved.\n\n\n- `5269 &lt;https://github.com/pytest-dev/pytest/issues/5269&gt;`_: ``pytest.importorskip`` includes the ``ImportError`` now in the default ``reason``.\n\n\n- `5311 &lt;https://github.com/pytest-dev/pytest/issues/5311&gt;`_: Captured logs that are output for each failing test are formatted using the\n  ColoredLevelFormatter.\n\n\n- `5312 &lt;https://github.com/pytest-dev/pytest/issues/5312&gt;`_: Improved formatting of multiline log messages in Python 3.\n\n\n\nBug Fixes\n---------\n\n- `2064 &lt;https://github.com/pytest-dev/pytest/issues/2064&gt;`_: The debugging plugin imports the wrapped ``Pdb`` class (``--pdbcls``) on-demand now.\n\n\n- `4908 &lt;https://github.com/pytest-dev/pytest/issues/4908&gt;`_: The ``pytest_enter_pdb`` hook gets called with post-mortem (``--pdb``).\n\n\n- `5036 &lt;https://github.com/pytest-dev/pytest/issues/5036&gt;`_: Fix issue where fixtures dependent on other parametrized fixtures would be erroneously parametrized.\n\n\n- `5256 &lt;https://github.com/pytest-dev/pytest/issues/5256&gt;`_: Handle internal error due to a lone surrogate unicode character not being representable in Jython.\n\n\n- `5257 &lt;https://github.com/pytest-dev/pytest/issues/5257&gt;`_: Ensure that ``sys.stdout.mode`` does not include ``&#39;b&#39;`` as it is a text stream.\n\n\n- `5278 &lt;https://github.com/pytest-dev/pytest/issues/5278&gt;`_: Pytest&#39;s internal python plugin can be disabled using ``-p no:python`` again.\n\n\n- `5286 &lt;https://github.com/pytest-dev/pytest/issues/5286&gt;`_: Fix issue with ``disable_test_id_escaping_and_forfeit_all_rights_to_community_support`` option not working when using a list of test IDs in parametrized tests.\n\n\n- `5330 &lt;https://github.com/pytest-dev/pytest/issues/5330&gt;`_: Show the test module being collected when emitting ``PytestCollectionWarning`` messages for\n  test classes with ``__init__`` and ``__new__`` methods to make it easier to pin down the problem.\n\n\n- `5333 &lt;https://github.com/pytest-dev/pytest/issues/5333&gt;`_: Fix regression in 4.5.0 with ``--lf`` not re-running all tests with known failures from non-selected tests.\n\n\n\nImproved Documentation\n----------------------\n\n- `5250 &lt;https://github.com/pytest-dev/pytest/issues/5250&gt;`_: Expand docs on use of ``setenv`` and ``delenv`` with ``monkeypatch``.\n   ```\n   \n  \n  \n   ### 4.5.0\n   ```\n   =========================\n\nFeatures\n--------\n\n- `4826 &lt;https://github.com/pytest-dev/pytest/issues/4826&gt;`_: A warning is now emitted when unknown marks are used as a decorator.\n  This is often due to a typo, which can lead to silently broken tests.\n\n\n- `4907 &lt;https://github.com/pytest-dev/pytest/issues/4907&gt;`_: Show XFail reason as part of JUnitXML message field.\n\n\n- `5013 &lt;https://github.com/pytest-dev/pytest/issues/5013&gt;`_: Messages from crash reports are displayed within test summaries now, truncated to the terminal width.\n\n\n- `5023 &lt;https://github.com/pytest-dev/pytest/issues/5023&gt;`_: New flag ``--strict-markers`` that triggers an error when unknown markers (e.g. those not registered using the `markers option`_ in the configuration file) are used in the test suite.\n\n  The existing ``--strict`` option has the same behavior currently, but can be augmented in the future for additional checks.\n\n  .. _`markers option`: https://docs.pytest.org/en/latest/reference.htmlconfval-markers\n\n\n- `5026 &lt;https://github.com/pytest-dev/pytest/issues/5026&gt;`_: Assertion failure messages for sequences and dicts contain the number of different items now.\n\n\n- `5034 &lt;https://github.com/pytest-dev/pytest/issues/5034&gt;`_: Improve reporting with ``--lf`` and ``--ff`` (run-last-failure).\n\n\n- `5035 &lt;https://github.com/pytest-dev/pytest/issues/5035&gt;`_: The ``--cache-show`` option/action accepts an optional glob to show only matching cache entries.\n\n\n- `5059 &lt;https://github.com/pytest-dev/pytest/issues/5059&gt;`_: Standard input (stdin) can be given to pytester&#39;s ``Testdir.run()`` and ``Testdir.popen()``.\n\n\n- `5068 &lt;https://github.com/pytest-dev/pytest/issues/5068&gt;`_: The ``-r`` option learnt about ``A`` to display all reports (including passed ones) in the short test summary.\n\n\n- `5108 &lt;https://github.com/pytest-dev/pytest/issues/5108&gt;`_: The short test summary is displayed after passes with output (``-rP``).\n\n\n- `5172 &lt;https://github.com/pytest-dev/pytest/issues/5172&gt;`_: The ``--last-failed`` (``--lf``) option got smarter and will now skip entire files if all tests\n  of that test file have passed in previous runs, greatly speeding up collection.\n\n\n- `5177 &lt;https://github.com/pytest-dev/pytest/issues/5177&gt;`_: Introduce new specific warning ``PytestWarning`` subclasses to make it easier to filter warnings based on the class, rather than on the message. The new subclasses are:\n\n\n  * ``PytestAssertRewriteWarning``\n\n  * ``PytestCacheWarning``\n\n  * ``PytestCollectionWarning``\n\n  * ``PytestConfigWarning``\n\n  * ``PytestUnhandledCoroutineWarning``\n\n  * ``PytestUnknownMarkWarning``\n\n\n- `5202 &lt;https://github.com/pytest-dev/pytest/issues/5202&gt;`_: New ``record_testsuite_property`` session-scoped fixture allows users to log ``&lt;property&gt;`` tags at the ``testsuite``\n  level with the ``junitxml`` plugin.\n\n  The generated XML is compatible with the latest xunit standard, contrary to\n  the properties recorded by ``record_property`` and ``record_xml_attribute``.\n\n\n- `5214 &lt;https://github.com/pytest-dev/pytest/issues/5214&gt;`_: The default logging format has been changed to improve readability. Here is an\n  example of a previous logging message::\n\n      test_log_cli_enabled_disabled.py    3 CRITICAL critical message logged by test\n\n  This has now become::\n\n      CRITICAL root:test_log_cli_enabled_disabled.py:3 critical message logged by test\n\n  The formatting can be changed through the `log_format &lt;https://docs.pytest.org/en/latest/reference.htmlconfval-log_format&gt;`__ configuration option.\n\n\n- `5220 &lt;https://github.com/pytest-dev/pytest/issues/5220&gt;`_: ``--fixtures`` now also shows fixture scope for scopes other than ``&quot;function&quot;``.\n\n\n\nBug Fixes\n---------\n\n- `5113 &lt;https://github.com/pytest-dev/pytest/issues/5113&gt;`_: Deselected items from plugins using ``pytest_collect_modifyitems`` as a hookwrapper are correctly reported now.\n\n\n- `5144 &lt;https://github.com/pytest-dev/pytest/issues/5144&gt;`_: With usage errors ``exitstatus`` is set to ``EXIT_USAGEERROR`` in the ``pytest_sessionfinish`` hook now as expected.\n\n\n- `5235 &lt;https://github.com/pytest-dev/pytest/issues/5235&gt;`_: ``outcome.exit`` is not used with ``EOF`` in the pdb wrapper anymore, but only with ``quit``.\n\n\n\nImproved Documentation\n----------------------\n\n- `4935 &lt;https://github.com/pytest-dev/pytest/issues/4935&gt;`_: Expand docs on registering marks and the effect of ``--strict``.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4942 &lt;https://github.com/pytest-dev/pytest/issues/4942&gt;`_: ``logging.raiseExceptions`` is not set to ``False`` anymore.\n\n\n- `5013 &lt;https://github.com/pytest-dev/pytest/issues/5013&gt;`_: pytest now depends on `wcwidth &lt;https://pypi.org/project/wcwidth&gt;`__ to properly track unicode character sizes for more precise terminal output.\n\n\n- `5059 &lt;https://github.com/pytest-dev/pytest/issues/5059&gt;`_: pytester&#39;s ``Testdir.popen()`` uses ``stdout`` and ``stderr`` via keyword arguments with defaults now (``subprocess.PIPE``).\n\n\n- `5069 &lt;https://github.com/pytest-dev/pytest/issues/5069&gt;`_: The code for the short test summary in the terminal was moved to the terminal plugin.\n\n\n- `5082 &lt;https://github.com/pytest-dev/pytest/issues/5082&gt;`_: Improved validation of kwargs for various methods in the pytester plugin.\n\n\n- `5202 &lt;https://github.com/pytest-dev/pytest/issues/5202&gt;`_: ``record_property`` now emits a ``PytestWarning`` when used with ``junit_family=xunit2``: the fixture generates\n  ``property`` tags as children of ``testcase``, which is not permitted according to the most\n  `recent schema &lt;https://github.com/jenkinsci/xunit-plugin/blob/master/\n  src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd&gt;`__.\n\n\n- `5239 &lt;https://github.com/pytest-dev/pytest/issues/5239&gt;`_: Pin ``pluggy`` to ``&lt; 1.0`` so we don&#39;t update to ``1.0`` automatically when\n  it gets released: there are planned breaking changes, and we want to ensure\n  pytest properly supports ``pluggy 1.0``.\n   ```\n   \n  \n  \n   ### 4.4.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5089 &lt;https://github.com/pytest-dev/pytest/issues/5089&gt;`_: Fix crash caused by error in ``__repr__`` function with both ``showlocals`` and verbose output enabled.\n\n\n- `5139 &lt;https://github.com/pytest-dev/pytest/issues/5139&gt;`_: Eliminate core dependency on &#39;terminal&#39; plugin.\n\n\n- `5229 &lt;https://github.com/pytest-dev/pytest/issues/5229&gt;`_: Require ``pluggy&gt;=0.11.0`` which reverts a dependency to ``importlib-metadata`` added in ``0.10.0``.\n  The ``importlib-metadata`` package cannot be imported when installed as an egg and causes issues when relying on ``setup.py`` to install test dependencies.\n\n\n\nImproved Documentation\n----------------------\n\n- `5171 &lt;https://github.com/pytest-dev/pytest/issues/5171&gt;`_: Doc: ``pytest_ignore_collect``, ``pytest_collect_directory``, ``pytest_collect_file`` and ``pytest_pycollect_makemodule`` hooks&#39;s &#39;path&#39; parameter documented type is now ``py.path.local``\n\n\n- `5188 &lt;https://github.com/pytest-dev/pytest/issues/5188&gt;`_: Improve help for ``--runxfail`` flag.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `5182 &lt;https://github.com/pytest-dev/pytest/issues/5182&gt;`_: Removed internal and unused ``_pytest.deprecated.MARK_INFO_ATTRIBUTE``.\n   ```\n   \n  \n  \n   ### 4.4.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `5031 &lt;https://github.com/pytest-dev/pytest/issues/5031&gt;`_: Environment variables are properly restored when using pytester&#39;s ``testdir`` fixture.\n\n\n- `5039 &lt;https://github.com/pytest-dev/pytest/issues/5039&gt;`_: Fix regression with ``--pdbcls``, which stopped working with local modules in 4.0.0.\n\n\n- `5092 &lt;https://github.com/pytest-dev/pytest/issues/5092&gt;`_: Produce a warning when unknown keywords are passed to ``pytest.param(...)``.\n\n\n- `5098 &lt;https://github.com/pytest-dev/pytest/issues/5098&gt;`_: Invalidate import caches with ``monkeypatch.syspath_prepend``, which is required with namespace packages being used.\n   ```\n   \n  \n  \n   ### 4.4.0\n   ```\n   =========================\n\nFeatures\n--------\n\n- `2224 &lt;https://github.com/pytest-dev/pytest/issues/2224&gt;`_: ``async`` test functions are skipped and a warning is emitted when a suitable\n  async plugin is not installed (such as ``pytest-asyncio`` or ``pytest-trio``).\n\n  Previously ``async`` functions would not execute at all but still be marked as &quot;passed&quot;.\n\n\n- `2482 &lt;https://github.com/pytest-dev/pytest/issues/2482&gt;`_: Include new ``disable_test_id_escaping_and_forfeit_all_rights_to_community_support`` option to disable ascii-escaping in parametrized values. This may cause a series of problems and as the name makes clear, use at your own risk.\n\n\n- `4718 &lt;https://github.com/pytest-dev/pytest/issues/4718&gt;`_: The ``-p`` option can now be used to early-load plugins also by entry-point name, instead of just\n  by module name.\n\n  This makes it possible to early load external plugins like ``pytest-cov`` in the command-line::\n\n      pytest -p pytest_cov\n\n\n- `4855 &lt;https://github.com/pytest-dev/pytest/issues/4855&gt;`_: The ``--pdbcls`` option handles classes via module attributes now (e.g.\n  ``pdb:pdb.Pdb`` with `pdb++`_), and its validation was improved.\n\n  .. _pdb++: https://pypi.org/project/pdbpp/\n\n\n- `4875 &lt;https://github.com/pytest-dev/pytest/issues/4875&gt;`_: The `testpaths &lt;https://docs.pytest.org/en/latest/reference.htmlconfval-testpaths&gt;`__ configuration option is now displayed next\n  to the ``rootdir`` and ``inifile`` lines in the pytest header if the option is in effect, i.e., directories or file names were\n  not explicitly passed in the command line.\n\n  Also, ``inifile`` is only displayed if there&#39;s a configuration file, instead of an empty ``inifile:`` string.\n\n\n- `4911 &lt;https://github.com/pytest-dev/pytest/issues/4911&gt;`_: Doctests can be skipped now dynamically using ``pytest.skip()``.\n\n\n- `4920 &lt;https://github.com/pytest-dev/pytest/issues/4920&gt;`_: Internal refactorings have been made in order to make the implementation of the\n  `pytest-subtests &lt;https://github.com/pytest-dev/pytest-subtests&gt;`__ plugin\n  possible, which adds unittest sub-test support and a new ``subtests`` fixture as discussed in\n  `1367 &lt;https://github.com/pytest-dev/pytest/issues/1367&gt;`__.\n\n  For details on the internal refactorings, please see the details on the related PR.\n\n\n- `4931 &lt;https://github.com/pytest-dev/pytest/issues/4931&gt;`_: pytester&#39;s ``LineMatcher`` asserts that the passed lines are a sequence.\n\n\n- `4936 &lt;https://github.com/pytest-dev/pytest/issues/4936&gt;`_: Handle ``-p plug`` after ``-p no:plug``.\n\n  This can be used to override a blocked plugin (e.g. in &quot;addopts&quot;) from the\n  command line etc.\n\n\n- `4951 &lt;https://github.com/pytest-dev/pytest/issues/4951&gt;`_: Output capturing is handled correctly when only capturing via fixtures (capsys, capfs) with ``pdb.set_trace()``.\n\n\n- `4956 &lt;https://github.com/pytest-dev/pytest/issues/4956&gt;`_: ``pytester`` sets ``$HOME`` and ``$USERPROFILE`` to the temporary directory during test runs.\n\n  This ensures to not load configuration files from the real user&#39;s home directory.\n\n\n- `4980 &lt;https://github.com/pytest-dev/pytest/issues/4980&gt;`_: Namespace packages are handled better with ``monkeypatch.syspath_prepend`` and ``testdir.syspathinsert`` (via ``pkg_resources.fixup_namespace_packages``).\n\n\n- `4993 &lt;https://github.com/pytest-dev/pytest/issues/4993&gt;`_: The stepwise plugin reports status information now.\n\n\n- `5008 &lt;https://github.com/pytest-dev/pytest/issues/5008&gt;`_: If a ``setup.cfg`` file contains ``[tool:pytest]`` and also the no longer supported ``[pytest]`` section, pytest will use ``[tool:pytest]`` ignoring ``[pytest]``. Previously it would unconditionally error out.\n\n  This makes it simpler for plugins to support old pytest versions.\n\n\n\nBug Fixes\n---------\n\n- `1895 &lt;https://github.com/pytest-dev/pytest/issues/1895&gt;`_: Fix bug where fixtures requested dynamically via ``request.getfixturevalue()`` might be teardown\n  before the requesting fixture.\n\n\n- `4851 &lt;https://github.com/pytest-dev/pytest/issues/4851&gt;`_: pytester unsets ``PYTEST_ADDOPTS`` now to not use outer options with ``testdir.runpytest()``.\n\n\n- `4903 &lt;https://github.com/pytest-dev/pytest/issues/4903&gt;`_: Use the correct modified time for years after 2038 in rewritten ``.pyc`` files.\n\n\n- `4928 &lt;https://github.com/pytest-dev/pytest/issues/4928&gt;`_: Fix line offsets with ``ScopeMismatch`` errors.\n\n\n- `4957 &lt;https://github.com/pytest-dev/pytest/issues/4957&gt;`_: ``-p no:plugin`` is handled correctly for default (internal) plugins now, e.g. with ``-p no:capture``.\n\n  Previously they were loaded (imported) always, making e.g. the ``capfd`` fixture available.\n\n\n- `4968 &lt;https://github.com/pytest-dev/pytest/issues/4968&gt;`_: The pdb ``quit`` command is handled properly when used after the ``debug`` command with `pdb++`_.\n\n  .. _pdb++: https://pypi.org/project/pdbpp/\n\n\n- `4975 &lt;https://github.com/pytest-dev/pytest/issues/4975&gt;`_: Fix the interpretation of ``-qq`` option where it was being considered as ``-v`` instead.\n\n\n- `4978 &lt;https://github.com/pytest-dev/pytest/issues/4978&gt;`_: ``outcomes.Exit`` is not swallowed in ``assertrepr_compare`` anymore.\n\n\n- `4988 &lt;https://github.com/pytest-dev/pytest/issues/4988&gt;`_: Close logging&#39;s file handler explicitly when the session finishes.\n\n\n- `5003 &lt;https://github.com/pytest-dev/pytest/issues/5003&gt;`_: Fix line offset with mark collection error (off by one).\n\n\n\nImproved Documentation\n----------------------\n\n- `4974 &lt;https://github.com/pytest-dev/pytest/issues/4974&gt;`_: Update docs for ``pytest_cmdline_parse`` hook to note availability liminations\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4718 &lt;https://github.com/pytest-dev/pytest/issues/4718&gt;`_: ``pluggy&gt;=0.9`` is now required.\n\n\n- `4815 &lt;https://github.com/pytest-dev/pytest/issues/4815&gt;`_: ``funcsigs&gt;=1.0`` is now required for Python 2.7.\n\n\n- `4829 &lt;https://github.com/pytest-dev/pytest/issues/4829&gt;`_: Some left-over internal code related to ``yield`` tests has been removed.\n\n\n- `4890 &lt;https://github.com/pytest-dev/pytest/issues/4890&gt;`_: Remove internally unused ``anypython`` fixture from the pytester plugin.\n\n\n- `4912 &lt;https://github.com/pytest-dev/pytest/issues/4912&gt;`_: Remove deprecated Sphinx directive, ``add_description_unit()``,\n  pin sphinx-removed-in to &gt;= 0.2.0 to support Sphinx 2.0.\n\n\n- `4913 &lt;https://github.com/pytest-dev/pytest/issues/4913&gt;`_: Fix pytest tests invocation with custom ``PYTHONPATH``.\n\n\n- `4965 &lt;https://github.com/pytest-dev/pytest/issues/4965&gt;`_: New ``pytest_report_to_serializable`` and ``pytest_report_from_serializable`` **experimental** hooks.\n\n  These hooks will be used by ``pytest-xdist``, ``pytest-subtests``, and the replacement for\n  resultlog to serialize and customize reports.\n\n  They are experimental, meaning that their details might change or even be removed\n  completely in future patch releases without warning.\n\n  Feedback is welcome from plugin authors and users alike.\n\n\n- `4987 &lt;https://github.com/pytest-dev/pytest/issues/4987&gt;`_: ``Collector.repr_failure`` respects the ``--tb`` option, but only defaults to ``short`` now (with ``auto``).\n   ```\n   \n  \n  \n   ### 4.3.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `4810 &lt;https://github.com/pytest-dev/pytest/issues/4810&gt;`_: Logging messages inside ``pytest_runtest_logreport()`` are now properly captured and displayed.\n\n\n- `4861 &lt;https://github.com/pytest-dev/pytest/issues/4861&gt;`_: Improve validation of contents written to captured output so it behaves the same as when capture is disabled.\n\n\n- `4898 &lt;https://github.com/pytest-dev/pytest/issues/4898&gt;`_: Fix ``AttributeError: FixtureRequest has no &#39;confg&#39; attribute`` bug in ``testdir.copy_example``.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4768 &lt;https://github.com/pytest-dev/pytest/issues/4768&gt;`_: Avoid pkg_resources import at the top-level.\n   ```\n   \n  \n  \n   ### 4.3.0\n   ```\n   =========================\n\nDeprecations\n------------\n\n- `4724 &lt;https://github.com/pytest-dev/pytest/issues/4724&gt;`_: ``pytest.warns()`` now emits a warning when it receives unknown keyword arguments.\n\n  This will be changed into an error in the future.\n\n\n\nFeatures\n--------\n\n- `2753 &lt;https://github.com/pytest-dev/pytest/issues/2753&gt;`_: Usage errors from argparse are mapped to pytest&#39;s ``UsageError``.\n\n\n- `3711 &lt;https://github.com/pytest-dev/pytest/issues/3711&gt;`_: Add the ``--ignore-glob`` parameter to exclude test-modules with Unix shell-style wildcards.\n  Add the ``collect_ignore_glob`` for ``conftest.py`` to exclude test-modules with Unix shell-style wildcards.\n\n\n- `4698 &lt;https://github.com/pytest-dev/pytest/issues/4698&gt;`_: The warning about Python 2.7 and 3.4 not being supported in pytest 5.0 has been removed.\n\n  In the end it was considered to be more\n  of a nuisance than actual utility and users of those Python versions shouldn&#39;t have problems as ``pip`` will not\n  install pytest 5.0 on those interpreters.\n\n\n- `4707 &lt;https://github.com/pytest-dev/pytest/issues/4707&gt;`_: With the help of new ``set_log_path()`` method there is a way to set ``log_file`` paths from hooks.\n\n\n\nBug Fixes\n---------\n\n- `4651 &lt;https://github.com/pytest-dev/pytest/issues/4651&gt;`_: ``--help`` and ``--version`` are handled with ``UsageError``.\n\n\n- `4782 &lt;https://github.com/pytest-dev/pytest/issues/4782&gt;`_: Fix ``AssertionError`` with collection of broken symlinks with packages.\n   ```\n   \n  \n  \n   ### 4.2.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `2895 &lt;https://github.com/pytest-dev/pytest/issues/2895&gt;`_: The ``pytest_report_collectionfinish`` hook now is also called with ``--collect-only``.\n\n\n- `3899 &lt;https://github.com/pytest-dev/pytest/issues/3899&gt;`_: Do not raise ``UsageError`` when an imported package has a ``pytest_plugins.py`` child module.\n\n\n- `4347 &lt;https://github.com/pytest-dev/pytest/issues/4347&gt;`_: Fix output capturing when using pdb++ with recursive debugging.\n\n\n- `4592 &lt;https://github.com/pytest-dev/pytest/issues/4592&gt;`_: Fix handling of ``collect_ignore`` via parent ``conftest.py``.\n\n\n- `4700 &lt;https://github.com/pytest-dev/pytest/issues/4700&gt;`_: Fix regression where ``setUpClass`` would always be called in subclasses even if all tests\n  were skipped by a ``unittest.skip()`` decorator applied in the subclass.\n\n\n- `4739 &lt;https://github.com/pytest-dev/pytest/issues/4739&gt;`_: Fix ``parametrize(... ids=&lt;function&gt;)`` when the function returns non-strings.\n\n\n- `4745 &lt;https://github.com/pytest-dev/pytest/issues/4745&gt;`_: Fix/improve collection of args when passing in ``__init__.py`` and a test file.\n\n\n- `4770 &lt;https://github.com/pytest-dev/pytest/issues/4770&gt;`_: ``more_itertools`` is now constrained to &lt;6.0.0 when required for Python 2.7 compatibility.\n\n\n- `526 &lt;https://github.com/pytest-dev/pytest/issues/526&gt;`_: Fix &quot;ValueError: Plugin already registered&quot; exceptions when running in build directories that symlink to actual source.\n\n\n\nImproved Documentation\n----------------------\n\n- `3899 &lt;https://github.com/pytest-dev/pytest/issues/3899&gt;`_: Add note to ``plugins.rst`` that ``pytest_plugins`` should not be used as a name for a user module containing plugins.\n\n\n- `4324 &lt;https://github.com/pytest-dev/pytest/issues/4324&gt;`_: Document how to use ``raises`` and ``does_not_raise`` to write parametrized tests with conditional raises.\n\n\n- `4709 &lt;https://github.com/pytest-dev/pytest/issues/4709&gt;`_: Document how to customize test failure messages when using\n  ``pytest.warns``.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4741 &lt;https://github.com/pytest-dev/pytest/issues/4741&gt;`_: Some verbosity related attributes of the TerminalReporter plugin are now\n  read only properties.\n   ```\n   \n  \n  \n   ### 4.2.0\n   ```\n   =========================\n\nFeatures\n--------\n\n- `3094 &lt;https://github.com/pytest-dev/pytest/issues/3094&gt;`_: `Classic xunit-style &lt;https://docs.pytest.org/en/latest/xunit_setup.html&gt;`__ functions and methods\n  now obey the scope of *autouse* fixtures.\n\n  This fixes a number of surprising issues like ``setup_method`` being called before session-scoped\n  autouse fixtures (see `517 &lt;https://github.com/pytest-dev/pytest/issues/517&gt;`__ for an example).\n\n\n- `4627 &lt;https://github.com/pytest-dev/pytest/issues/4627&gt;`_: Display a message at the end of the test session when running under Python 2.7 and 3.4 that pytest 5.0 will no longer\n  support those Python versions.\n\n\n- `4660 &lt;https://github.com/pytest-dev/pytest/issues/4660&gt;`_: The number of *selected* tests now are also displayed when the ``-k`` or ``-m`` flags are used.\n\n\n- `4688 &lt;https://github.com/pytest-dev/pytest/issues/4688&gt;`_: ``pytest_report_teststatus`` hook now can also receive a ``config`` parameter.\n\n\n- `4691 &lt;https://github.com/pytest-dev/pytest/issues/4691&gt;`_: ``pytest_terminal_summary`` hook now can also receive a ``config`` parameter.\n\n\n\nBug Fixes\n---------\n\n- `3547 &lt;https://github.com/pytest-dev/pytest/issues/3547&gt;`_: ``--junitxml`` can emit XML compatible with Jenkins xUnit.\n  ``junit_family`` INI option accepts ``legacy|xunit1``, which produces old style output, and ``xunit2`` that conforms more strictly to https://github.com/jenkinsci/xunit-plugin/blob/xunit-2.3.2/src/main/resources/org/jenkinsci/plugins/xunit/types/model/xsd/junit-10.xsd\n\n\n- `4280 &lt;https://github.com/pytest-dev/pytest/issues/4280&gt;`_: Improve quitting from pdb, especially with ``--trace``.\n\n  Using ``q[quit]`` after ``pdb.set_trace()`` will quit pytest also.\n\n\n- `4402 &lt;https://github.com/pytest-dev/pytest/issues/4402&gt;`_: Warning summary now groups warnings by message instead of by test id.\n\n  This makes the output more compact and better conveys the general idea of how much code is\n  actually generating warnings, instead of how many tests call that code.\n\n\n- `4536 &lt;https://github.com/pytest-dev/pytest/issues/4536&gt;`_: ``monkeypatch.delattr`` handles class descriptors like ``staticmethod``/``classmethod``.\n\n\n- `4649 &lt;https://github.com/pytest-dev/pytest/issues/4649&gt;`_: Restore marks being considered keywords for keyword expressions.\n\n\n- `4653 &lt;https://github.com/pytest-dev/pytest/issues/4653&gt;`_: ``tmp_path`` fixture and other related ones provides resolved path (a.k.a real path)\n\n\n- `4667 &lt;https://github.com/pytest-dev/pytest/issues/4667&gt;`_: ``pytest_terminal_summary`` uses result from ``pytest_report_teststatus`` hook, rather than hardcoded strings.\n\n\n- `4669 &lt;https://github.com/pytest-dev/pytest/issues/4669&gt;`_: Correctly handle ``unittest.SkipTest`` exception containing non-ascii characters on Python 2.\n\n\n- `4680 &lt;https://github.com/pytest-dev/pytest/issues/4680&gt;`_: Ensure the ``tmpdir`` and the ``tmp_path`` fixtures are the same folder.\n\n\n- `4681 &lt;https://github.com/pytest-dev/pytest/issues/4681&gt;`_: Ensure ``tmp_path`` is always a real path.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4643 &lt;https://github.com/pytest-dev/pytest/issues/4643&gt;`_: Use ``a.item()`` instead of the deprecated ``np.asscalar(a)`` in ``pytest.approx``.\n\n  ``np.asscalar`` has been `deprecated &lt;https://github.com/numpy/numpy/blob/master/doc/release/1.16.0-notes.rstnew-deprecations&gt;`__ in ``numpy 1.16.``.\n\n\n- `4657 &lt;https://github.com/pytest-dev/pytest/issues/4657&gt;`_: Copy saferepr from pylib\n\n\n- `4668 &lt;https://github.com/pytest-dev/pytest/issues/4668&gt;`_: The verbose word for expected failures in the teststatus report changes from ``xfail`` to ``XFAIL`` to be consistent with other test outcomes.\n   ```\n   \n  \n  \n   ### 4.1.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `2256 &lt;https://github.com/pytest-dev/pytest/issues/2256&gt;`_: Show full repr with ``assert a==b`` and ``-vv``.\n\n\n- `3456 &lt;https://github.com/pytest-dev/pytest/issues/3456&gt;`_: Extend Doctest-modules to ignore mock objects.\n\n\n- `4617 &lt;https://github.com/pytest-dev/pytest/issues/4617&gt;`_: Fixed ``pytest.warns`` bug when context manager is reused (e.g. multiple parametrization).\n\n\n- `4631 &lt;https://github.com/pytest-dev/pytest/issues/4631&gt;`_: Don&#39;t rewrite assertion when ``__getattr__`` is broken\n\n\n\nImproved Documentation\n----------------------\n\n- `3375 &lt;https://github.com/pytest-dev/pytest/issues/3375&gt;`_: Document that using ``setup.cfg`` may crash other tools or cause hard to track down problems because it uses a different parser than ``pytest.ini`` or ``tox.ini`` files.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4602 &lt;https://github.com/pytest-dev/pytest/issues/4602&gt;`_: Uninstall ``hypothesis`` in regen tox env.\n   ```\n   \n"},"comment":{"url":"https://api.github.com/repos/inhumantsar/python-ansible-vault-rekey/issues/comments/565770544","html_url":"https://github.com/inhumantsar/python-ansible-vault-rekey/pull/251#issuecomment-565770544","issue_url":"https://api.github.com/repos/inhumantsar/python-ansible-vault-rekey/issues/251","id":565770544,"node_id":"MDEyOklzc3VlQ29tbWVudDU2NTc3MDU0NA==","user":{"login":"pyup-bot","id":16239342,"node_id":"MDQ6VXNlcjE2MjM5MzQy","avatar_url":"https://avatars0.githubusercontent.com/u/16239342?v=4","gravatar_id":"","url":"https://api.github.com/users/pyup-bot","html_url":"https://github.com/pyup-bot","followers_url":"https://api.github.com/users/pyup-bot/followers","following_url":"https://api.github.com/users/pyup-bot/following{/other_user}","gists_url":"https://api.github.com/users/pyup-bot/gists{/gist_id}","starred_url":"https://api.github.com/users/pyup-bot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pyup-bot/subscriptions","organizations_url":"https://api.github.com/users/pyup-bot/orgs","repos_url":"https://api.github.com/users/pyup-bot/repos","events_url":"https://api.github.com/users/pyup-bot/events{/privacy}","received_events_url":"https://api.github.com/users/pyup-bot/received_events","type":"User","site_admin":false},"created_at":"2019-12-15T02:11:45Z","updated_at":"2019-12-15T02:11:45Z","author_association":"CONTRIBUTOR","body":"Closing this in favor of #255"}}
{"actor":{"display_login":"pyup-bot"}}