payload: {"action":"closed","number":160,"pull_request":{"url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls/160","id":284313164,"node_id":"MDExOlB1bGxSZXF1ZXN0Mjg0MzEzMTY0","html_url":"https://github.com/infOpen/ansible-role-postgresql/pull/160","diff_url":"https://github.com/infOpen/ansible-role-postgresql/pull/160.diff","patch_url":"https://github.com/infOpen/ansible-role-postgresql/pull/160.patch","issue_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues/160","number":160,"state":"closed","locked":false,"title":"Update pytest to 4.6.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.6.2** to **4.6.0**.\n\n\n\n<details>\n  <summary>Changelog</summary>\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  \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 no 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 tear","created_at":"2019-06-02T03:24:50Z","updated_at":"2019-06-03T04:09:35Z","closed_at":"2019-06-03T04:09:35Z","merged_at":null,"merge_commit_sha":"5a9ea8bbbb3fea54286600fd4867c52b5168324f","assignee":null,"assignees":[],"requested_reviewers":[],"requested_teams":[],"labels":[],"milestone":null,"commits_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls/160/commits","review_comments_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls/160/comments","review_comment_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls/comments{/number}","comments_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues/160/comments","statuses_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/statuses/19f32e63c7e6a64e32d901283aa0e6a15c0914e5","head":{"label":"infOpen:pyup-update-pytest-3.6.2-to-4.6.0","ref":"pyup-update-pytest-3.6.2-to-4.6.0","sha":"19f32e63c7e6a64e32d901283aa0e6a15c0914e5","user":{"login":"infOpen","id":2934016,"node_id":"MDEyOk9yZ2FuaXphdGlvbjI5MzQwMTY=","avatar_url":"https://avatars2.githubusercontent.com/u/2934016?v=4","gravatar_id":"","url":"https://api.github.com/users/infOpen","html_url":"https://github.com/infOpen","followers_url":"https://api.github.com/users/infOpen/followers","following_url":"https://api.github.com/users/infOpen/following{/other_user}","gists_url":"https://api.github.com/users/infOpen/gists{/gist_id}","starred_url":"https://api.github.com/users/infOpen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/infOpen/subscriptions","organizations_url":"https://api.github.com/users/infOpen/orgs","repos_url":"https://api.github.com/users/infOpen/repos","events_url":"https://api.github.com/users/infOpen/events{/privacy}","received_events_url":"https://api.github.com/users/infOpen/received_events","type":"Organization","site_admin":false},"repo":{"id":89707197,"node_id":"MDEwOlJlcG9zaXRvcnk4OTcwNzE5Nw==","name":"ansible-role-postgresql","full_name":"infOpen/ansible-role-postgresql","private":false,"owner":{"login":"infOpen","id":2934016,"node_id":"MDEyOk9yZ2FuaXphdGlvbjI5MzQwMTY=","avatar_url":"https://avatars2.githubusercontent.com/u/2934016?v=4","gravatar_id":"","url":"https://api.github.com/users/infOpen","html_url":"https://github.com/infOpen","followers_url":"https://api.github.com/users/infOpen/followers","following_url":"https://api.github.com/users/infOpen/following{/other_user}","gists_url":"https://api.github.com/users/infOpen/gists{/gist_id}","starred_url":"https://api.github.com/users/infOpen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/infOpen/subscriptions","organizations_url":"https://api.github.com/users/infOpen/orgs","repos_url":"https://api.github.com/users/infOpen/repos","events_url":"https://api.github.com/users/infOpen/events{/privacy}","received_events_url":"https://api.github.com/users/infOpen/received_events","type":"Organization","site_admin":false},"html_url":"https://github.com/infOpen/ansible-role-postgresql","description":"Ansible role to install and configure Postgresql","fork":false,"url":"https://api.github.com/repos/infOpen/ansible-role-postgresql","forks_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/forks","keys_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/keys{/key_id}","collaborators_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/teams","hooks_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/hooks","issue_events_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues/events{/number}","events_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/events","assignees_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/assignees{/user}","branches_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/branches{/branch}","tags_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/tags","blobs_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/refs{/sha}","trees_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/trees{/sha}","statuses_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/statuses/{sha}","languages_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/languages","stargazers_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/stargazers","contributors_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/contributors","subscribers_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/subscribers","subscription_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/subscription","commits_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/commits{/sha}","git_commits_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/commits{/sha}","comments_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/comments{/number}","issue_comment_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues/comments{/number}","contents_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/contents/{+path}","compare_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/compare/{base}...{head}","merges_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/merges","archive_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/downloads","issues_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues{/number}","pulls_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls{/number}","milestones_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/milestones{/number}","notifications_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/labels{/name}","releases_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/releases{/id}","deployments_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/deployments","created_at":"2017-04-28T13:11:17Z","updated_at":"2019-04-16T22:05:12Z","pushed_at":"2019-06-03T04:09:32Z","git_url":"git://github.com/infOpen/ansible-role-postgresql.git","ssh_url":"git@github.com:infOpen/ansible-role-postgresql.git","clone_url":"https://github.com/infOpen/ansible-role-postgresql.git","svn_url":"https://github.com/infOpen/ansible-role-postgresql","homepage":"","size":86,"stargazers_count":2,"watchers_count":2,"language":"Python","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":0,"mirror_url":null,"archived":false,"disabled":false,"open_issues_count":4,"license":{"key":"mit","name":"MIT License","spdx_id":"MIT","url":"https://api.github.com/licenses/mit","node_id":"MDc6TGljZW5zZTEz"},"forks":0,"open_issues":4,"watchers":2,"default_branch":"develop"}},"base":{"label":"infOpen:develop","ref":"develop","sha":"29d9e470e58497c10c46ded5ff77281d7da071a4","user":{"login":"infOpen","id":2934016,"node_id":"MDEyOk9yZ2FuaXphdGlvbjI5MzQwMTY=","avatar_url":"https://avatars2.githubusercontent.com/u/2934016?v=4","gravatar_id":"","url":"https://api.github.com/users/infOpen","html_url":"https://github.com/infOpen","followers_url":"https://api.github.com/users/infOpen/followers","following_url":"https://api.github.com/users/infOpen/following{/other_user}","gists_url":"https://api.github.com/users/infOpen/gists{/gist_id}","starred_url":"https://api.github.com/users/infOpen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/infOpen/subscriptions","organizations_url":"https://api.github.com/users/infOpen/orgs","repos_url":"https://api.github.com/users/infOpen/repos","events_url":"https://api.github.com/users/infOpen/events{/privacy}","received_events_url":"https://api.github.com/users/infOpen/received_events","type":"Organization","site_admin":false},"repo":{"id":89707197,"node_id":"MDEwOlJlcG9zaXRvcnk4OTcwNzE5Nw==","name":"ansible-role-postgresql","full_name":"infOpen/ansible-role-postgresql","private":false,"owner":{"login":"infOpen","id":2934016,"node_id":"MDEyOk9yZ2FuaXphdGlvbjI5MzQwMTY=","avatar_url":"https://avatars2.githubusercontent.com/u/2934016?v=4","gravatar_id":"","url":"https://api.github.com/users/infOpen","html_url":"https://github.com/infOpen","followers_url":"https://api.github.com/users/infOpen/followers","following_url":"https://api.github.com/users/infOpen/following{/other_user}","gists_url":"https://api.github.com/users/infOpen/gists{/gist_id}","starred_url":"https://api.github.com/users/infOpen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/infOpen/subscriptions","organizations_url":"https://api.github.com/users/infOpen/orgs","repos_url":"https://api.github.com/users/infOpen/repos","events_url":"https://api.github.com/users/infOpen/events{/privacy}","received_events_url":"https://api.github.com/users/infOpen/received_events","type":"Organization","site_admin":false},"html_url":"https://github.com/infOpen/ansible-role-postgresql","description":"Ansible role to install and configure Postgresql","fork":false,"url":"https://api.github.com/repos/infOpen/ansible-role-postgresql","forks_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/forks","keys_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/keys{/key_id}","collaborators_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/collaborators{/collaborator}","teams_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/teams","hooks_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/hooks","issue_events_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues/events{/number}","events_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/events","assignees_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/assignees{/user}","branches_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/branches{/branch}","tags_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/tags","blobs_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/blobs{/sha}","git_tags_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/tags{/sha}","git_refs_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/refs{/sha}","trees_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/trees{/sha}","statuses_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/statuses/{sha}","languages_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/languages","stargazers_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/stargazers","contributors_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/contributors","subscribers_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/subscribers","subscription_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/subscription","commits_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/commits{/sha}","git_commits_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/git/commits{/sha}","comments_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/comments{/number}","issue_comment_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues/comments{/number}","contents_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/contents/{+path}","compare_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/compare/{base}...{head}","merges_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/merges","archive_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/{archive_format}{/ref}","downloads_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/downloads","issues_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues{/number}","pulls_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls{/number}","milestones_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/milestones{/number}","notifications_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/notifications{?since,all,participating}","labels_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/labels{/name}","releases_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/releases{/id}","deployments_url":"https://api.github.com/repos/infOpen/ansible-role-postgresql/deployments","created_at":"2017-04-28T13:11:17Z","updated_at":"2019-04-16T22:05:12Z","pushed_at":"2019-06-03T04:09:32Z","git_url":"git://github.com/infOpen/ansible-role-postgresql.git","ssh_url":"git@github.com:infOpen/ansible-role-postgresql.git","clone_url":"https://github.com/infOpen/ansible-role-postgresql.git","svn_url":"https://github.com/infOpen/ansible-role-postgresql","homepage":"","size":86,"stargazers_count":2,"watchers_count":2,"language":"Python","has_issues":true,"has_projects":true,"has_downloads":true,"has_wiki":true,"has_pages":false,"forks_count":0,"mirror_url":null,"archived":false,"disabled":false,"open_issues_count":4,"license":{"key":"mit","name":"MIT License","spdx_id":"MIT","url":"https://api.github.com/licenses/mit","node_id":"MDc6TGljZW5zZTEz"},"forks":0,"open_issues":4,"watchers":2,"default_branch":"develop"}},"_links":{"self":{"href":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls/160"},"html":{"href":"https://github.com/infOpen/ansible-role-postgresql/pull/160"},"issue":{"href":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues/160"},"comments":{"href":"https://api.github.com/repos/infOpen/ansible-role-postgresql/issues/160/comments"},"review_comments":{"href":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls/160/comments"},"review_comment":{"href":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls/comments{/number}"},"commits":{"href":"https://api.github.com/repos/infOpen/ansible-role-postgresql/pulls/160/commits"},"statuses":{"href":"https://api.github.com/repos/infOpen/ansible-role-postgresql/statuses/19f32e63c7e6a64e32d901283aa0e6a15c0914e5"}},"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}}
other: {"actor":{"display_login":"pyup-bot"}}