{"action":"closed","number":165,"pull_request":{"url":"https://api.github.com/repos/fgmacedo/django-export-action/pulls/165","id":249108684,"node_id":"MDExOlB1bGxSZXF1ZXN0MjQ5MTA4Njg0","html_url":"https://github.com/fgmacedo/django-export-action/pull/165","diff_url":"https://github.com/fgmacedo/django-export-action/pull/165.diff","patch_url":"https://github.com/fgmacedo/django-export-action/pull/165.patch","issue_url":"https://api.github.com/repos/fgmacedo/django-export-action/issues/165","number":165,"state":"closed","locked":false,"title":"Update pytest to 4.2.0","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},"body":"\nThis PR updates [pytest](https://pypi.org/project/pytest) from **3.2.5** to **4.2.0**.\n\n\n\n<details>\n  <summary>Changelog</summary>\n  \n  \n   ### 4.2.0\n   ```\n   =========================\n\nFeatures\n--------\n\n- `3094 &lt;https://github.com/pytest-dev/pytest/issues/3094&gt;`_: `Class 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  \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  \n  \n   ### 4.1.0\n   ```\n   =========================\n\nRemovals\n--------\n\n- `2169 &lt;https://github.com/pytest-dev/pytest/issues/2169&gt;`_: ``pytest.mark.parametrize``: in previous versions, errors raised by id functions were suppressed and changed into warnings. Now the exceptions are propagated, along with a pytest message informing the node, parameter value and index where the exception occurred.\n\n\n- `3078 &lt;https://github.com/pytest-dev/pytest/issues/3078&gt;`_: Remove legacy internal warnings system: ``config.warn``, ``Node.warn``. The ``pytest_logwarning`` now issues a warning when implemented.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlconfig-warn-and-node-warn&gt;`__ on information on how to update your code.\n\n\n- `3079 &lt;https://github.com/pytest-dev/pytest/issues/3079&gt;`_: Removed support for yield tests - they are fundamentally broken because they don&#39;t support fixtures properly since collection and test execution were separated.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlyield-tests&gt;`__ on information on how to update your code.\n\n\n- `3082 &lt;https://github.com/pytest-dev/pytest/issues/3082&gt;`_: Removed support for applying marks directly to values in ``pytest.mark.parametrize``. Use ``pytest.param`` instead.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlmarks-in-pytest-mark-parametrize&gt;`__ on information on how to update your code.\n\n\n- `3083 &lt;https://github.com/pytest-dev/pytest/issues/3083&gt;`_: Removed ``Metafunc.addcall``. This was the predecessor mechanism to ``pytest.mark.parametrize``.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlmetafunc-addcall&gt;`__ on information on how to update your code.\n\n\n- `3085 &lt;https://github.com/pytest-dev/pytest/issues/3085&gt;`_: Removed support for passing strings to ``pytest.main``. Now, always pass a list of strings instead.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlpassing-command-line-string-to-pytest-main&gt;`__ on information on how to update your code.\n\n\n- `3086 &lt;https://github.com/pytest-dev/pytest/issues/3086&gt;`_: ``[pytest]`` section in **setup.cfg** files is not longer supported, use ``[tool:pytest]`` instead. ``setup.cfg`` files\n  are meant for use with ``distutils``, and a section named ``pytest`` has notoriously been a source of conflicts and bugs.\n\n  Note that for **pytest.ini** and **tox.ini** files the section remains ``[pytest]``.\n\n\n- `3616 &lt;https://github.com/pytest-dev/pytest/issues/3616&gt;`_: Removed the deprecated compat properties for ``node.Class/Function/Module`` - use ``pytest.Class/Function/Module`` now.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlinternal-classes-accessed-through-node&gt;`__ on information on how to update your code.\n\n\n- `4421 &lt;https://github.com/pytest-dev/pytest/issues/4421&gt;`_: Removed the implementation of the ``pytest_namespace`` hook.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlpytest-namespace&gt;`__ on information on how to update your code.\n\n\n- `4489 &lt;https://github.com/pytest-dev/pytest/issues/4489&gt;`_: Removed ``request.cached_setup``. This was the predecessor mechanism to modern fixtures.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlcached-setup&gt;`__ on information on how to update your code.\n\n\n- `4535 &lt;https://github.com/pytest-dev/pytest/issues/4535&gt;`_: Removed the deprecated ``PyCollector.makeitem`` method. This method was made public by mistake a long time ago.\n\n\n- `4543 &lt;https://github.com/pytest-dev/pytest/issues/4543&gt;`_: Removed support to define fixtures using the ``pytest_funcarg__`` prefix. Use the ``pytest.fixture`` decorator instead.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlpytest-funcarg-prefix&gt;`__ on information on how to update your code.\n\n\n- `4545 &lt;https://github.com/pytest-dev/pytest/issues/4545&gt;`_: Calling fixtures directly is now always an error instead of a warning.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlcalling-fixtures-directly&gt;`__ on information on how to update your code.\n\n\n- `4546 &lt;https://github.com/pytest-dev/pytest/issues/4546&gt;`_: Remove ``Node.get_marker(name)`` the return value was not usable for more than a existence check.\n\n  Use ``Node.get_closest_marker(name)`` as a replacement.\n\n\n- `4547 &lt;https://github.com/pytest-dev/pytest/issues/4547&gt;`_: The deprecated ``record_xml_property`` fixture has been removed, use the more generic ``record_property`` instead.\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlrecord-xml-property&gt;`__ for more information.\n\n\n- `4548 &lt;https://github.com/pytest-dev/pytest/issues/4548&gt;`_: An error is now raised if the ``pytest_plugins`` variable is defined in a non-top-level ``conftest.py`` file (i.e., not residing in the ``rootdir``).\n\n  See our `docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlpytest-plugins-in-non-top-level-conftest-files&gt;`__ for more information.\n\n\n- `891 &lt;https://github.com/pytest-dev/pytest/issues/891&gt;`_: Remove ``testfunction.markername`` attributes - use ``Node.iter_markers(name=None)`` to iterate them.\n\n\n\nDeprecations\n------------\n\n- `3050 &lt;https://github.com/pytest-dev/pytest/issues/3050&gt;`_: Deprecated the ``pytest.config`` global.\n\n  See https://docs.pytest.org/en/latest/deprecations.htmlpytest-config-global for rationale.\n\n\n- `3974 &lt;https://github.com/pytest-dev/pytest/issues/3974&gt;`_: Passing the ``message`` parameter of ``pytest.raises`` now issues a ``DeprecationWarning``.\n\n  It is a common mistake to think this parameter will match the exception message, while in fact\n  it only serves to provide a custom message in case the ``pytest.raises`` check fails. To avoid this\n  mistake and because it is believed to be little used, pytest is deprecating it without providing\n  an alternative for the moment.\n\n  If you have concerns about this, please comment on `issue 3974 &lt;https://github.com/pytest-dev/pytest/issues/3974&gt;`__.\n\n\n- `4435 &lt;https://github.com/pytest-dev/pytest/issues/4435&gt;`_: Deprecated ``raises(..., &#39;code(as_a_string)&#39;)`` and ``warns(..., &#39;code(as_a_string)&#39;)``.\n\n  See https://docs.pytest.org/en/latest/deprecations.htmlraises-warns-exec for rationale and examples.\n\n\n\nFeatures\n--------\n\n- `3191 &lt;https://github.com/pytest-dev/pytest/issues/3191&gt;`_: A warning is now issued when assertions are made for ``None``.\n\n  This is a common source of confusion among new users, which write:\n\n  .. code-block:: python\n\n      assert mocked_object.assert_called_with(3, 4, 5, key=&quot;value&quot;)\n\n  When they should write:\n\n  .. code-block:: python\n\n      mocked_object.assert_called_with(3, 4, 5, key=&quot;value&quot;)\n\n  Because the ``assert_called_with`` method of mock objects already executes an assertion.\n\n  This warning will not be issued when ``None`` is explicitly checked. An assertion like:\n\n  .. code-block:: python\n\n      assert variable is None\n\n  will not issue the warning.\n\n\n- `3632 &lt;https://github.com/pytest-dev/pytest/issues/3632&gt;`_: Richer equality comparison introspection on ``AssertionError`` for objects created using `attrs &lt;http://www.attrs.org/en/stable/&gt;`__ or `dataclasses &lt;https://docs.python.org/3/library/dataclasses.html&gt;`_ (Python 3.7+, `backported to 3.6 &lt;https://pypi.org/project/dataclasses&gt;`__).\n\n\n- `4278 &lt;https://github.com/pytest-dev/pytest/issues/4278&gt;`_: ``CACHEDIR.TAG`` files are now created inside cache directories.\n\n  Those files are part of the `Cache Directory Tagging Standard &lt;http://www.bford.info/cachedir/spec.html&gt;`__, and can\n  be used by backup or synchronization programs to identify pytest&#39;s cache directory as such.\n\n\n- `4292 &lt;https://github.com/pytest-dev/pytest/issues/4292&gt;`_: ``pytest.outcomes.Exit`` is derived from ``SystemExit`` instead of ``KeyboardInterrupt``. This allows us to better handle ``pdb`` exiting.\n\n\n- `4371 &lt;https://github.com/pytest-dev/pytest/issues/4371&gt;`_: Updated the ``--collect-only`` option to display test descriptions when ran using ``--verbose``.\n\n\n- `4386 &lt;https://github.com/pytest-dev/pytest/issues/4386&gt;`_: Restructured ``ExceptionInfo`` object construction and ensure incomplete instances have a ``repr``/``str``.\n\n\n- `4416 &lt;https://github.com/pytest-dev/pytest/issues/4416&gt;`_: pdb: added support for keyword arguments with ``pdb.set_trace``.\n\n  It handles ``header`` similar to Python 3.7 does it, and forwards any\n  other keyword arguments to the ``Pdb`` constructor.\n\n  This allows for ``__import__(&quot;pdb&quot;).set_trace(skip=[&quot;foo.*&quot;])``.\n\n\n- `4483 &lt;https://github.com/pytest-dev/pytest/issues/4483&gt;`_: Added ini parameter ``junit_duration_report`` to optionally report test call durations, excluding setup and teardown times.\n\n  The JUnit XML specification and the default pytest behavior is to include setup and teardown times in the test duration\n  report. You can include just the call durations instead (excluding setup and teardown) by adding this to your ``pytest.ini`` file:\n\n  .. code-block:: ini\n\n      [pytest]\n      junit_duration_report = call\n\n\n- `4532 &lt;https://github.com/pytest-dev/pytest/issues/4532&gt;`_: ``-ra`` now will show errors and failures last, instead of as the first items in the summary.\n\n  This makes it easier to obtain a list of errors and failures to run tests selectively.\n\n\n- `4599 &lt;https://github.com/pytest-dev/pytest/issues/4599&gt;`_: ``pytest.importorskip`` now supports a ``reason`` parameter, which will be shown when the\n  requested module cannot be imported.\n\n\n\nBug Fixes\n---------\n\n- `3532 &lt;https://github.com/pytest-dev/pytest/issues/3532&gt;`_: ``-p`` now accepts its argument without a space between the value, for example ``-pmyplugin``.\n\n\n- `4327 &lt;https://github.com/pytest-dev/pytest/issues/4327&gt;`_: ``approx`` again works with more generic containers, more precisely instances of ``Iterable`` and ``Sized`` instead of more restrictive ``Sequence``.\n\n\n- `4397 &lt;https://github.com/pytest-dev/pytest/issues/4397&gt;`_: Ensure that node ids are printable.\n\n\n- `4435 &lt;https://github.com/pytest-dev/pytest/issues/4435&gt;`_: Fixed ``raises(..., &#39;code(string)&#39;)`` frame filename.\n\n\n- `4458 &lt;https://github.com/pytest-dev/pytest/issues/4458&gt;`_: Display actual test ids in ``--collect-only``.\n\n\n\nImproved Documentation\n----------------------\n\n- `4557 &lt;https://github.com/pytest-dev/pytest/issues/4557&gt;`_: Markers example documentation page updated to support latest pytest version.\n\n\n- `4558 &lt;https://github.com/pytest-dev/pytest/issues/4558&gt;`_: Update cache documentation example to correctly show cache hit and miss.\n\n\n- `4580 &lt;https://github.com/pytest-dev/pytest/issues/4580&gt;`_: Improved detailed summary report documentation.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4447 &lt;https://github.com/pytest-dev/pytest/issues/4447&gt;`_: Changed the deprecation type of ``--result-log`` to ``PytestDeprecationWarning``.\n\n  It was decided to remove this feature at the next major revision.\n   ```\n   \n  \n  \n   ### 4.0.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `4265 &lt;https://github.com/pytest-dev/pytest/issues/4265&gt;`_: Validate arguments from the ``PYTEST_ADDOPTS`` environment variable and the ``addopts`` ini option separately.\n\n\n- `4435 &lt;https://github.com/pytest-dev/pytest/issues/4435&gt;`_: Fix ``raises(..., &#39;code(string)&#39;)`` frame filename.\n\n\n- `4500 &lt;https://github.com/pytest-dev/pytest/issues/4500&gt;`_: When a fixture yields and a log call is made after the test runs, and, if the test is interrupted, capture attributes are ``None``.\n\n\n- `4538 &lt;https://github.com/pytest-dev/pytest/issues/4538&gt;`_: Raise ``TypeError`` for ``with raises(..., match=&lt;non-None falsey value&gt;)``.\n\n\n\nImproved Documentation\n----------------------\n\n- `1495 &lt;https://github.com/pytest-dev/pytest/issues/1495&gt;`_: Document common doctest fixture directory tree structure pitfalls\n   ```\n   \n  \n  \n   ### 4.0.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3952 &lt;https://github.com/pytest-dev/pytest/issues/3952&gt;`_: Display warnings before &quot;short test summary info&quot; again, but still later warnings in the end.\n\n\n- `4386 &lt;https://github.com/pytest-dev/pytest/issues/4386&gt;`_: Handle uninitialized exceptioninfo in repr/str.\n\n\n- `4393 &lt;https://github.com/pytest-dev/pytest/issues/4393&gt;`_: Do not create ``.gitignore``/``README.md`` files in existing cache directories.\n\n\n- `4400 &lt;https://github.com/pytest-dev/pytest/issues/4400&gt;`_: Rearrange warning handling for the yield test errors so the opt-out in 4.0.x correctly works.\n\n\n- `4405 &lt;https://github.com/pytest-dev/pytest/issues/4405&gt;`_: Fix collection of testpaths with ``--pyargs``.\n\n\n- `4412 &lt;https://github.com/pytest-dev/pytest/issues/4412&gt;`_: Fix assertion rewriting involving ``Starred`` + side-effects.\n\n\n- `4425 &lt;https://github.com/pytest-dev/pytest/issues/4425&gt;`_: Ensure we resolve the absolute path when the given ``--basetemp`` is a relative path.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4315 &lt;https://github.com/pytest-dev/pytest/issues/4315&gt;`_: Use ``pkg_resources.parse_version`` instead of ``LooseVersion`` in minversion check.\n\n\n- `4440 &lt;https://github.com/pytest-dev/pytest/issues/4440&gt;`_: Adjust the stack level of some internal pytest warnings.\n   ```\n   \n  \n  \n   ### 4.0.0\n   ```\n   =========================\n\nRemovals\n--------\n\n- `3737 &lt;https://github.com/pytest-dev/pytest/issues/3737&gt;`_: **RemovedInPytest4Warnings 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 ``RemovedInPytest4Warnings`` now generate errors\n  instead of warning messages.\n\n  **The affected features will be effectively removed in pytest 4.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 ``4.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.RemovedInPytest4Warning\n\n  But this will stop working when pytest ``4.1`` is released.\n\n  **If you have concerns** about the removal of a specific feature, please add a\n  comment to `4348 &lt;https://github.com/pytest-dev/pytest/issues/4348&gt;`__.\n\n\n- `4358 &lt;https://github.com/pytest-dev/pytest/issues/4358&gt;`_: Remove the ``::()`` notation to denote a test class instance in node ids.\n\n  Previously, node ids that contain test instances would use ``::()`` to denote the instance like this::\n\n      test_foo.py::Test::()::test_bar\n\n  The extra ``::()`` was puzzling to most users and has been removed, so that the test id becomes now::\n\n      test_foo.py::Test::test_bar\n\n  This change could not accompany a deprecation period as is usual when user-facing functionality changes because\n  it was not really possible to detect when the functionality was being used explicitly.\n\n  The extra ``::()`` might have been removed in some places internally already,\n  which then led to confusion in places where it was expected, e.g. with\n  ``--deselect`` (`4127 &lt;https://github.com/pytest-dev/pytest/issues/4127&gt;`_).\n\n  Test class instances are also not listed with ``--collect-only`` anymore.\n\n\n\nFeatures\n--------\n\n- `4270 &lt;https://github.com/pytest-dev/pytest/issues/4270&gt;`_: The ``cache_dir`` option uses ``$TOX_ENV_DIR`` as prefix (if set in the environment).\n\n  This uses a different cache per tox environment by default.\n\n\n\nBug Fixes\n---------\n\n- `3554 &lt;https://github.com/pytest-dev/pytest/issues/3554&gt;`_: Fix ``CallInfo.__repr__`` for when the call is not finished yet.\n   ```\n   \n  \n  \n   ### 3.10.1\n   ```\n   ==========================\n\nBug Fixes\n---------\n\n- `4287 &lt;https://github.com/pytest-dev/pytest/issues/4287&gt;`_: Fix nested usage of debugging plugin (pdb), e.g. with pytester&#39;s ``testdir.runpytest``.\n\n\n- `4304 &lt;https://github.com/pytest-dev/pytest/issues/4304&gt;`_: Block the ``stepwise`` plugin if ``cacheprovider`` is also blocked, as one depends on the other.\n\n\n- `4306 &lt;https://github.com/pytest-dev/pytest/issues/4306&gt;`_: Parse ``minversion`` as an actual version and not as dot-separated strings.\n\n\n- `4310 &lt;https://github.com/pytest-dev/pytest/issues/4310&gt;`_: Fix duplicate collection due to multiple args matching the same packages.\n\n\n- `4321 &lt;https://github.com/pytest-dev/pytest/issues/4321&gt;`_: Fix ``item.nodeid`` with resolved symlinks.\n\n\n- `4325 &lt;https://github.com/pytest-dev/pytest/issues/4325&gt;`_: Fix collection of direct symlinked files, where the target does not match ``python_files``.\n\n\n- `4329 &lt;https://github.com/pytest-dev/pytest/issues/4329&gt;`_: Fix TypeError in report_collect with _collect_report_last_write.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4305 &lt;https://github.com/pytest-dev/pytest/issues/4305&gt;`_: Replace byte/unicode helpers in test_capture with python level syntax.\n   ```\n   \n  \n  \n   ### 3.10.0\n   ```\n   ==========================\n\nFeatures\n--------\n\n- `2619 &lt;https://github.com/pytest-dev/pytest/issues/2619&gt;`_: Resume capturing output after ``continue`` with ``__import__(&quot;pdb&quot;).set_trace()``.\n\n  This also adds a new ``pytest_leave_pdb`` hook, and passes in ``pdb`` to the\n  existing ``pytest_enter_pdb`` hook.\n\n\n- `4147 &lt;https://github.com/pytest-dev/pytest/issues/4147&gt;`_: Add ``--sw``, ``--stepwise`` as an alternative to ``--lf -x`` for stopping at the first failure, but starting the next test invocation from that test.  See `the documentation &lt;https://docs.pytest.org/en/latest/cache.htmlstepwise&gt;`__ for more info.\n\n\n- `4188 &lt;https://github.com/pytest-dev/pytest/issues/4188&gt;`_: Make ``--color`` emit colorful dots when not running in verbose mode. Earlier, it would only colorize the test-by-test output if ``--verbose`` was also passed.\n\n\n- `4225 &lt;https://github.com/pytest-dev/pytest/issues/4225&gt;`_: Improve performance with collection reporting in non-quiet mode with terminals.\n\n  The &quot;collecting …&quot; message is only printed/updated every 0.5s.\n\n\n\nBug Fixes\n---------\n\n- `2701 &lt;https://github.com/pytest-dev/pytest/issues/2701&gt;`_: Fix false ``RemovedInPytest4Warning: usage of Session... is deprecated, please use pytest`` warnings.\n\n\n- `4046 &lt;https://github.com/pytest-dev/pytest/issues/4046&gt;`_: Fix problems with running tests in package ``__init__.py`` files.\n\n\n- `4260 &lt;https://github.com/pytest-dev/pytest/issues/4260&gt;`_: Swallow warnings during anonymous compilation of source.\n\n\n- `4262 &lt;https://github.com/pytest-dev/pytest/issues/4262&gt;`_: Fix access denied error when deleting stale directories created by ``tmpdir`` / ``tmp_path``.\n\n\n- `611 &lt;https://github.com/pytest-dev/pytest/issues/611&gt;`_: Naming a fixture ``request`` will now raise a warning: the ``request`` fixture is internal and\n  should not be overwritten as it will lead to internal errors.\n\n- `4266 &lt;https://github.com/pytest-dev/pytest/issues/4266&gt;`_: Handle (ignore) exceptions raised during collection, e.g. with Django&#39;s LazySettings proxy class.\n\n\n\nImproved Documentation\n----------------------\n\n- `4255 &lt;https://github.com/pytest-dev/pytest/issues/4255&gt;`_: Added missing documentation about the fact that module names passed to filter warnings are not regex-escaped.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4272 &lt;https://github.com/pytest-dev/pytest/issues/4272&gt;`_: Display cachedir also in non-verbose mode if non-default.\n\n\n- `4277 &lt;https://github.com/pytest-dev/pytest/issues/4277&gt;`_: pdb: improve message about output capturing with ``set_trace``.\n\n  Do not display &quot;IO-capturing turned off/on&quot; when ``-s`` is used to avoid\n  confusion.\n\n\n- `4279 &lt;https://github.com/pytest-dev/pytest/issues/4279&gt;`_: Improve message and stack level of warnings issued by ``monkeypatch.setenv`` when the value of the environment variable is not a ``str``.\n   ```\n   \n  \n  \n   ### 3.9.3\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `4174 &lt;https://github.com/pytest-dev/pytest/issues/4174&gt;`_: Fix &quot;ValueError: Plugin already registered&quot; with conftest plugins via symlink.\n\n\n- `4181 &lt;https://github.com/pytest-dev/pytest/issues/4181&gt;`_: Handle race condition between creation and deletion of temporary folders.\n\n\n- `4221 &lt;https://github.com/pytest-dev/pytest/issues/4221&gt;`_: Fix bug where the warning summary at the end of the test session was not showing the test where the warning was originated.\n\n\n- `4243 &lt;https://github.com/pytest-dev/pytest/issues/4243&gt;`_: Fix regression when ``stacklevel`` for warnings was passed as positional argument on python2.\n\n\n\nImproved Documentation\n----------------------\n\n- `3851 &lt;https://github.com/pytest-dev/pytest/issues/3851&gt;`_: Add reference to ``empty_parameter_set_mark`` ini option in documentation of ``pytest.mark.parametrize``\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `4028 &lt;https://github.com/pytest-dev/pytest/issues/4028&gt;`_: Revert patching of ``sys.breakpointhook`` since it appears to do nothing.\n\n\n- `4233 &lt;https://github.com/pytest-dev/pytest/issues/4233&gt;`_: Apply an import sorter (``reorder-python-imports``) to the codebase.\n\n\n- `4248 &lt;https://github.com/pytest-dev/pytest/issues/4248&gt;`_: Remove use of unnecessary compat shim, six.binary_type\n   ```\n   \n  \n  \n   ### 3.9.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `2909 &lt;https://github.com/pytest-dev/pytest/issues/2909&gt;`_: Improve error message when a recursive dependency between fixtures is detected.\n\n\n- `3340 &lt;https://github.com/pytest-dev/pytest/issues/3340&gt;`_: Fix logging messages not shown in hooks ``pytest_sessionstart()`` and ``pytest_sessionfinish()``.\n\n\n- `3533 &lt;https://github.com/pytest-dev/pytest/issues/3533&gt;`_: Fix unescaped XML raw objects in JUnit report for skipped tests\n\n\n- `3691 &lt;https://github.com/pytest-dev/pytest/issues/3691&gt;`_: Python 2: safely format warning message about passing unicode strings to ``warnings.warn``, which may cause\n  surprising ``MemoryError`` exception when monkey patching ``warnings.warn`` itself.\n\n\n- `4026 &lt;https://github.com/pytest-dev/pytest/issues/4026&gt;`_: Improve error message when it is not possible to determine a function&#39;s signature.\n\n\n- `4177 &lt;https://github.com/pytest-dev/pytest/issues/4177&gt;`_: Pin ``setuptools&gt;=40.0`` to support ``py_modules`` in ``setup.cfg``\n\n\n- `4179 &lt;https://github.com/pytest-dev/pytest/issues/4179&gt;`_: Restore the tmpdir behaviour of symlinking the current test run.\n\n\n- `4192 &lt;https://github.com/pytest-dev/pytest/issues/4192&gt;`_: Fix filename reported by ``warnings.warn`` when using ``recwarn`` under python2.\n   ```\n   \n  \n  \n   ### 3.9.1\n   ```\n   =========================\n\nFeatures\n--------\n\n- `4159 &lt;https://github.com/pytest-dev/pytest/issues/4159&gt;`_: For test-suites containing test classes, the information about the subclassed\n  module is now output only if a higher verbosity level is specified (at least\n  &quot;-vv&quot;).\n   ```\n   \n  \n  \n   ### 3.9.0\n   ```\n   =========================================================================\n\nDeprecations\n------------\n\n- `3616 &lt;https://github.com/pytest-dev/pytest/issues/3616&gt;`_: The following accesses have been documented as deprecated for years, but are now actually emitting deprecation warnings.\n\n  * Access of ``Module``, ``Function``, ``Class``, ``Instance``, ``File`` and ``Item`` through ``Node`` instances. Now\n    users will this warning::\n\n          usage of Function.Module is deprecated, please use pytest.Module instead\n\n    Users should just ``import pytest`` and access those objects using the ``pytest`` module.\n\n  * ``request.cached_setup``, this was the precursor of the setup/teardown mechanism available to fixtures. You can\n    consult `funcarg comparison section in the docs &lt;https://docs.pytest.org/en/latest/funcarg_compare.html&gt;`_.\n\n  * Using objects named ``&quot;Class&quot;`` as a way to customize the type of nodes that are collected in ``Collector``\n    subclasses has been deprecated. Users instead should use ``pytest_collect_make_item`` to customize node types during\n    collection.\n\n    This issue should affect only advanced plugins who create new collection types, so if you see this warning\n    message please contact the authors so they can change the code.\n\n  * The warning that produces the message below has changed to ``RemovedInPytest4Warning``::\n\n          getfuncargvalue is deprecated, use getfixturevalue\n\n\n- `3988 &lt;https://github.com/pytest-dev/pytest/issues/3988&gt;`_: Add a Deprecation warning for pytest.ensuretemp as it was deprecated since a while.\n\n\n\nFeatures\n--------\n\n- `2293 &lt;https://github.com/pytest-dev/pytest/issues/2293&gt;`_: Improve usage errors messages by hiding internal details which can be distracting and noisy.\n\n  This has the side effect that some error conditions that previously raised generic errors (such as\n  ``ValueError`` for unregistered marks) are now raising ``Failed`` exceptions.\n\n\n- `3332 &lt;https://github.com/pytest-dev/pytest/issues/3332&gt;`_: Improve the error displayed when a ``conftest.py`` file could not be imported.\n\n  In order to implement this, a new ``chain`` parameter was added to ``ExceptionInfo.getrepr``\n  to show or hide chained tracebacks in Python 3 (defaults to ``True``).\n\n\n- `3849 &lt;https://github.com/pytest-dev/pytest/issues/3849&gt;`_: Add ``empty_parameter_set_mark=fail_at_collect`` ini option for raising an exception when parametrize collects an empty set.\n\n\n- `3964 &lt;https://github.com/pytest-dev/pytest/issues/3964&gt;`_: Log messages generated in the collection phase are shown when\n  live-logging is enabled and/or when they are logged to a file.\n\n\n- `3985 &lt;https://github.com/pytest-dev/pytest/issues/3985&gt;`_: Introduce ``tmp_path`` as a fixture providing a Path object.\n\n\n- `4013 &lt;https://github.com/pytest-dev/pytest/issues/4013&gt;`_: Deprecation warnings are now shown even if you customize the warnings filters yourself. In the previous version\n  any customization would override pytest&#39;s filters and deprecation warnings would fall back to being hidden by default.\n\n\n- `4073 &lt;https://github.com/pytest-dev/pytest/issues/4073&gt;`_: Allow specification of timeout for ``Testdir.runpytest_subprocess()`` and ``Testdir.run()``.\n\n\n- `4098 &lt;https://github.com/pytest-dev/pytest/issues/4098&gt;`_: Add returncode argument to pytest.exit() to exit pytest with a specific return code.\n\n\n- `4102 &lt;https://github.com/pytest-dev/pytest/issues/4102&gt;`_: Reimplement ``pytest.deprecated_call`` using ``pytest.warns`` so it supports the ``match=&#39;...&#39;`` keyword argument.\n\n  This has the side effect that ``pytest.deprecated_call`` now raises ``pytest.fail.Exception`` instead\n  of ``AssertionError``.\n\n\n- `4149 &lt;https://github.com/pytest-dev/pytest/issues/4149&gt;`_: Require setuptools&gt;=30.3 and move most of the metadata to ``setup.cfg``.\n\n\n\nBug Fixes\n---------\n\n- `2535 &lt;https://github.com/pytest-dev/pytest/issues/2535&gt;`_: Improve error message when test functions of ``unittest.TestCase`` subclasses use a parametrized fixture.\n\n\n- `3057 &lt;https://github.com/pytest-dev/pytest/issues/3057&gt;`_: ``request.fixturenames`` now correctly returns the name of fixtures created by ``request.getfixturevalue()``.\n\n\n- `3946 &lt;https://github.com/pytest-dev/pytest/issues/3946&gt;`_: Warning filters passed as command line options using ``-W`` now take precedence over filters defined in ``ini``\n  configuration files.\n\n\n- `4066 &lt;https://github.com/pytest-dev/pytest/issues/4066&gt;`_: Fix source reindenting by using ``textwrap.dedent`` directly.\n\n\n- `4102 &lt;https://github.com/pytest-dev/pytest/issues/4102&gt;`_: ``pytest.warn`` will capture previously-warned warnings in Python 2. Previously they were never raised.\n\n\n- `4108 &lt;https://github.com/pytest-dev/pytest/issues/4108&gt;`_: Resolve symbolic links for args.\n\n  This fixes running ``pytest tests/test_foo.py::test_bar``, where ``tests``\n  is a symlink to ``project/app/tests``:\n  previously ``project/app/conftest.py`` would be ignored for fixtures then.\n\n\n- `4132 &lt;https://github.com/pytest-dev/pytest/issues/4132&gt;`_: Fix duplicate printing of internal errors when using ``--pdb``.\n\n\n- `4135 &lt;https://github.com/pytest-dev/pytest/issues/4135&gt;`_: pathlib based tmpdir cleanup now correctly handles symlinks in the folder.\n\n\n- `4152 &lt;https://github.com/pytest-dev/pytest/issues/4152&gt;`_: Display the filename when encountering ``SyntaxWarning``.\n\n\n\nImproved Documentation\n----------------------\n\n- `3713 &lt;https://github.com/pytest-dev/pytest/issues/3713&gt;`_: Update usefixtures documentation to clarify that it can&#39;t be used with fixture functions.\n\n\n- `4058 &lt;https://github.com/pytest-dev/pytest/issues/4058&gt;`_: Update fixture documentation to specify that a fixture can be invoked twice in the scope it&#39;s defined for.\n\n\n- `4064 &lt;https://github.com/pytest-dev/pytest/issues/4064&gt;`_: According to unittest.rst, setUpModule and tearDownModule were not implemented, but it turns out they are. So updated the documentation for unittest.\n\n\n- `4151 &lt;https://github.com/pytest-dev/pytest/issues/4151&gt;`_: Add tempir testing example to CONTRIBUTING.rst guide\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `2293 &lt;https://github.com/pytest-dev/pytest/issues/2293&gt;`_: The internal ``MarkerError`` exception has been removed.\n\n\n- `3988 &lt;https://github.com/pytest-dev/pytest/issues/3988&gt;`_: Port the implementation of tmpdir to pathlib.\n\n\n- `4063 &lt;https://github.com/pytest-dev/pytest/issues/4063&gt;`_: Exclude 0.00 second entries from ``--duration`` output unless ``-vv`` is passed on the command-line.\n\n\n- `4093 &lt;https://github.com/pytest-dev/pytest/issues/4093&gt;`_: Fixed formatting of string literals in internal tests.\n   ```\n   \n  \n  \n   ### 3.8.2\n   ```\n   =========================\n\nDeprecations and Removals\n-------------------------\n\n- `4036 &lt;https://github.com/pytest-dev/pytest/issues/4036&gt;`_: The ``item`` parameter of ``pytest_warning_captured`` hook is now documented as deprecated. We realized only after\n  the ``3.8`` release that this parameter is incompatible with ``pytest-xdist``.\n\n  Our policy is to not deprecate features during bugfix releases, but in this case we believe it makes sense as we are\n  only documenting it as deprecated, without issuing warnings which might potentially break test suites. This will get\n  the word out that hook implementers should not use this parameter at all.\n\n  In a future release ``item`` will always be ``None`` and will emit a proper warning when a hook implementation\n  makes use of it.\n\n\n\nBug Fixes\n---------\n\n- `3539 &lt;https://github.com/pytest-dev/pytest/issues/3539&gt;`_: Fix reload on assertion rewritten modules.\n\n\n- `4034 &lt;https://github.com/pytest-dev/pytest/issues/4034&gt;`_: The ``.user_properties`` attribute of ``TestReport`` objects is a list\n  of (name, value) tuples, but could sometimes be instantiated as a tuple\n  of tuples.  It is now always a list.\n\n\n- `4039 &lt;https://github.com/pytest-dev/pytest/issues/4039&gt;`_: No longer issue warnings about using ``pytest_plugins`` in non-top-level directories when using ``--pyargs``: the\n  current ``--pyargs`` mechanism is not reliable and might give false negatives.\n\n\n- `4040 &lt;https://github.com/pytest-dev/pytest/issues/4040&gt;`_: Exclude empty reports for passed tests when ``-rP`` option is used.\n\n\n- `4051 &lt;https://github.com/pytest-dev/pytest/issues/4051&gt;`_: Improve error message when an invalid Python expression is passed to the ``-m`` option.\n\n\n- `4056 &lt;https://github.com/pytest-dev/pytest/issues/4056&gt;`_: ``MonkeyPatch.setenv`` and ``MonkeyPatch.delenv`` issue a warning if the environment variable name is not ``str`` on Python 2.\n\n  In Python 2, adding ``unicode`` keys to ``os.environ`` causes problems with ``subprocess`` (and possible other modules),\n  making this a subtle bug specially susceptible when used with ``from __future__ import unicode_literals``.\n\n\n\nImproved Documentation\n----------------------\n\n- `3928 &lt;https://github.com/pytest-dev/pytest/issues/3928&gt;`_: Add possible values for fixture scope to docs.\n   ```\n   \n  \n  \n   ### 3.8.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3286 &lt;https://github.com/pytest-dev/pytest/issues/3286&gt;`_: ``.pytest_cache`` directory is now automatically ignored by Git. Users who would like to contribute a solution for other SCMs please consult/comment on this issue.\n\n\n- `3749 &lt;https://github.com/pytest-dev/pytest/issues/3749&gt;`_: Fix the following error during collection of tests inside packages::\n\n      TypeError: object of type &#39;Package&#39; has no len()\n\n\n- `3941 &lt;https://github.com/pytest-dev/pytest/issues/3941&gt;`_: Fix bug where indirect parametrization would consider the scope of all fixtures used by the test function to determine the parametrization scope, and not only the scope of the fixtures being parametrized.\n\n\n- `3973 &lt;https://github.com/pytest-dev/pytest/issues/3973&gt;`_: Fix crash of the assertion rewriter if a test changed the current working directory without restoring it afterwards.\n\n\n- `3998 &lt;https://github.com/pytest-dev/pytest/issues/3998&gt;`_: Fix issue that prevented some caplog properties (for example ``record_tuples``) from being available when entering the debugger with ``--pdb``.\n\n\n- `3999 &lt;https://github.com/pytest-dev/pytest/issues/3999&gt;`_: Fix ``UnicodeDecodeError`` in python2.x when a class returns a non-ascii binary ``__repr__`` in an assertion which also contains non-ascii text.\n\n\n\nImproved Documentation\n----------------------\n\n- `3996 &lt;https://github.com/pytest-dev/pytest/issues/3996&gt;`_: New `Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`_ page shows all currently\n  deprecated features, the rationale to do so, and alternatives to update your code. It also list features removed\n  from pytest in past major releases to help those with ancient pytest versions to upgrade.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `3955 &lt;https://github.com/pytest-dev/pytest/issues/3955&gt;`_: Improve pre-commit detection for changelog filenames\n\n\n- `3975 &lt;https://github.com/pytest-dev/pytest/issues/3975&gt;`_: Remove legacy code around im_func as that was python2 only\n   ```\n   \n  \n  \n   ### 3.8.0\n   ```\n   =========================\n\nDeprecations and Removals\n-------------------------\n\n- `2452 &lt;https://github.com/pytest-dev/pytest/issues/2452&gt;`_: ``Config.warn`` and ``Node.warn`` have been\n  deprecated, see `&lt;https://docs.pytest.org/en/latest/deprecations.htmlconfig-warn-and-node-warn&gt;`_ for rationale and\n  examples.\n\n- `3936 &lt;https://github.com/pytest-dev/pytest/issues/3936&gt;`_: ``pytest.mark.filterwarnings`` second parameter is no longer regex-escaped,\n  making it possible to actually use regular expressions to check the warning message.\n\n  **Note**: regex-escaping the match string was an implementation oversight that might break test suites which depend\n  on the old behavior.\n\n\n\nFeatures\n--------\n\n- `2452 &lt;https://github.com/pytest-dev/pytest/issues/2452&gt;`_: Internal pytest warnings are now issued using the standard ``warnings`` module, making it possible to use\n  the standard warnings filters to manage those warnings. This introduces ``PytestWarning``,\n  ``PytestDeprecationWarning`` and ``RemovedInPytest4Warning`` warning types as part of the public API.\n\n  Consult `the documentation &lt;https://docs.pytest.org/en/latest/warnings.htmlinternal-pytest-warnings&gt;`__ for more info.\n\n\n- `2908 &lt;https://github.com/pytest-dev/pytest/issues/2908&gt;`_: ``DeprecationWarning`` and ``PendingDeprecationWarning`` are now shown by default if no other warning filter is\n  configured. This makes pytest more compliant with\n  `PEP-0506 &lt;https://www.python.org/dev/peps/pep-0565/recommended-filter-settings-for-test-runners&gt;`_. See\n  `the docs &lt;https://docs.pytest.org/en/latest/warnings.htmldeprecationwarning-and-pendingdeprecationwarning&gt;`_ for\n  more info.\n\n\n- `3251 &lt;https://github.com/pytest-dev/pytest/issues/3251&gt;`_: Warnings are now captured and displayed during test collection.\n\n\n- `3784 &lt;https://github.com/pytest-dev/pytest/issues/3784&gt;`_: ``PYTEST_DISABLE_PLUGIN_AUTOLOAD`` environment variable disables plugin auto-loading when set.\n\n\n- `3829 &lt;https://github.com/pytest-dev/pytest/issues/3829&gt;`_: Added the ``count`` option to ``console_output_style`` to enable displaying the progress as a count instead of a percentage.\n\n\n- `3837 &lt;https://github.com/pytest-dev/pytest/issues/3837&gt;`_: Added support for &#39;xfailed&#39; and &#39;xpassed&#39; outcomes to the ``pytester.RunResult.assert_outcomes`` signature.\n\n\n\nBug Fixes\n---------\n\n- `3911 &lt;https://github.com/pytest-dev/pytest/issues/3911&gt;`_: Terminal writer now takes into account unicode character width when writing out progress.\n\n\n- `3913 &lt;https://github.com/pytest-dev/pytest/issues/3913&gt;`_: Pytest now returns with correct exit code (EXIT_USAGEERROR, 4) when called with unknown arguments.\n\n\n- `3918 &lt;https://github.com/pytest-dev/pytest/issues/3918&gt;`_: Improve performance of assertion rewriting.\n\n\n\nImproved Documentation\n----------------------\n\n- `3566 &lt;https://github.com/pytest-dev/pytest/issues/3566&gt;`_: Added a blurb in usage.rst for the usage of -r flag which is used to show an extra test summary info.\n\n\n- `3907 &lt;https://github.com/pytest-dev/pytest/issues/3907&gt;`_: Corrected type of the exceptions collection passed to ``xfail``: ``raises`` argument accepts a ``tuple`` instead of ``list``.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `3853 &lt;https://github.com/pytest-dev/pytest/issues/3853&gt;`_: Removed ``&quot;run all (no recorded failures)&quot;`` message printed with ``--failed-first`` and ``--last-failed`` when there are no failed tests.\n   ```\n   \n  \n  \n   ### 3.7.4\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3506 &lt;https://github.com/pytest-dev/pytest/issues/3506&gt;`_: Fix possible infinite recursion when writing ``.pyc`` files.\n\n\n- `3853 &lt;https://github.com/pytest-dev/pytest/issues/3853&gt;`_: Cache plugin now obeys the ``-q`` flag when ``--last-failed`` and ``--failed-first`` flags are used.\n\n\n- `3883 &lt;https://github.com/pytest-dev/pytest/issues/3883&gt;`_: Fix bad console output when using ``console_output_style=classic``.\n\n\n- `3888 &lt;https://github.com/pytest-dev/pytest/issues/3888&gt;`_: Fix macOS specific code using ``capturemanager`` plugin in doctests.\n\n\n\nImproved Documentation\n----------------------\n\n- `3902 &lt;https://github.com/pytest-dev/pytest/issues/3902&gt;`_: Fix pytest.org links\n   ```\n   \n  \n  \n   ### 3.7.3\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3033 &lt;https://github.com/pytest-dev/pytest/issues/3033&gt;`_: Fixtures during teardown can again use ``capsys`` and ``capfd`` to inspect output captured during tests.\n\n\n- `3773 &lt;https://github.com/pytest-dev/pytest/issues/3773&gt;`_: Fix collection of tests from ``__init__.py`` files if they match the ``python_files`` configuration option.\n\n\n- `3796 &lt;https://github.com/pytest-dev/pytest/issues/3796&gt;`_: Fix issue where teardown of fixtures of consecutive sub-packages were executed once, at the end of the outer\n  package.\n\n\n- `3816 &lt;https://github.com/pytest-dev/pytest/issues/3816&gt;`_: Fix bug where ``--show-capture=no`` option would still show logs printed during fixture teardown.\n\n\n- `3819 &lt;https://github.com/pytest-dev/pytest/issues/3819&gt;`_: Fix ``stdout/stderr`` not getting captured when real-time cli logging is active.\n\n\n- `3843 &lt;https://github.com/pytest-dev/pytest/issues/3843&gt;`_: Fix collection error when specifying test functions directly in the command line using ``test.py::test`` syntax together with ``--doctest-modules``.\n\n\n- `3848 &lt;https://github.com/pytest-dev/pytest/issues/3848&gt;`_: Fix bugs where unicode arguments could not be passed to ``testdir.runpytest`` on Python 2.\n\n\n- `3854 &lt;https://github.com/pytest-dev/pytest/issues/3854&gt;`_: Fix double collection of tests within packages when the filename starts with a capital letter.\n\n\n\nImproved Documentation\n----------------------\n\n- `3824 &lt;https://github.com/pytest-dev/pytest/issues/3824&gt;`_: Added example for multiple glob pattern matches in ``python_files``.\n\n\n- `3833 &lt;https://github.com/pytest-dev/pytest/issues/3833&gt;`_: Added missing docs for ``pytester.Testdir``.\n\n\n- `3870 &lt;https://github.com/pytest-dev/pytest/issues/3870&gt;`_: Correct documentation for setuptools integration.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `3826 &lt;https://github.com/pytest-dev/pytest/issues/3826&gt;`_: Replace broken type annotations with type comments.\n\n\n- `3845 &lt;https://github.com/pytest-dev/pytest/issues/3845&gt;`_: Remove a reference to issue `568 &lt;https://github.com/pytest-dev/pytest/issues/568&gt;`_ from the documentation, which has since been\n  fixed.\n   ```\n   \n  \n  \n   ### 3.7.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3671 &lt;https://github.com/pytest-dev/pytest/issues/3671&gt;`_: Fix ``filterwarnings`` not being registered as a builtin mark.\n\n\n- `3768 &lt;https://github.com/pytest-dev/pytest/issues/3768&gt;`_, `3789 &lt;https://github.com/pytest-dev/pytest/issues/3789&gt;`_: Fix test collection from packages mixed with normal directories.\n\n\n- `3771 &lt;https://github.com/pytest-dev/pytest/issues/3771&gt;`_: Fix infinite recursion during collection if a ``pytest_ignore_collect`` hook returns ``False`` instead of ``None``.\n\n\n- `3774 &lt;https://github.com/pytest-dev/pytest/issues/3774&gt;`_: Fix bug where decorated fixtures would lose functionality (for example ``mock.patch``).\n\n\n- `3775 &lt;https://github.com/pytest-dev/pytest/issues/3775&gt;`_: Fix bug where importing modules or other objects with prefix ``pytest_`` prefix would raise a ``PluginValidationError``.\n\n\n- `3788 &lt;https://github.com/pytest-dev/pytest/issues/3788&gt;`_: Fix ``AttributeError`` during teardown of ``TestCase`` subclasses which raise an exception during ``__init__``.\n\n\n- `3804 &lt;https://github.com/pytest-dev/pytest/issues/3804&gt;`_: Fix traceback reporting for exceptions with ``__cause__`` cycles.\n\n\n\nImproved Documentation\n----------------------\n\n- `3746 &lt;https://github.com/pytest-dev/pytest/issues/3746&gt;`_: Add documentation for ``metafunc.config`` that had been mistakenly hidden.\n   ```\n   \n  \n  \n   ### 3.7.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- `3473 &lt;https://github.com/pytest-dev/pytest/issues/3473&gt;`_: Raise immediately if ``approx()`` is given an expected value of a type it doesn&#39;t understand (e.g. strings, nested dicts, etc.).\n\n\n- `3712 &lt;https://github.com/pytest-dev/pytest/issues/3712&gt;`_: Correctly represent the dimensions of a numpy array when calling ``repr()`` on ``approx()``.\n\n- `3742 &lt;https://github.com/pytest-dev/pytest/issues/3742&gt;`_: Fix incompatibility with third party plugins during collection, which produced the error ``object has no attribute &#39;_collectfile&#39;``.\n\n- `3745 &lt;https://github.com/pytest-dev/pytest/issues/3745&gt;`_: Display the absolute path if ``cache_dir`` is not relative to the ``rootdir`` instead of failing.\n\n\n- `3747 &lt;https://github.com/pytest-dev/pytest/issues/3747&gt;`_: Fix compatibility problem with plugins and the warning code issued by fixture functions when they are called directly.\n\n\n- `3748 &lt;https://github.com/pytest-dev/pytest/issues/3748&gt;`_: Fix infinite recursion in ``pytest.approx`` with arrays in ``numpy&lt;1.13``.\n\n\n- `3757 &lt;https://github.com/pytest-dev/pytest/issues/3757&gt;`_: Pin pathlib2 to ``&gt;=2.2.0`` as we require ``__fspath__`` support.\n\n\n- `3763 &lt;https://github.com/pytest-dev/pytest/issues/3763&gt;`_: Fix ``TypeError`` when the assertion message is ``bytes`` in python 3.\n   ```\n   \n  \n  \n   ### 3.7.0\n   ```\n   =========================\n\nDeprecations and Removals\n-------------------------\n\n- `2639 &lt;https://github.com/pytest-dev/pytest/issues/2639&gt;`_: ``pytest_namespace`` has been `deprecated &lt;https://docs.pytest.org/en/latest/deprecations.htmlpytest-namespace&gt;`_.\n\n\n- `3661 &lt;https://github.com/pytest-dev/pytest/issues/3661&gt;`_: Calling a fixture function directly, as opposed to request them in a test function, now issues a ``RemovedInPytest4Warning``. See `the documentation for rationale and examples &lt;https://docs.pytest.org/en/latest/deprecations.htmlcalling-fixtures-directly&gt;`_.\n\n\n\nFeatures\n--------\n\n- `2283 &lt;https://github.com/pytest-dev/pytest/issues/2283&gt;`_: New ``package`` fixture scope: fixtures are finalized when the last test of a *package* finishes. This feature is considered **experimental**, so use it sparingly.\n\n\n- `3576 &lt;https://github.com/pytest-dev/pytest/issues/3576&gt;`_: ``Node.add_marker`` now supports an ``append=True/False`` parameter to determine whether the mark comes last (default) or first.\n\n\n- `3579 &lt;https://github.com/pytest-dev/pytest/issues/3579&gt;`_: Fixture ``caplog`` now has a ``messages`` property, providing convenient access to the format-interpolated log messages without the extra data provided by the formatter/handler.\n\n\n- `3610 &lt;https://github.com/pytest-dev/pytest/issues/3610&gt;`_: New ``--trace`` option to enter the debugger at the start of a test.\n\n\n- `3623 &lt;https://github.com/pytest-dev/pytest/issues/3623&gt;`_: Introduce ``pytester.copy_example`` as helper to do acceptance tests against examples from the project.\n\n\n\nBug Fixes\n---------\n\n- `2220 &lt;https://github.com/pytest-dev/pytest/issues/2220&gt;`_: Fix a bug where fixtures overridden by direct parameters (for example parametrization) were being instantiated even if they were not being used by a test.\n\n\n- `3695 &lt;https://github.com/pytest-dev/pytest/issues/3695&gt;`_: Fix ``ApproxNumpy`` initialisation argument mixup, ``abs`` and ``rel`` tolerances were flipped causing strange comparsion results.\n  Add tests to check ``abs`` and ``rel`` tolerances for ``np.array`` and test for expecting ``nan`` with ``np.array()``\n\n\n- `980 &lt;https://github.com/pytest-dev/pytest/issues/980&gt;`_: Fix truncated locals output in verbose mode.\n\n\n\nImproved Documentation\n----------------------\n\n- `3295 &lt;https://github.com/pytest-dev/pytest/issues/3295&gt;`_: Correct the usage documentation of ``--last-failed-no-failures`` by adding the missing ``--last-failed`` argument in the presented examples, because they are misleading and lead to think that the missing argument is not needed.\n\n\n\nTrivial/Internal Changes\n------------------------\n\n- `3519 &lt;https://github.com/pytest-dev/pytest/issues/3519&gt;`_: Now a ``README.md`` file is created in ``.pytest_cache`` to make it clear why the directory exists.\n   ```\n   \n  \n  \n   ### 3.6.4\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- Invoke pytest using ``-mpytest`` so ``sys.path`` does not get polluted by packages installed in ``site-packages``. (`742 &lt;https://github.com/pytest-dev/pytest/issues/742&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Use ``smtp_connection`` instead of ``smtp`` in fixtures documentation to avoid possible confusion. (`3592 &lt;https://github.com/pytest-dev/pytest/issues/3592&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Remove obsolete ``__future__`` imports. (`2319 &lt;https://github.com/pytest-dev/pytest/issues/2319&gt;`_)\n\n- Add CITATION to provide information on how to formally cite pytest. (`3402 &lt;https://github.com/pytest-dev/pytest/issues/3402&gt;`_)\n\n- Replace broken type annotations with type comments. (`3635 &lt;https://github.com/pytest-dev/pytest/issues/3635&gt;`_)\n\n- Pin ``pluggy`` to ``&lt;0.8``. (`3727 &lt;https://github.com/pytest-dev/pytest/issues/3727&gt;`_)\n   ```\n   \n  \n  \n   ### 3.6.3\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- Fix ``ImportWarning`` triggered by explicit relative imports in\n  assertion-rewritten package modules. (`3061\n  &lt;https://github.com/pytest-dev/pytest/issues/3061&gt;`_)\n\n- Fix error in ``pytest.approx`` when dealing with 0-dimension numpy\n  arrays. (`3593 &lt;https://github.com/pytest-dev/pytest/issues/3593&gt;`_)\n\n- No longer raise ``ValueError`` when using the ``get_marker`` API. (`3605\n  &lt;https://github.com/pytest-dev/pytest/issues/3605&gt;`_)\n\n- Fix problem where log messages with non-ascii characters would not\n  appear in the output log file.\n  (`3630 &lt;https://github.com/pytest-dev/pytest/issues/3630&gt;`_)\n\n- No longer raise ``AttributeError`` when legacy marks can&#39;t be stored in\n  functions. (`3631 &lt;https://github.com/pytest-dev/pytest/issues/3631&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- The description above the example for ``pytest.mark.skipif`` now better\n  matches the code. (`3611\n  &lt;https://github.com/pytest-dev/pytest/issues/3611&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Internal refactoring: removed unused ``CallSpec2tox ._globalid_args``\n  attribute and ``metafunc`` parameter from ``CallSpec2.copy()``. (`3598\n  &lt;https://github.com/pytest-dev/pytest/issues/3598&gt;`_)\n\n- Silence usage of ``reduce`` warning in Python 2 (`3609\n  &lt;https://github.com/pytest-dev/pytest/issues/3609&gt;`_)\n\n- Fix usage of ``attr.ib`` deprecated ``convert`` parameter. (`3653\n  &lt;https://github.com/pytest-dev/pytest/issues/3653&gt;`_)\n   ```\n   \n  \n  \n   ### 3.6.2\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- Fix regression in ``Node.add_marker`` by extracting the mark object of a\n  ``MarkDecorator``. (`3555\n  &lt;https://github.com/pytest-dev/pytest/issues/3555&gt;`_)\n\n- Warnings without ``location`` were reported as ``None``. This is corrected to\n  now report ``&lt;undetermined location&gt;``. (`3563\n  &lt;https://github.com/pytest-dev/pytest/issues/3563&gt;`_)\n\n- Continue to call finalizers in the stack when a finalizer in a former scope\n  raises an exception. (`3569\n  &lt;https://github.com/pytest-dev/pytest/issues/3569&gt;`_)\n\n- Fix encoding error with ``print`` statements in doctests (`3583\n  &lt;https://github.com/pytest-dev/pytest/issues/3583&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Add documentation for the ``--strict`` flag. (`3549\n  &lt;https://github.com/pytest-dev/pytest/issues/3549&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Update old quotation style to parens in fixture.rst documentation. (`3525\n  &lt;https://github.com/pytest-dev/pytest/issues/3525&gt;`_)\n\n- Improve display of hint about ``--fulltrace`` with ``KeyboardInterrupt``.\n  (`3545 &lt;https://github.com/pytest-dev/pytest/issues/3545&gt;`_)\n\n- pytest&#39;s testsuite is no longer runnable through ``python setup.py test`` --\n  instead invoke ``pytest`` or ``tox`` directly. (`3552\n  &lt;https://github.com/pytest-dev/pytest/issues/3552&gt;`_)\n\n- Fix typo in documentation (`3567\n  &lt;https://github.com/pytest-dev/pytest/issues/3567&gt;`_)\n   ```\n   \n  \n  \n   ### 3.6.1\n   ```\n   =========================\n\nBug Fixes\n---------\n\n- Fixed a bug where stdout and stderr were logged twice by junitxml when a test\n  was marked xfail. (`3491\n  &lt;https://github.com/pytest-dev/pytest/issues/3491&gt;`_)\n\n- Fix ``usefixtures`` mark applyed to unittest tests by correctly instantiating\n  ``FixtureInfo``. (`3498\n  &lt;https://github.com/pytest-dev/pytest/issues/3498&gt;`_)\n\n- Fix assertion rewriter compatibility with libraries that monkey patch\n  ``file`` objects. (`3503\n  &lt;https://github.com/pytest-dev/pytest/issues/3503&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Added a section on how to use fixtures as factories to the fixture\n  documentation. (`3461 &lt;https://github.com/pytest-dev/pytest/issues/3461&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Enable caching for pip/pre-commit in order to reduce build time on\n  travis/appveyor. (`3502\n  &lt;https://github.com/pytest-dev/pytest/issues/3502&gt;`_)\n\n- Switch pytest to the src/ layout as we already suggested it for good practice\n  - now we implement it as well. (`3513\n  &lt;https://github.com/pytest-dev/pytest/issues/3513&gt;`_)\n\n- Fix if in tests to support 3.7.0b5, where a docstring handling in AST got\n  reverted. (`3530 &lt;https://github.com/pytest-dev/pytest/issues/3530&gt;`_)\n\n- Remove some python2.5 compatibility code. (`3529\n  &lt;https://github.com/pytest-dev/pytest/issues/3529&gt;`_)\n   ```\n   \n  \n  \n   ### 3.6.0\n   ```\n   =========================\n\nFeatures\n--------\n\n- Revamp the internals of the ``pytest.mark`` implementation with correct per\n  node handling which fixes a number of long standing bugs caused by the old\n  design. This introduces new ``Node.iter_markers(name)`` and\n  ``Node.get_closest_marker(name)`` APIs. Users are **strongly encouraged** to\n  read the `reasons for the revamp in the docs\n  &lt;https://docs.pytest.org/en/latest/mark.htmlmarker-revamp-and-iteration&gt;`_,\n  or jump over to details about `updating existing code to use the new APIs\n  &lt;https://docs.pytest.org/en/latest/mark.htmlupdating-code&gt;`_. (`3317\n  &lt;https://github.com/pytest-dev/pytest/issues/3317&gt;`_)\n\n- Now when ``pytest.fixture`` is applied more than once to the same function a\n  ``ValueError`` is raised. This buggy behavior would cause surprising problems\n  and if was working for a test suite it was mostly by accident. (`2334\n  &lt;https://github.com/pytest-dev/pytest/issues/2334&gt;`_)\n\n- Support for Python 3.7&#39;s builtin ``breakpoint()`` method, see `Using the\n  builtin breakpoint function\n  &lt;https://docs.pytest.org/en/latest/usage.htmlbreakpoint-builtin&gt;`_ for\n  details. (`3180 &lt;https://github.com/pytest-dev/pytest/issues/3180&gt;`_)\n\n- ``monkeypatch`` now supports a ``context()`` function which acts as a context\n  manager which undoes all patching done within the ``with`` block. (`3290\n  &lt;https://github.com/pytest-dev/pytest/issues/3290&gt;`_)\n\n- The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger,\n  instead of stopping the test session. On python 2.7, hitting CTRL+C again\n  exits the debugger. On python 3.2 and higher, use CTRL+D. (`3299\n  &lt;https://github.com/pytest-dev/pytest/issues/3299&gt;`_)\n\n- pytest not longer changes the log level of the root logger when the\n  ``log-level`` parameter has greater numeric value than that of the level of\n  the root logger, which makes it play better with custom logging configuration\n  in user code. (`3307 &lt;https://github.com/pytest-dev/pytest/issues/3307&gt;`_)\n\n\nBug Fixes\n---------\n\n- A rare race-condition which might result in corrupted ``.pyc`` files on\n  Windows has been hopefully solved. (`3008\n  &lt;https://github.com/pytest-dev/pytest/issues/3008&gt;`_)\n\n- Also use iter_marker for discovering the marks applying for marker\n  expressions from the cli to avoid the bad data from the legacy mark storage.\n  (`3441 &lt;https://github.com/pytest-dev/pytest/issues/3441&gt;`_)\n\n- When showing diffs of failed assertions where the contents contain only\n  whitespace, escape them using ``repr()`` first to make it easy to spot the\n  differences. (`3443 &lt;https://github.com/pytest-dev/pytest/issues/3443&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Change documentation copyright year to a range which auto-updates itself each\n  time it is published. (`3303\n  &lt;https://github.com/pytest-dev/pytest/issues/3303&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- ``pytest`` now depends on the `python-atomicwrites\n  &lt;https://github.com/untitaker/python-atomicwrites&gt;`_ library. (`3008\n  &lt;https://github.com/pytest-dev/pytest/issues/3008&gt;`_)\n\n- Update all pypi.python.org URLs to pypi.org. (`3431\n  &lt;https://github.com/pytest-dev/pytest/issues/3431&gt;`_)\n\n- Detect `pytest_` prefixed hooks using the internal plugin manager since\n  ``pluggy`` is deprecating the ``implprefix`` argument to ``PluginManager``.\n  (`3487 &lt;https://github.com/pytest-dev/pytest/issues/3487&gt;`_)\n\n- Import ``Mapping`` and ``Sequence`` from ``_pytest.compat`` instead of\n  directly from ``collections`` in ``python_api.py::approx``. Add ``Mapping``\n  to ``_pytest.compat``, import it from ``collections`` on python 2, but from\n  ``collections.abc`` on Python 3 to avoid a ``DeprecationWarning`` on Python\n  3.7 or newer. (`3497 &lt;https://github.com/pytest-dev/pytest/issues/3497&gt;`_)\n   ```\n   \n  \n  \n   ### 3.5.1\n   ```\n   =========================\n\n\nBug Fixes\n---------\n\n- Reset ``sys.last_type``, ``sys.last_value`` and ``sys.last_traceback`` before\n  each test executes. Those attributes are added by pytest during the test run\n  to aid debugging, but were never reset so they would create a leaking\n  reference to the last failing test&#39;s frame which in turn could never be\n  reclaimed by the garbage collector. (`2798\n  &lt;https://github.com/pytest-dev/pytest/issues/2798&gt;`_)\n\n- ``pytest.raises`` now raises ``TypeError`` when receiving an unknown keyword\n  argument. (`3348 &lt;https://github.com/pytest-dev/pytest/issues/3348&gt;`_)\n\n- ``pytest.raises`` now works with exception classes that look like iterables.\n  (`3372 &lt;https://github.com/pytest-dev/pytest/issues/3372&gt;`_)\n\n\nImproved Documentation\n----------------------\n\n- Fix typo in ``caplog`` fixture documentation, which incorrectly identified\n  certain attributes as methods. (`3406\n  &lt;https://github.com/pytest-dev/pytest/issues/3406&gt;`_)\n\n\nTrivial/Internal Changes\n------------------------\n\n- Added a more indicative error message when parametrizing a function whose\n  argument takes a default value. (`3221\n  &lt;https://github.com/pytest-dev/pytest/issues/3221&gt;`_)\n\n- Remove internal ``_pytest.terminal.flatten`` function in favor of\n  ``more_itertools.collapse``. (`3330\n  &lt;https://github.com/pytest-dev/pytest/issues/3330&gt;`_)\n\n- Import some modules from ``collections.abc`` instead of ``collections`` as\n  the former modules trigger ``DeprecationWarning`` in Python 3.7. (`3339\n  &lt;https://github.com/pytest-dev/pytest/issues/3339&gt;`_)\n\n- record_property is no longer experimental, removing the warnings was\n  forgotten. (`3360 &lt;https://github.com/pytest-dev/pytest/issues/3360&gt;`_)\n\n- Mention in documentation and CLI help that fixtures with leading ``_`` are\n  printed by ``pytest --fixtures`` only if the ``-v`` option is added. (`3398\n  &lt;https://github.com/pytest-dev/pytest/issues/3398&gt;`_)\n   ```\n   \n  \n  \n   ### 3.5.0\n   ```\n   =========================\n\nDeprecations and Removals\n-------------------------\n\n- ``record_xml_property`` fixture is now deprecated in favor of the more\n  generic ``record_property``. (`2770\n  &lt;https://github.com/pytest-dev/pytest/issues/2770&gt;`_)\n\n- Defining ``pytest_plugins`` is now deprecated in non-top-level conftest.py\n  files, because they &quot;leak&quot; to the entire directory tree. `See the docs &lt;https://docs.pytest.org/en/latest/deprecations.htmlpytest-plugins-in-non-top-level-conftest-files&gt;`_ for the rationale behind this decision (`3084\n  &lt;https://github.com/pytest-dev/pytest/issues/3084&gt;`_)\n\n\nFeatures\n--------\n\n- New ``--show-capture`` command-line option that allows to specify how to\n  display captured output when tests fail: ``no``, ``stdout``, ``stderr``,\n  ``log`` or ``all`` (the default). (`1478\n  &lt;https://github.com/pytest-dev/pytest/issues/1478&gt;`_)\n\n- New ``--rootdir`` command-line option to override the rules for discovering\n  the root directory. See `customize\n  &lt;https://docs.pytest.org/en/latest/customize.html&gt;`_ in the documentation for\n  details. (`1642 &lt;https://github.com/pytest-dev/pytest/issues/1642&gt;`_)\n\n- Fixtures are now instantiated based on their scopes, with higher-scoped\n  fixtures (such as ``session``) being instantiated first than lower-scoped\n  fixtures (such as ``function``). The relative order of fixtures of the same\n  scope is kept unchanged, based in their declaration order and their\n  dependencies. (`2405 &lt;https://github.com/pytest-dev/pytest/issues/2405","created_at":"2019-01-31T03:46:25Z","updated_at":"2019-02-13T14:22:24Z","closed_at":"2019-02-13T14:22:24Z","merged_at":null,"merge_commit_sha":"e33eb07535d1bf496e4b1675d9116ebb00bd45da","assignee":null,"assignees":[],"requested_reviewers":[],"requested_teams":[],"labels":[],"milestone":null,"commits_url":"https://api.github.com/repos/fgmacedo/django-export-action/pulls/165/commits","review_comments_url":"https://api.github.com/repos/fgmacedo/django-export-action/pulls/165/comments","review_comment_url":"https://api.github.com/repos/fgmacedo/django-export-action/pulls/comments{/number}","comments_url":"https://api.github.com/repos/fgmacedo/django-export-action/issues/165/comments","statuses_url":"https://api.github.com/repos/fgmacedo/django-export-action/statuses/16a7aacba9a9791e374dbb942d9ce176f12b5856","head":{"label":"fgmacedo:pyup-update-pytest-3.2.5-to-4.2.0","ref":"pyup-update-pytest-3.2.5-to-4.2.0","sha":"16a7aacba9a9791e374dbb942d9ce176f12b5856","user":{"login":"fgmacedo","id":281007,"node_id":"MDQ6VXNlcjI4MTAwNw==","avatar_url":"https://avatars0.githubusercontent.com/u/281007?v=4","gravatar_id":"","url":"https://api.github.com/users/fgmacedo","html_url":"https://github.com/fgmacedo","followers_url":"https://api.github.com/users/fgmacedo/followers","following_url":"https://api.github.com/users/fgmacedo/following{/other_user}","gists_url":"https://api.github.com/users/fgmacedo/gists{/gist_id}","starred_url":"https://api.github.com/users/fgmacedo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgmacedo/subscriptions","organizations_url":"https://api.github.com/users/fgmacedo/orgs","repos_url":"https://api.github.com/users/fgmacedo/repos","events_url":"https://api.github.com/users/fgmacedo/events{/privacy}","received_events_url":"https://api.github.com/users/fgmacedo/received_events","type":"User","site_admin":false},"repo":{"id":69603824,"node_id":"MDEwOlJlcG9zaXRvcnk2OTYwMzgyNA==","name":"django-export-action","full_name":"fgmacedo/django-export-action","private":false,"owner":{"login":"fgmacedo","id":281007,"node_id":"MDQ6VXNlcjI4MTAwNw==","avatar_url":"https://avatars0.githubusercontent.com/u/281007?v=4","gravatar_id":"","url":"https://api.github.com/users/fgmacedo","html_url":"https://github.com/fgmacedo","followers_url":"https://api.github.com/users/fgmacedo/followers","following_url":"https://api.github.com/users/fgmacedo/following{/other_user}","gists_url":"https://api.github.com/users/fgmacedo/gists{/gist_id}","starred_url":"https://api.github.com/users/fgmacedo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgmacedo/subscriptions","organizations_url":"https://api.github.com/users/fgmacedo/orgs","repos_url":"https://api.github.com/users/fgmacedo/repos","events_url":"https://api.github.com/users/fgmacedo/events{/privacy}","received_events_url":"https://api.github.com/users/fgmacedo/received_events","type":"User","site_admin":false},"html_url":"https://github.com/fgmacedo/django-export-action","description":"Generic export action for Django's Admin","fork":false,"url":"https://api.github.com/repos/fgmacedo/django-export-action","forks_url":"https://api.github.com/repos/fgmacedo/django-export-action/forks","keys_url":"https://api.github.com/repos/fgmacedo/django-export-action/keys{/key_id}","collaborators_url":"https://api.github.com/repos/fgmacedo/django-export-action/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/fgmacedo/django-export-action/teams","hooks_url":"https://api.github.com/repos/fgmacedo/django-export-action/hooks","issue_events_url":"https://api.github.com/repos/fgmacedo/django-export-action/issues/events{/number}","events_url":"https://api.github.com/repos/fgmacedo/django-export-action/events","assignees_url":"https://api.github.com/repos/fgmacedo/django-export-action/assignees{/user}","branches_url":"https://api.github.com/repos/fgmacedo/django-export-action/branches{/branch}","tags_url":"https://api.github.com/repos/fgmacedo/django-export-action/tags","blobs_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/refs{/sha}","trees_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/trees{/sha}","statuses_url":"https://api.github.com/repos/fgmacedo/django-export-action/statuses/{sha}","languages_url":"https://api.github.com/repos/fgmacedo/django-export-action/languages","stargazers_url":"https://api.github.com/repos/fgmacedo/django-export-action/stargazers","contributors_url":"https://api.github.com/repos/fgmacedo/django-export-action/contributors","subscribers_url":"https://api.github.com/repos/fgmacedo/django-export-action/subscribers","subscription_url":"https://api.github.com/repos/fgmacedo/django-export-action/subscription","commits_url":"https://api.github.com/repos/fgmacedo/django-export-action/commits{/sha}","git_commits_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/commits{/sha}","comments_url":"https://api.github.com/repos/fgmacedo/django-export-action/comments{/number}","issue_comment_url":"https://api.github.com/repos/fgmacedo/django-export-action/issues/comments{/number}","contents_url":"https://api.github.com/repos/fgmacedo/django-export-action/contents/{+path}","compare_url":"https://api.github.com/repos/fgmacedo/django-export-action/compare/{base}...{head}","merges_url":"https://api.github.com/repos/fgmacedo/django-export-action/merges","archive_url":"https://api.github.com/repos/fgmacedo/django-export-action/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/fgmacedo/django-export-action/downloads","issues_url":"https://api.github.com/repos/fgmacedo/django-export-action/issues{/number}","pulls_url":"https://api.github.com/repos/fgmacedo/django-export-action/pulls{/number}","milestones_url":"https://api.github.com/repos/fgmacedo/django-export-action/milestones{/number}","notifications_url":"https://api.github.com/repos/fgmacedo/django-export-action/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/fgmacedo/django-export-action/labels{/name}","releases_url":"https://api.github.com/repos/fgmacedo/django-export-action/releases{/id}","deployments_url":"https://api.github.com/repos/fgmacedo/django-export-action/deployments","created_at":"2016-09-29T20:09:00Z","updated_at":"2019-01-10T15:43:54Z","pushed_at":"2019-02-13T14:22:19Z","git_url":"git://github.com/fgmacedo/django-export-action.git","ssh_url":"git@github.com:fgmacedo/django-export-action.git","clone_url":"https://github.com/fgmacedo/django-export-action.git","svn_url":"https://github.com/fgmacedo/django-export-action","homepage":null,"size":56,"stargazers_count":42,"watchers_count":42,"language":"Python","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":21,"mirror_url":null,"archived":false,"open_issues_count":24,"license":{"key":"mit","name":"MIT License","spdx_id":"MIT","url":"https://api.github.com/licenses/mit","node_id":"MDc6TGljZW5zZTEz"},"forks":21,"open_issues":24,"watchers":42,"default_branch":"develop"}},"base":{"label":"fgmacedo:develop","ref":"develop","sha":"215fecb9044d22e3ae19d86c3b220041a11fad07","user":{"login":"fgmacedo","id":281007,"node_id":"MDQ6VXNlcjI4MTAwNw==","avatar_url":"https://avatars0.githubusercontent.com/u/281007?v=4","gravatar_id":"","url":"https://api.github.com/users/fgmacedo","html_url":"https://github.com/fgmacedo","followers_url":"https://api.github.com/users/fgmacedo/followers","following_url":"https://api.github.com/users/fgmacedo/following{/other_user}","gists_url":"https://api.github.com/users/fgmacedo/gists{/gist_id}","starred_url":"https://api.github.com/users/fgmacedo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgmacedo/subscriptions","organizations_url":"https://api.github.com/users/fgmacedo/orgs","repos_url":"https://api.github.com/users/fgmacedo/repos","events_url":"https://api.github.com/users/fgmacedo/events{/privacy}","received_events_url":"https://api.github.com/users/fgmacedo/received_events","type":"User","site_admin":false},"repo":{"id":69603824,"node_id":"MDEwOlJlcG9zaXRvcnk2OTYwMzgyNA==","name":"django-export-action","full_name":"fgmacedo/django-export-action","private":false,"owner":{"login":"fgmacedo","id":281007,"node_id":"MDQ6VXNlcjI4MTAwNw==","avatar_url":"https://avatars0.githubusercontent.com/u/281007?v=4","gravatar_id":"","url":"https://api.github.com/users/fgmacedo","html_url":"https://github.com/fgmacedo","followers_url":"https://api.github.com/users/fgmacedo/followers","following_url":"https://api.github.com/users/fgmacedo/following{/other_user}","gists_url":"https://api.github.com/users/fgmacedo/gists{/gist_id}","starred_url":"https://api.github.com/users/fgmacedo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fgmacedo/subscriptions","organizations_url":"https://api.github.com/users/fgmacedo/orgs","repos_url":"https://api.github.com/users/fgmacedo/repos","events_url":"https://api.github.com/users/fgmacedo/events{/privacy}","received_events_url":"https://api.github.com/users/fgmacedo/received_events","type":"User","site_admin":false},"html_url":"https://github.com/fgmacedo/django-export-action","description":"Generic export action for Django's Admin","fork":false,"url":"https://api.github.com/repos/fgmacedo/django-export-action","forks_url":"https://api.github.com/repos/fgmacedo/django-export-action/forks","keys_url":"https://api.github.com/repos/fgmacedo/django-export-action/keys{/key_id}","collaborators_url":"https://api.github.com/repos/fgmacedo/django-export-action/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/fgmacedo/django-export-action/teams","hooks_url":"https://api.github.com/repos/fgmacedo/django-export-action/hooks","issue_events_url":"https://api.github.com/repos/fgmacedo/django-export-action/issues/events{/number}","events_url":"https://api.github.com/repos/fgmacedo/django-export-action/events","assignees_url":"https://api.github.com/repos/fgmacedo/django-export-action/assignees{/user}","branches_url":"https://api.github.com/repos/fgmacedo/django-export-action/branches{/branch}","tags_url":"https://api.github.com/repos/fgmacedo/django-export-action/tags","blobs_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/refs{/sha}","trees_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/trees{/sha}","statuses_url":"https://api.github.com/repos/fgmacedo/django-export-action/statuses/{sha}","languages_url":"https://api.github.com/repos/fgmacedo/django-export-action/languages","stargazers_url":"https://api.github.com/repos/fgmacedo/django-export-action/stargazers","contributors_url":"https://api.github.com/repos/fgmacedo/django-export-action/contributors","subscribers_url":"https://api.github.com/repos/fgmacedo/django-export-action/subscribers","subscription_url":"https://api.github.com/repos/fgmacedo/django-export-action/subscription","commits_url":"https://api.github.com/repos/fgmacedo/django-export-action/commits{/sha}","git_commits_url":"https://api.github.com/repos/fgmacedo/django-export-action/git/commits{/sha}","comments_url":"https://api.github.com/repos/fgmacedo/django-export-action/comments{/number}","issue_comment_url":"https://api.github.com/repos/fgmacedo/django-export-action/issues/comments{/number}","contents_url":"https://api.github.com/repos/fgmacedo/django-export-action/contents/{+path}","compare_url":"https://api.github.com/repos/fgmacedo/django-export-action/compare/{base}...{head}","merges_url":"https://api.github.com/repos/fgmacedo/django-export-action/merges","archive_url":"https://api.github.com/repos/fgmacedo/django-export-action/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/fgmacedo/django-export-action/downloads","issues_url":"https://api.github.com/repos/fgmacedo/django-export-action/issues{/number}","pulls_url":"https://api.github.com/repos/fgmacedo/django-export-action/pulls{/number}","milestones_url":"https://api.github.com/repos/fgmacedo/django-export-action/milestones{/number}","notifications_url":"https://api.github.com/repos/fgmacedo/django-export-action/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/fgmacedo/django-export-action/labels{/name}","releases_url":"https://api.github.com/repos/fgmacedo/django-export-action/releases{/id}","deployments_url":"https://api.github.com/repos/fgmacedo/django-export-action/deployments","created_at":"2016-09-29T20:09:00Z","updated_at":"2019-01-10T15:43:54Z","pushed_at":"2019-02-13T14:22:19Z","git_url":"git://github.com/fgmacedo/django-export-action.git","ssh_url":"git@github.com:fgmacedo/django-export-action.git","clone_url":"https://github.com/fgmacedo/django-export-action.git","svn_url":"https://github.com/fgmacedo/django-export-action","homepage":null,"size":56,"stargazers_count":42,"watchers_count":42,"language":"Python","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":21,"mirror_url":null,"archived":false,"open_issues_count":24,"license":{"key":"mit","name":"MIT License","spdx_id":"MIT","url":"https://api.github.com/licenses/mit","node_id":"MDc6TGljZW5zZTEz"},"forks":21,"open_issues":24,"watchers":42,"default_branch":"develop"}},"_links":{"self":{"href":"https://api.github.com/repos/fgmacedo/django-export-action/pulls/165"},"html":{"href":"https://github.com/fgmacedo/django-export-action/pull/165"},"issue":{"href":"https://api.github.com/repos/fgmacedo/django-export-action/issues/165"},"comments":{"href":"https://api.github.com/repos/fgmacedo/django-export-action/issues/165/comments"},"review_comments":{"href":"https://api.github.com/repos/fgmacedo/django-export-action/pulls/165/comments"},"review_comment":{"href":"https://api.github.com/repos/fgmacedo/django-export-action/pulls/comments{/number}"},"commits":{"href":"https://api.github.com/repos/fgmacedo/django-export-action/pulls/165/commits"},"statuses":{"href":"https://api.github.com/repos/fgmacedo/django-export-action/statuses/16a7aacba9a9791e374dbb942d9ce176f12b5856"}},"author_association":"CONTRIBUTOR","merged":false,"mergeable":true,"rebaseable":true,"mergeable_state":"unstable","merged_by":null,"comments":1,"review_comments":0,"maintainer_can_modify":false,"commits":1,"additions":1,"deletions":1,"changed_files":1}}
{"actor":{"display_login":"pyup-bot"}}