Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Last Failed" mode no longer reruns all tests on successful run #5301

Closed
exhuma opened this issue May 23, 2019 · 51 comments · Fixed by #6448
Closed

"Last Failed" mode no longer reruns all tests on successful run #5301

exhuma opened this issue May 23, 2019 · 51 comments · Fixed by #6448
Labels
plugin: cache type: bug type: regression

Comments

@exhuma
Copy link

@exhuma exhuma commented May 23, 2019

For about a month now (maybe less) our team is experiencing issues with the --last-failed mode. Since we regularly update our development dependencies there is a chance that it might be due to an issue in pytest. Unfortunately I don't have an example to reproduce the issue.

I will try downgrading to pytest 4.4 and see if this fixes the issue. If I don't forget it, I will update this issue if that's the case.

When using "last-failed" mode we expect the following behaviour:

  • As long as there are failures, only run the failed tests on each run
  • The run following the first run without any failures should re-run all tests

What we observe instead:

  • As long as there are failures, only run the failed tests on each run
  • The run following the first run without any failures only some tests are re-run. Only a fraction of tests are executed.

Workaround:

  • Running pytest once without --last-failed solves the issue (but only once).

pip list output

Package                       Version  Location
----------------------------- -------- ------------------------------
alabaster                     0.7.12
apipkg                        1.5
asn1crypto                    0.24.0
astroid                       2.2.5
atomicwrites                  1.3.0
attr                          0.3.1
attrs                         19.1.0
autopep8                      1.4.4
Babel                         2.6.0
bboss                         1.10.1
bcrypt                        3.1.6
certifi                       2019.3.9
cffi                          1.12.3
chardet                       3.0.4
colorama                      0.4.1
commonmark                    0.9.0
config-resolver               4.3.4
coverage                      4.5.3
cryptography                  2.6.1
distribute                    0.7.3
docutils                      0.14
entrypoints                   0.3
execnet                       1.6.0
flake8                        3.7.7
flake8-polyfill               1.0.2
future                        0.17.1
gouge                         1.3.0
idna                          2.8
imagesize                     1.1.0
isort                         4.3.20
jargon                        4.14.0
Jinja2                        2.10.1
lazy-object-proxy             1.4.1
mando                         0.6.4
MarkupSafe                    1.1.1
mccabe                        0.6.1
more-itertools                7.0.0
msgpack-python                0.5.6
mypy                          0.701
mypy-extensions               0.4.1
packaging                     19.0
paramiko                      2.4.2
pathlib2                      2.3.3
pexpect                       3.3
pip                           19.1.1
pkg-resources                 0.0.0
pluggy                        0.11.0
puresnmp                      1.5.1
py                            1.8.0
pyasn1                        0.4.5
pycodestyle                   2.5.0
pycparser                     2.19
pyflakes                      2.1.1
Pygments                      2.4.0
pylint                        2.3.1
PyNaCl                        1.3.0
pynet                         3.11.0   /home/users/malbert/work/pynet
pyparsing                     2.4.0
pytest                        4.5.0
pytest-cov                    2.7.1
pytest-cover                  3.0.0
pytest-coverage               0.0
pytest-forked                 1.0.2
pytest-xdist                  1.28.0
python-dateutil               2.8.0
pytz                          2019.1
PyYAML                        3.13
radon                         3.0.3
recommonmark                  0.5.0
requests                      2.22.0
schema                        5.2.3
setuptools                    41.0.1
six                           1.12.0
snowballstemmer               1.2.1
Sphinx                        2.0.1
sphinx-rtd-theme              0.4.3
sphinxcontrib-applehelp       1.0.1
sphinxcontrib-devhelp         1.0.1
sphinxcontrib-htmlhelp        1.0.2
sphinxcontrib-jsmath          1.0.1
sphinxcontrib-qthelp          1.0.2
sphinxcontrib-serializinghtml 1.1.3
typed-ast                     1.3.5
typing                        3.6.6
urllib3                       1.25.2
verlib                        0.1
wcwidth                       0.1.7
wheel                         0.33.4
wrapt                         1.11.1

OS Information

Linux BBS-nexus.ipsw.dt.ept.lu 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

Python 3.5.2
@blueyed
Copy link
Contributor

@blueyed blueyed commented May 23, 2019

Maybe due to 1f5a61e / #5034.

@blueyed blueyed added plugin: cache type: bug labels May 23, 2019
@blueyed
Copy link
Contributor

@blueyed blueyed commented May 23, 2019

  • only some tests are re-run. Only a fraction of tests are executed.

More details on those might be interesting if you see it again.

@blueyed
Copy link
Contributor

@blueyed blueyed commented May 23, 2019

btw: I've found to put the pytest cache dir under Git control good for looking how the cache changes over time / after a run. This came up with having state of last-failed stashed for later / git-bisect.

@exhuma
Copy link
Author

@exhuma exhuma commented May 23, 2019

I have downgraded to 4.4 and it seems better now, so maybe it is indeed a regression in 4.5.

I'm still keeping an eye on this, although, my test-runs and round-trip is not the fastest in the project I am currently working on which has around 1600 tests (and I will be off from this afternoon until Monday).

@exhuma
Copy link
Author

@exhuma exhuma commented May 23, 2019

... forgot to ask: You asked for more details on the fraction of tests. Is there anything specific I should look out for?

@exhuma
Copy link
Author

@exhuma exhuma commented May 23, 2019

I can now confirm that it definitely only happens in 4.5.0

@blueyed blueyed added this to the 4.6 milestone May 27, 2019
@blueyed blueyed added the type: regression label May 27, 2019
@blueyed
Copy link
Contributor

@blueyed blueyed commented May 29, 2019

Are you seeing some output then, e.g. "run-last-failure: 1 known failures not in selected tests" then?

Just noticed this myself, and bisected it to 08734bd.

@blueyed
Copy link
Contributor

@blueyed blueyed commented May 29, 2019

My issue is fixed with #5333 - would be good if you could try it, and/or provide more information to reproduce your issue.

@nicoddemus
Copy link
Member

@nicoddemus nicoddemus commented May 29, 2019

Thanks @blueyed for the fix. 👍

@exhuma
Copy link
Author

@exhuma exhuma commented May 30, 2019

I'm currently out of office. I will check back on Monday and let you know if the fix worked.

@exhuma
Copy link
Author

@exhuma exhuma commented Jun 7, 2019

Sorry for the late reply. I only now managed to upgrade and am now on pytest 4.6.2 and it is still not re-running all tests. I just ran a successful test by just running ./env/bin/pytest without any arguments (that is, without last-fail mode).

After running that command, I ran pytest with last-fail activated and I get this:

================================================= test session starts ==================================================
platform linux -- Python 3.5.2, pytest-4.6.2, py-1.8.0, pluggy-0.12.0
rootdir: /home/users/malbert/work/ipbase/core, inifile: pytest.ini, testpaths: tests
plugins: cov-2.7.1
collected 448 items
run-last-failure: 99 known failures not in selected tests (skipped 87 files)

Note that it says: "skipped 87 files". But because the previous test-run was successful it should have run everything. It also states that there are 99 known failures even though the test-run was successful.

Until now, we blacklisted only 4.5 but unfortunately I think we need to stick with pytest < 4.5 for now.

It is not super critical for us as the failures get picket up by our CI pipelines but it is still quite annoying to see everything go green only to have the pipeline fail 10 minutes later 😉

Unfortunately it is sometimes hard to spot that not every test was run. Especially if only one or two got skipped.

If you need help debugging this, I could make myself available for a skype/hangout/... session as I am aware that this is hard to reproduce.

@blueyed blueyed reopened this Jun 7, 2019
@blueyed
Copy link
Contributor

@blueyed blueyed commented Jun 7, 2019

It also states that there are 99 known failures even though the test-run was successful.

It says "99 known failures not in selected tests", i.e. there are known failures outside of the collected tests. This might be due to only running selecting specific tests, but also because files have been removed or renamed.
You do not specify how you run pytest, e.g. what args are being used.

For this to debug you can inspect .pytest_cache/v/cache/lastfailed.

I suggest copying .pytest_cache for a state where this is failing for you, and then git-bisect pytest to see where that behavior changed.

@exhuma
Copy link
Author

@exhuma exhuma commented Jun 14, 2019

I am having trouble reproducing this in a controlled manner. It still happens, but keeping a backup of .pytest_cache did not help. Here's what I did:

  • cause a bug in my code-base and run tests
  • Fix the bug and re-run the tests resulting in 0 failures
  • re-run tests again (expecting it to execute them all), but not all are executed.
  • make a copy of .pytest_cache using: cp -rv .pytest_cache failing-cache
  • check-out pytest 4.4.2 which was the last one to work
  • re-run the tests (the failing cache is still in place). Now, as expected, all tests are run
  • check-out 4.6.3
  • copy the failing cache using cp -rv failing-cache .pytest_cache
  • re-run the test, expecting it to not run all the tests (this would be my bisect bad baseline). But lo and behold, all tests are run 🤔

I am still trying to find a way to reproduce the issue. But seemingly, copying the .pytest_cache folder is not enough.

And yes indeed, I forgot to mention how I run pytest. The command-line is:

./env/bin/pytest --lf

and pytest.ini contains:

 [pytest]
 norecursedirs = .git env log
 testpaths = tests
 log_cli_level = CRITICAL

@exhuma
Copy link
Author

@exhuma exhuma commented Jun 14, 2019

I am currently unable to reproduce the error. It's unfortunate that the .pytest_cache backup did not help, even though I ran into the issue again this morning.

I will... for now... pin pytest to the last known failing version 4.6.2 in all my projects and keep a close eye on it. If I find more I will send an update.

I need to drop this for now as I need to advance on other projects 🙁

@nicoddemus
Copy link
Member

@nicoddemus nicoddemus commented Jun 15, 2019

@exhuma it is really a bummer that we can't reproduce this. Please do come back when you give this another go. 👍

@exhuma
Copy link
Author

@exhuma exhuma commented Jun 20, 2019

I'm aware that this is another comment which won't help much identifying it, but - for what it's worth - I just started adding unit-tests to a new project, so everything is brand-new: New pytest install (on 4.6.3) and brand-new unit-tests. Even on a completely different machine (private laptop as compared to shared office server).

I ran into the same issue about 20min into development. At first everything seemed fine, I was not even thinking abut this issue and suddenly it happened again. I still don't know what triggers it. But from one moment to the next it decided to ignore most tests again.

I'm merely posting this update as this is on a completely different setup as the one I was observing the behaviour earlier. So it's not isolated to our office box. I was still not sure if it might be something local to that environment. I can safely discard that now. It is definitely something affecting pytest itself.

I will go ahead and create a dummy project now and keep track of my steps... Maybe I will find something

@exhuma
Copy link
Author

@exhuma exhuma commented Jun 20, 2019

... for the life of me I can't reproduce it in a controlled manner. Whenever I try to, it works as it should. With the dummy project I created right now it works again. But on the same machine I have another window open with a project where it doesn't ☹️

@exhuma
Copy link
Author

@exhuma exhuma commented Jun 20, 2019

Okay.... I may have something which demonstrates the error. Unfortunately it does not show the steps of how to get there. I took the project I am working on and zipped it. Unzipping it, cleaning it out and running the tests with --lf demonstrates the error.
As I can't make uploads directly on GitHub do you have a preference or an idea how I can share it?

@blueyed
Copy link
Contributor

@blueyed blueyed commented Jun 20, 2019

Great.
You could start by investigating if e.g. there are files in the cache that do not exist anymore etc. - basically all the ideas I gave already.
Then also the code for this is rather compact, and you should be able to print-debug it.
Also git-bisecting it would still be useful.

Otherwise you could push the project as a temporary git project somewhere, but I'd suggest to start debugging it yourself already.

@exhuma
Copy link
Author

@exhuma exhuma commented Jun 21, 2019

This is getting me somewhere. Bisecting gave me the commit 08734bd as the culprit

@exhuma
Copy link
Author

@exhuma exhuma commented Jun 21, 2019

The commit contains a check to see if a file should be skipped.

The check does not make sense to me. I read it as "If a file has not failed in the last run, skip it". This may explain why I was unable to reproduce it. I was always using "dummy" projects with just one test-file. This seems to happen if you have multiple files.

blueyed added a commit to blueyed/dotfiles that referenced this issue Oct 22, 2019
@blueyed
Copy link
Contributor

@blueyed blueyed commented Oct 22, 2019

@exhuma
It does not really help us if you repeat that it's annoying - I think we got that.. ;)
I still recommend to use e.g. version control to see what going on (you can use https://github.com/blueyed/dotfiles/blob/master/usr/bin/p-cache-git). This was also what showed me e.g. #5206.

As for disabling the optimisation: not that I know of - but you could (monkey-)patch it out I guess - after all you would have to use a config setting for it, so you can have something in a pytest plugin also probably. But then you also need to know what's causing it really in the first place I guess.

Have you checked if the git-bisect result (#5301 (comment)) still applies?
Maybe #5625 helps, which takes given args better into account.

@blueyed
Copy link
Contributor

@blueyed blueyed commented Oct 22, 2019

I still recommend to use e.g. version control to see what going on

You could have e.g. a p script that wraps git to commit before and after each run. If it then happens again you have information to debug this. I recommend only using "last-failed" from the cache then (but not e.g. "nodeids" at least, which is buggy (#6004)).

blueyed added a commit to blueyed/pytest that referenced this issue Nov 2, 2019
This is meant to aid debugging, e.g. in case there are suddenly a lot of
last-failed tests.

Ref: pytest-dev#5301
Works better with: #54
blueyed added a commit to blueyed/pytest that referenced this issue Nov 2, 2019
…55)

This is meant to aid debugging, e.g. in case there are suddenly a lot of
last-failed tests.

Ref: pytest-dev#5301
Ref: #54
@segv
Copy link

@segv segv commented Jan 9, 2020

i'm hitting this bug as well. i'm able to reproduce it by deleting or renaming&fixing the failing test. if i have two files, test_a.py and test_b.py, with a passing and a failing test in test_a and a single failing test in test_b; if i delete the failing test from test_a.py then ptest --lf will never run the tests in test_b.py. i also see this behavior if i fix and rename the test before running pytest --lf again.

i'm not sure if this is exactly the same situation i'm hitting in production but i hope this info helps a bit.

ps - for anyone else who googles this issue my hacky work around is to delete .pytest_cache when pytest exits with success (since i'm calling pytest from a wrapper script this is easy for me to do):

pytest --lf ... && rm -f .pytest_cache/v/cache/lastfailed

@segv
Copy link

@segv segv commented Jan 9, 2020

(using pytest 5.3.2 and python 3.7.5 in a fresh venv)

@nicoddemus
Copy link
Member

@nicoddemus nicoddemus commented Jan 9, 2020

Thanks @segv for the reproducible problem, we appreciate it!

What happens is:

First run:

$ pytest 
collected 3 items
test_a.py::test_1 PASS
test_a.py::test_2 FAIL
test_b.py::test_3 PASS

So --lf records test_a.py::test_2 as failed.

Now we comment out the function test_2:

$ pytest --lf
collected 1 item
run-last-failure: 1 known failures not in selected tests (skipped 1 file)
test_a.py::test_1 PASS

The second run should now run all tests, because it could not detect any failures this time around.

But after some debugging, now things are clearer: the optimization that prevents us from collecting files in case they didn't contain any failing tests from the previous run effectively breaks the case 're-running all tests due to no previous failures', because the files with all tests passing are not even collected.

That's what's happening here: because no test from test_b.py failed, it is not collected, but because on the 2nd run there's no failing tests anymore, it should run all tests, but it only runs tests from test_a.py because test_b.py was never collected.

Commenting out pytest_collect_ignore (responsible for the optimization) now produces the correct behavior:

collected 2 items
run-last-failure: 1 known failures not in selected tests

test_a.py::test_1 PASS
test_b.py::test_3 PASS

But even then it seems some adjustments in the run-last-failure message.

If my analysis is correct, I don't think there's any way to implement the existing optimization consistently, so I propose we remove it. Better to have a slower collection than wrong/unexpected behavior.

What do you think @blueyed?

@blueyed
Copy link
Contributor

@blueyed blueyed commented Jan 11, 2020

What do you think @blueyed?

This could be improved/fixed by storing the mtime of files, i.e. if a file is newer then what we know about its failures it could be ignored for skipping others. (Note that this is something good to have in general - in blueyed#102 I've added this via a generic "cache/fspaths" cache key, where it is then used for a faster -k that can skip collection)

Another approach/idea might be to only ignore files once at least a failure has been found. For this it might be best to sort modules/files with failures to the beginning (via pytest_make_collect_report). I've tried to use pytest_make_collect_report instead of pytest_ignore_collect, but the problem there is that it cannot be used both as a hookwrapper, and to return an empty collect report for skipped files (it can still override the result, but collection is not skipped then, i.e. it has no performance improvement then anymore). For this two separate plugins could be used (a hookwrapper to sort failures first, and a firstresult one to skip files).

Somehow related also: #5625

@blueyed
Copy link
Contributor

@blueyed blueyed commented Jan 13, 2020

You might want to try #6448.

@nicoddemus
Copy link
Member

@nicoddemus nicoddemus commented Jan 22, 2020

(Sorry for the delay)

This could be improved/fixed by storing the mtime of files, i.e. if a file is newer then what we know about its failures it could be ignored for skipping others.

Not sure I follow can you elaborate? How it would help with the case in #5301 (comment), given that the file modified is the one with the failure?

@blueyed
Copy link
Contributor

@blueyed blueyed commented Jan 24, 2020

@nicoddemus I cannot really recall after 2 weeks. What I've meant likely is keeping track of mtime of files and execution times for tests, therefore heuristics could be applied to detect "this test is not in there anymore" etc, but it always is a question about "have we collected everything from the file?" (i.e. no -k etc).
Therefore #6448 is better in this regard, because it hooks into the collection process already.

@nicoddemus nicoddemus removed this from the 4.6 milestone Feb 13, 2020
blueyed added a commit to blueyed/pytest that referenced this issue Feb 18, 2020
blueyed added a commit to blueyed/pytest that referenced this issue Feb 19, 2020
Fixes pytest-dev#5301.

Refactor/steps:

- use var
- harden test_lastfailed_usecase
- harden test_failedfirst_order
- revisit last_failed_paths
- harden test_lastfailed_with_known_failures_not_being_selected
blueyed added a commit that referenced this issue Feb 19, 2020
Fixes #5301.

Refactor/steps:

- use var
- harden test_lastfailed_usecase
- harden test_failedfirst_order
- revisit last_failed_paths
- harden test_lastfailed_with_known_failures_not_being_selected
bors bot added a commit to aragilar/spaceplot that referenced this issue Apr 17, 2021
6: Pin pytest to latest version 6.2.3 r=aragilar a=pyup-bot


This PR pins [pytest](https://pypi.org/project/pytest) to the latest release **6.2.3**.



<details>
  <summary>Changelog</summary>
  
  
   ### 6.2.2
   ```
   =========================

Bug Fixes
---------

- `8152 &lt;https://github.com/pytest-dev/pytest/issues/8152&gt;`_: Fixed &quot;(&lt;Skipped instance&gt;)&quot; being shown as a skip reason in the verbose test summary line when the reason is empty.


- `8249 &lt;https://github.com/pytest-dev/pytest/issues/8249&gt;`_: Fix the ``faulthandler`` plugin for occasions when running with ``twisted.logger`` and using ``pytest --capture=no``.
   ```
   
  
  
   ### 6.2.1
   ```
   =========================

Bug Fixes
---------

- `7678 &lt;https://github.com/pytest-dev/pytest/issues/7678&gt;`_: Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in
  the host and loaded later from an UNC mounted path (Windows).


- `8132 &lt;https://github.com/pytest-dev/pytest/issues/8132&gt;`_: Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises
  ``TypeError`` when dealing with non-numeric types, falling back to normal comparison.
  Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
  and happened to compare correctly to a scalar if they had only one element.
  After 6.2.0, these types began failing, because they inherited neither from
  standard Python number hierarchy nor from ``numpy.ndarray``.

  ``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array
  protocol and are not scalars. This treats array-like objects like numpy arrays,
  regardless of size.
   ```
   
  
  
   ### 6.2.0
   ```
   =========================

Breaking Changes
----------------

- `7808 &lt;https://github.com/pytest-dev/pytest/issues/7808&gt;`_: pytest now supports python3.6+ only.



Deprecations
------------

- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_: Directly constructing/calling the following classes/functions is now deprecated:

  - ``_pytest.cacheprovider.Cache``
  - ``_pytest.cacheprovider.Cache.for_config()``
  - ``_pytest.cacheprovider.Cache.clear_cache()``
  - ``_pytest.cacheprovider.Cache.cache_dir_from_config()``
  - ``_pytest.capture.CaptureFixture``
  - ``_pytest.fixtures.FixtureRequest``
  - ``_pytest.fixtures.SubRequest``
  - ``_pytest.logging.LogCaptureFixture``
  - ``_pytest.pytester.Pytester``
  - ``_pytest.pytester.Testdir``
  - ``_pytest.recwarn.WarningsRecorder``
  - ``_pytest.recwarn.WarningsChecker``
  - ``_pytest.tmpdir.TempPathFactory``
  - ``_pytest.tmpdir.TempdirFactory``

  These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.


- `7530 &lt;https://github.com/pytest-dev/pytest/issues/7530&gt;`_: The ``--strict`` command-line option has been deprecated, use ``--strict-markers`` instead.

  We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing flag for all strictness
  related options (``--strict-markers`` and ``--strict-config`` at the moment, more might be introduced in the future).


- `7988 &lt;https://github.com/pytest-dev/pytest/issues/7988&gt;`_: The ``pytest.yield_fixture`` decorator/function is now deprecated. Use :func:`pytest.fixture` instead.

  ``yield_fixture`` has been an alias for ``fixture`` for a very long time, so can be search/replaced safely.



Features
--------

- `5299 &lt;https://github.com/pytest-dev/pytest/issues/5299&gt;`_: pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python&gt;=3.8.
  See :ref:`unraisable` for more information.


- `7425 &lt;https://github.com/pytest-dev/pytest/issues/7425&gt;`_: New :fixture:`pytester` fixture, which is identical to :fixture:`testdir` but its methods return :class:`pathlib.Path` when appropriate instead of ``py.path.local``.

  This is part of the movement to use :class:`pathlib.Path` objects internally, in order to remove the dependency to ``py`` in the future.

  Internally, the old :class:`Testdir &lt;_pytest.pytester.Testdir&gt;` is now a thin wrapper around :class:`Pytester &lt;_pytest.pytester.Pytester&gt;`, preserving the old interface.


- `7695 &lt;https://github.com/pytest-dev/pytest/issues/7695&gt;`_: A new hook was added, `pytest_markeval_namespace` which should return a dictionary.
  This dictionary will be used to augment the &quot;global&quot; variables available to evaluate skipif/xfail/xpass markers.

  Pseudo example

  ``conftest.py``:

  .. code-block:: python

     def pytest_markeval_namespace():
         return {&quot;color&quot;: &quot;red&quot;}

  ``test_func.py``:

  .. code-block:: python

     pytest.mark.skipif(&quot;color == &#39;blue&#39;&quot;, reason=&quot;Color is not red&quot;)
     def test_func():
         assert False


- `8006 &lt;https://github.com/pytest-dev/pytest/issues/8006&gt;`_: It is now possible to construct a :class:`~pytest.MonkeyPatch` object directly as ``pytest.MonkeyPatch()``,
  in cases when the :fixture:`monkeypatch` fixture cannot be used. Previously some users imported it
  from the private `_pytest.monkeypatch.MonkeyPatch` namespace.

  Additionally, :meth:`MonkeyPatch.context &lt;pytest.MonkeyPatch.context&gt;` is now a classmethod,
  and can be used as ``with MonkeyPatch.context() as mp: ...``. This is the recommended way to use
  ``MonkeyPatch`` directly, since unlike the ``monkeypatch`` fixture, an instance created directly
  is not ``undo()``-ed automatically.



Improvements
------------

- `1265 &lt;https://github.com/pytest-dev/pytest/issues/1265&gt;`_: Added an ``__str__`` implementation to the :class:`~pytest.pytester.LineMatcher` class which is returned from ``pytester.run_pytest().stdout`` and similar. It returns the entire output, like the existing ``str()`` method.


- `2044 &lt;https://github.com/pytest-dev/pytest/issues/2044&gt;`_: Verbose mode now shows the reason that a test was skipped in the test&#39;s terminal line after the &quot;SKIPPED&quot;, &quot;XFAIL&quot; or &quot;XPASS&quot;.


- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_ The types of builtin pytest fixtures are now exported so they may be used in type annotations of test functions.
  The newly-exported types are:

  - ``pytest.FixtureRequest`` for the :fixture:`request` fixture.
  - ``pytest.Cache`` for the :fixture:`cache` fixture.
  - ``pytest.CaptureFixture[str]`` for the :fixture:`capfd` and :fixture:`capsys` fixtures.
  - ``pytest.CaptureFixture[bytes]`` for the :fixture:`capfdbinary` and :fixture:`capsysbinary` fixtures.
  - ``pytest.LogCaptureFixture`` for the :fixture:`caplog` fixture.
  - ``pytest.Pytester`` for the :fixture:`pytester` fixture.
  - ``pytest.Testdir`` for the :fixture:`testdir` fixture.
  - ``pytest.TempdirFactory`` for the :fixture:`tmpdir_factory` fixture.
  - ``pytest.TempPathFactory`` for the :fixture:`tmp_path_factory` fixture.
  - ``pytest.MonkeyPatch`` for the :fixture:`monkeypatch` fixture.
  - ``pytest.WarningsRecorder`` for the :fixture:`recwarn` fixture.

  Constructing them is not supported (except for `MonkeyPatch`); they are only meant for use in type annotations.
  Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.

  Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.


- `7527 &lt;https://github.com/pytest-dev/pytest/issues/7527&gt;`_: When a comparison between :func:`namedtuple &lt;collections.namedtuple&gt;` instances of the same type fails, pytest now shows the differing field names (possibly nested) instead of their indexes.


- `7615 &lt;https://github.com/pytest-dev/pytest/issues/7615&gt;`_: :meth:`Node.warn &lt;_pytest.nodes.Node.warn&gt;` now permits any subclass of :class:`Warning`, not just :class:`PytestWarning &lt;pytest.PytestWarning&gt;`.


- `7701 &lt;https://github.com/pytest-dev/pytest/issues/7701&gt;`_: Improved reporting when using ``--collected-only``. It will now show the number of collected tests in the summary stats.


- `7710 &lt;https://github.com/pytest-dev/pytest/issues/7710&gt;`_: Use strict equality comparison for non-numeric types in :func:`pytest.approx` instead of
  raising :class:`TypeError`.

  This was the undocumented behavior before 3.7, but is now officially a supported feature.


- `7938 &lt;https://github.com/pytest-dev/pytest/issues/7938&gt;`_: New ``--sw-skip`` argument which is a shorthand for ``--stepwise-skip``.


- `8023 &lt;https://github.com/pytest-dev/pytest/issues/8023&gt;`_: Added ``&#39;node_modules&#39;`` to default value for :confval:`norecursedirs`.


- `8032 &lt;https://github.com/pytest-dev/pytest/issues/8032&gt;`_: :meth:`doClassCleanups &lt;unittest.TestCase.doClassCleanups&gt;` (introduced in :mod:`unittest` in Python and 3.8) is now called appropriately.



Bug Fixes
---------

- `4824 &lt;https://github.com/pytest-dev/pytest/issues/4824&gt;`_: Fixed quadratic behavior and improved performance of collection of items using autouse fixtures and xunit fixtures.


- `7758 &lt;https://github.com/pytest-dev/pytest/issues/7758&gt;`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.


- `7911 &lt;https://github.com/pytest-dev/pytest/issues/7911&gt;`_: Directories created by by :fixture:`tmp_path` and :fixture:`tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.


- `7913 &lt;https://github.com/pytest-dev/pytest/issues/7913&gt;`_: Fixed a crash or hang in :meth:`pytester.spawn &lt;_pytest.pytester.Pytester.spawn&gt;` when the :mod:`readline` module is involved.


- `7951 &lt;https://github.com/pytest-dev/pytest/issues/7951&gt;`_: Fixed handling of recursive symlinks when collecting tests.


- `7981 &lt;https://github.com/pytest-dev/pytest/issues/7981&gt;`_: Fixed symlinked directories not being followed during collection. Regressed in pytest 6.1.0.


- `8016 &lt;https://github.com/pytest-dev/pytest/issues/8016&gt;`_: Fixed only one doctest being collected when using ``pytest --doctest-modules path/to/an/__init__.py``.



Improved Documentation
----------------------

- `7429 &lt;https://github.com/pytest-dev/pytest/issues/7429&gt;`_: Add more information and use cases about skipping doctests.


- `7780 &lt;https://github.com/pytest-dev/pytest/issues/7780&gt;`_: Classes which should not be inherited from are now marked ``final class`` in the API reference.


- `7872 &lt;https://github.com/pytest-dev/pytest/issues/7872&gt;`_: ``_pytest.config.argparsing.Parser.addini()`` accepts explicit ``None`` and ``&quot;string&quot;``.


- `7878 &lt;https://github.com/pytest-dev/pytest/issues/7878&gt;`_: In pull request section, ask to commit after editing changelog and authors file.



Trivial/Internal Changes
------------------------

- `7802 &lt;https://github.com/pytest-dev/pytest/issues/7802&gt;`_: The ``attrs`` dependency requirement is now &gt;=19.2.0 instead of &gt;=17.4.0.


- `8014 &lt;https://github.com/pytest-dev/pytest/issues/8014&gt;`_: `.pyc` files created by pytest&#39;s assertion rewriting now conform to the newer PEP-552 format on Python&gt;=3.7.
  (These files are internal and only interpreted by pytest itself.)
   ```
   
  
  
   ### 6.1.2
   ```
   =========================

Bug Fixes
---------

- `7758 &lt;https://github.com/pytest-dev/pytest/issues/7758&gt;`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.


- `7911 &lt;https://github.com/pytest-dev/pytest/issues/7911&gt;`_: Directories created by `tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.



Improved Documentation
----------------------

- `7815 &lt;https://github.com/pytest-dev/pytest/issues/7815&gt;`_: Improve deprecation warning message for ``pytest._fillfuncargs()``.
   ```
   
  
  
   ### 6.1.1
   ```
   =========================

Bug Fixes
---------

- `7807 &lt;https://github.com/pytest-dev/pytest/issues/7807&gt;`_: Fixed regression in pytest 6.1.0 causing incorrect rootdir to be determined in some non-trivial cases where parent directories have config files as well.


- `7814 &lt;https://github.com/pytest-dev/pytest/issues/7814&gt;`_: Fixed crash in header reporting when :confval:`testpaths` is used and contains absolute paths (regression in 6.1.0).
   ```
   
  
  
   ### 6.1.0
   ```
   =========================

Breaking Changes
----------------

- `5585 &lt;https://github.com/pytest-dev/pytest/issues/5585&gt;`_: As per our policy, the following features which have been deprecated in the 5.X series are now
  removed:

  * The ``funcargnames`` read-only property of ``FixtureRequest``, ``Metafunc``, and ``Function`` classes. Use ``fixturenames`` attribute.

  * ``pytest.fixture`` no longer supports positional arguments, pass all arguments by keyword instead.

  * Direct construction of ``Node`` subclasses now raise an error, use ``from_parent`` instead.

  * The default value for ``junit_family`` has changed to ``xunit2``. If you require the old format, add ``junit_family=xunit1`` to your configuration file.

  * The ``TerminalReporter`` no longer has a ``writer`` attribute. Plugin authors may use the public functions of the ``TerminalReporter`` instead of accessing the ``TerminalWriter`` object directly.

  * The ``--result-log`` option has been removed. Users are recommended to use the `pytest-reportlog &lt;https://github.com/pytest-dev/pytest-reportlog&gt;`__ plugin instead.


  For more information consult
  `Deprecations and Removals &lt;https://docs.pytest.org/en/stable/deprecations.html&gt;`__ in the docs.



Deprecations
------------

- `6981 &lt;https://github.com/pytest-dev/pytest/issues/6981&gt;`_: The ``pytest.collect`` module is deprecated: all its names can be imported from ``pytest`` directly.


- `7097 &lt;https://github.com/pytest-dev/pytest/issues/7097&gt;`_: The ``pytest._fillfuncargs`` function is deprecated. This function was kept
  for backward compatibility with an older plugin.

  It&#39;s functionality is not meant to be used directly, but if you must replace
  it, use `function._request._fillfixtures()` instead, though note this is not
  a public API and may break in the future.


- `7210 &lt;https://github.com/pytest-dev/pytest/issues/7210&gt;`_: The special ``-k &#39;-expr&#39;`` syntax to ``-k`` is deprecated. Use ``-k &#39;not expr&#39;``
  instead.

  The special ``-k &#39;expr:&#39;`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.


- `7255 &lt;https://github.com/pytest-dev/pytest/issues/7255&gt;`_: The :func:`pytest_warning_captured &lt;_pytest.hookspec.pytest_warning_captured&gt;` hook is deprecated in favor
  of :func:`pytest_warning_recorded &lt;_pytest.hookspec.pytest_warning_recorded&gt;`, and will be removed in a future version.


- `7648 &lt;https://github.com/pytest-dev/pytest/issues/7648&gt;`_: The ``gethookproxy()`` and ``isinitpath()`` methods of ``FSCollector`` and ``Package`` are deprecated;
  use ``self.session.gethookproxy()`` and ``self.session.isinitpath()`` instead.
  This should work on all pytest versions.



Features
--------

- `7667 &lt;https://github.com/pytest-dev/pytest/issues/7667&gt;`_: New ``--durations-min`` command-line flag controls the minimal duration for inclusion in the slowest list of tests shown by ``--durations``. Previously this was hard-coded to ``0.005s``.



Improvements
------------

- `6681 &lt;https://github.com/pytest-dev/pytest/issues/6681&gt;`_: Internal pytest warnings issued during the early stages of initialization are now properly handled and can filtered through :confval:`filterwarnings` or ``--pythonwarnings/-W``.

  This also fixes a number of long standing issues: `2891 &lt;https://github.com/pytest-dev/pytest/issues/2891&gt;`__, `#7620 &lt;https://github.com/pytest-dev/pytest/issues/7620&gt;`__, `#7426 &lt;https://github.com/pytest-dev/pytest/issues/7426&gt;`__.


- `7572 &lt;https://github.com/pytest-dev/pytest/issues/7572&gt;`_: When a plugin listed in ``required_plugins`` is missing or an unknown config key is used with ``--strict-config``, a simple error message is now shown instead of a stacktrace.


- `7685 &lt;https://github.com/pytest-dev/pytest/issues/7685&gt;`_: Added two new attributes :attr:`rootpath &lt;_pytest.config.Config.rootpath&gt;` and :attr:`inipath &lt;_pytest.config.Config.inipath&gt;` to :class:`Config &lt;_pytest.config.Config&gt;`.
  These attributes are :class:`pathlib.Path` versions of the existing :attr:`rootdir &lt;_pytest.config.Config.rootdir&gt;` and :attr:`inifile &lt;_pytest.config.Config.inifile&gt;` attributes,
  and should be preferred over them when possible.


- `7780 &lt;https://github.com/pytest-dev/pytest/issues/7780&gt;`_: Public classes which are not designed to be inherited from are now marked `final &lt;https://docs.python.org/3/library/typing.html#typing.final&gt;`_.
  Code which inherits from these classes will trigger a type-checking (e.g. mypy) error, but will still work in runtime.
  Currently the ``final`` designation does not appear in the API Reference but hopefully will in the future.



Bug Fixes
---------

- `1953 &lt;https://github.com/pytest-dev/pytest/issues/1953&gt;`_: Fixed error when overwriting a parametrized fixture, while also reusing the super fixture value.

  .. code-block:: python

       conftest.py
      import pytest


      pytest.fixture(params=[1, 2])
      def foo(request):
          return request.param


       test_foo.py
      import pytest


      pytest.fixture
      def foo(foo):
          return foo * 2


- `4984 &lt;https://github.com/pytest-dev/pytest/issues/4984&gt;`_: Fixed an internal error crash with ``IndexError: list index out of range`` when
  collecting a module which starts with a decorated function, the decorator
  raises, and assertion rewriting is enabled.


- `7591 &lt;https://github.com/pytest-dev/pytest/issues/7591&gt;`_: pylint shouldn&#39;t complain anymore about unimplemented abstract methods when inheriting from :ref:`File &lt;non-python tests&gt;`.


- `7628 &lt;https://github.com/pytest-dev/pytest/issues/7628&gt;`_: Fixed test collection when a full path without a drive letter was passed to pytest on Windows (for example ``\projects\tests\test.py`` instead of ``c:\projects\tests\pytest.py``).


- `7638 &lt;https://github.com/pytest-dev/pytest/issues/7638&gt;`_: Fix handling of command-line options that appear as paths but trigger an OS-level syntax error on Windows, such as the options used internally by ``pytest-xdist``.


- `7742 &lt;https://github.com/pytest-dev/pytest/issues/7742&gt;`_: Fixed INTERNALERROR when accessing locals / globals with faulty ``exec``.



Improved Documentation
----------------------

- `1477 &lt;https://github.com/pytest-dev/pytest/issues/1477&gt;`_: Removed faq.rst and its reference in contents.rst.



Trivial/Internal Changes
------------------------

- `7536 &lt;https://github.com/pytest-dev/pytest/issues/7536&gt;`_: The internal ``junitxml`` plugin has rewritten to use ``xml.etree.ElementTree``.
  The order of attributes in XML elements might differ. Some unneeded escaping is
  no longer performed.


- `7587 &lt;https://github.com/pytest-dev/pytest/issues/7587&gt;`_: The dependency on the ``more-itertools`` package has been removed.


- `7631 &lt;https://github.com/pytest-dev/pytest/issues/7631&gt;`_: The result type of :meth:`capfd.readouterr() &lt;_pytest.capture.CaptureFixture.readouterr&gt;` (and similar) is no longer a namedtuple,
  but should behave like one in all respects. This was done for technical reasons.


- `7671 &lt;https://github.com/pytest-dev/pytest/issues/7671&gt;`_: When collecting tests, pytest finds test classes and functions by examining the
  attributes of python objects (modules, classes and instances). To speed up this
  process, pytest now ignores builtin attributes (like ``__class__``,
  ``__delattr__`` and ``__new__``) without consulting the :confval:`python_classes` and
  :confval:`python_functions` configuration options and without passing them to plugins
  using the :func:`pytest_pycollect_makeitem &lt;_pytest.hookspec.pytest_pycollect_makeitem&gt;` hook.
   ```
   
  
  
   ### 6.0.2
   ```
   =========================

Bug Fixes
---------

- `7148 &lt;https://github.com/pytest-dev/pytest/issues/7148&gt;`_: Fixed ``--log-cli`` potentially causing unrelated ``print`` output to be swallowed.


- `7672 &lt;https://github.com/pytest-dev/pytest/issues/7672&gt;`_: Fixed log-capturing level restored incorrectly if ``caplog.set_level`` is called more than once.


- `7686 &lt;https://github.com/pytest-dev/pytest/issues/7686&gt;`_: Fixed `NotSetType.token` being used as the parameter ID when the parametrization list is empty.
  Regressed in pytest 6.0.0.


- `7707 &lt;https://github.com/pytest-dev/pytest/issues/7707&gt;`_: Fix internal error when handling some exceptions that contain multiple lines or the style uses multiple lines (``--tb=line`` for example).
   ```
   
  
  
   ### 6.0.1
   ```
   =========================

Bug Fixes
---------

- `7394 &lt;https://github.com/pytest-dev/pytest/issues/7394&gt;`_: Passing an empty ``help`` value to ``Parser.add_option`` is now accepted instead of crashing when running ``pytest --help``.
  Passing ``None`` raises a more informative ``TypeError``.


- `7558 &lt;https://github.com/pytest-dev/pytest/issues/7558&gt;`_: Fix pylint ``not-callable`` lint on ``pytest.mark.parametrize()`` and the other builtin marks:
  ``skip``, ``skipif``, ``xfail``, ``usefixtures``, ``filterwarnings``.


- `7559 &lt;https://github.com/pytest-dev/pytest/issues/7559&gt;`_: Fix regression in plugins using ``TestReport.longreprtext`` (such as ``pytest-html``) when ``TestReport.longrepr`` is not a string.


- `7569 &lt;https://github.com/pytest-dev/pytest/issues/7569&gt;`_: Fix logging capture handler&#39;s level not reset on teardown after a call to ``caplog.set_level()``.
   ```
   
  
  
   ### 6.0.0
   ```
   =========================

(**Please see the full set of changes for this release also in the 6.0.0rc1 notes below**)

Breaking Changes
----------------

- `5584 &lt;https://github.com/pytest-dev/pytest/issues/5584&gt;`_: **PytestDeprecationWarning are now errors by default.**

  Following our plan to remove deprecated features with as little disruption as
  possible, all warnings of type ``PytestDeprecationWarning`` now generate errors
  instead of warning messages.

  **The affected features will be effectively removed in pytest 6.1**, so please consult the
  `Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`__
  section in the docs for directions on how to update existing code.

  In the pytest ``6.0.X`` series, it is possible to change the errors back into warnings as a
  stopgap measure by adding this to your ``pytest.ini`` file:

  .. code-block:: ini

      [pytest]
      filterwarnings =
          ignore::pytest.PytestDeprecationWarning

  But this will stop working when pytest ``6.1`` is released.

  **If you have concerns** about the removal of a specific feature, please add a
  comment to `5584 &lt;https://github.com/pytest-dev/pytest/issues/5584&gt;`__.


- `7472 &lt;https://github.com/pytest-dev/pytest/issues/7472&gt;`_: The ``exec_()`` and ``is_true()`` methods of ``_pytest._code.Frame`` have been removed.



Features
--------

- `7464 &lt;https://github.com/pytest-dev/pytest/issues/7464&gt;`_: Added support for :envvar:`NO_COLOR` and :envvar:`FORCE_COLOR` environment variables to control colored output.



Improvements
------------

- `7467 &lt;https://github.com/pytest-dev/pytest/issues/7467&gt;`_: ``--log-file`` CLI option and ``log_file`` ini marker now create subdirectories if needed.


- `7489 &lt;https://github.com/pytest-dev/pytest/issues/7489&gt;`_: The :func:`pytest.raises` function has a clearer error message when ``match`` equals the obtained string but is not a regex match. In this case it is suggested to escape the regex.



Bug Fixes
---------

- `7392 &lt;https://github.com/pytest-dev/pytest/issues/7392&gt;`_: Fix the reported location of tests skipped with ``pytest.mark.skip`` when ``--runxfail`` is used.


- `7491 &lt;https://github.com/pytest-dev/pytest/issues/7491&gt;`_: :fixture:`tmpdir` and :fixture:`tmp_path` no longer raise an error if the lock to check for
  stale temporary directories is not accessible.


- `7517 &lt;https://github.com/pytest-dev/pytest/issues/7517&gt;`_: Preserve line endings when captured via ``capfd``.


- `7534 &lt;https://github.com/pytest-dev/pytest/issues/7534&gt;`_: Restored the previous formatting of ``TracebackEntry.__str__`` which was changed by accident.



Improved Documentation
----------------------

- `7422 &lt;https://github.com/pytest-dev/pytest/issues/7422&gt;`_: Clarified when the ``usefixtures`` mark can apply fixtures to test.


- `7441 &lt;https://github.com/pytest-dev/pytest/issues/7441&gt;`_: Add a note about ``-q`` option used in getting started guide.



Trivial/Internal Changes
------------------------

- `7389 &lt;https://github.com/pytest-dev/pytest/issues/7389&gt;`_: Fixture scope ``package`` is no longer considered experimental.
   ```
   
  
  
   ### 6.0.0rc1
   ```
   ============================

Breaking Changes
----------------

- `1316 &lt;https://github.com/pytest-dev/pytest/issues/1316&gt;`_: ``TestReport.longrepr`` is now always an instance of ``ReprExceptionInfo``. Previously it was a ``str`` when a test failed with ``pytest.fail(..., pytrace=False)``.


- `5965 &lt;https://github.com/pytest-dev/pytest/issues/5965&gt;`_: symlinks are no longer resolved during collection and matching `conftest.py` files with test file paths.

  Resolving symlinks for the current directory and during collection was introduced as a bugfix in 3.9.0, but it actually is a new feature which had unfortunate consequences in Windows and surprising results in other platforms.

  The team decided to step back on resolving symlinks at all, planning to review this in the future with a more solid solution (see discussion in
  `6523 &lt;https://github.com/pytest-dev/pytest/pull/6523&gt;`__ for details).

  This might break test suites which made use of this feature; the fix is to create a symlink
  for the entire test tree, and not only to partial files/tress as it was possible previously.


- `6505 &lt;https://github.com/pytest-dev/pytest/issues/6505&gt;`_: ``Testdir.run().parseoutcomes()`` now always returns the parsed nouns in plural form.

  Originally ``parseoutcomes()`` would always returns the nouns in plural form, but a change
  meant to improve the terminal summary by using singular form single items (``1 warning`` or ``1 error``)
  caused an unintended regression by changing the keys returned by ``parseoutcomes()``.

  Now the API guarantees to always return the plural form, so calls like this:

  .. code-block:: python

      result = testdir.runpytest()
      result.assert_outcomes(error=1)

  Need to be changed to:


  .. code-block:: python

      result = testdir.runpytest()
      result.assert_outcomes(errors=1)


- `6903 &lt;https://github.com/pytest-dev/pytest/issues/6903&gt;`_: The ``os.dup()`` function is now assumed to exist. We are not aware of any
  supported Python 3 implementations which do not provide it.


- `7040 &lt;https://github.com/pytest-dev/pytest/issues/7040&gt;`_: ``-k`` no longer matches against the names of the directories outside the test session root.

  Also, ``pytest.Package.name`` is now just the name of the directory containing the package&#39;s
  ``__init__.py`` file, instead of the full path. This is consistent with how the other nodes
  are named, and also one of the reasons why ``-k`` would match against any directory containing
  the test suite.


- `7122 &lt;https://github.com/pytest-dev/pytest/issues/7122&gt;`_: Expressions given to the ``-m`` and ``-k`` options are no longer evaluated using Python&#39;s :func:`eval`.
  The format supports ``or``, ``and``, ``not``, parenthesis and general identifiers to match against.
  Python constants, keywords or other operators are no longer evaluated differently.


- `7135 &lt;https://github.com/pytest-dev/pytest/issues/7135&gt;`_: Pytest now uses its own ``TerminalWriter`` class instead of using the one from the ``py`` library.
  Plugins generally access this class through ``TerminalReporter.writer``, ``TerminalReporter.write()``
  (and similar methods), or ``_pytest.config.create_terminal_writer()``.

  The following breaking changes were made:

  - Output (``write()`` method and others) no longer flush implicitly; the flushing behavior
    of the underlying file is respected. To flush explicitly (for example, if you
    want output to be shown before an end-of-line is printed), use ``write(flush=True)`` or
    ``terminal_writer.flush()``.
  - Explicit Windows console support was removed, delegated to the colorama library.
  - Support for writing ``bytes`` was removed.
  - The ``reline`` method and ``chars_on_current_line`` property were removed.
  - The ``stringio`` and ``encoding`` arguments was removed.
  - Support for passing a callable instead of a file was removed.


- `7224 &lt;https://github.com/pytest-dev/pytest/issues/7224&gt;`_: The `item.catch_log_handler` and `item.catch_log_handlers` attributes, set by the
  logging plugin and never meant to be public, are no longer available.

  The deprecated ``--no-print-logs`` option and ``log_print`` ini option are removed. Use ``--show-capture`` instead.


- `7226 &lt;https://github.com/pytest-dev/pytest/issues/7226&gt;`_: Removed the unused ``args`` parameter from ``pytest.Function.__init__``.


- `7418 &lt;https://github.com/pytest-dev/pytest/issues/7418&gt;`_: Removed the `pytest_doctest_prepare_content` hook specification. This hook
  hasn&#39;t been triggered by pytest for at least 10 years.


- `7438 &lt;https://github.com/pytest-dev/pytest/issues/7438&gt;`_: Some changes were made to the internal ``_pytest._code.source``, listed here
  for the benefit of plugin authors who may be using it:

  - The ``deindent`` argument to ``Source()`` has been removed, now it is always true.
  - Support for zero or multiple arguments to ``Source()`` has been removed.
  - Support for comparing ``Source`` with an ``str`` has been removed.
  - The methods ``Source.isparseable()`` and ``Source.putaround()`` have been removed.
  - The method ``Source.compile()`` and function ``_pytest._code.compile()`` have
    been removed; use plain ``compile()`` instead.
  - The function ``_pytest._code.source.getsource()`` has been removed; use
    ``Source()`` directly instead.



Deprecations
------------

- `7210 &lt;https://github.com/pytest-dev/pytest/issues/7210&gt;`_: The special ``-k &#39;-expr&#39;`` syntax to ``-k`` is deprecated. Use ``-k &#39;not expr&#39;``
  instead.

  The special ``-k &#39;expr:&#39;`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.

- `4049 &lt;https://github.com/pytest-dev/pytest/issues/4049&gt;`_: ``pytest_warning_captured`` is deprecated in favor of the ``pytest_warning_recorded`` hook.


Features
--------

- `1556 &lt;https://github.com/pytest-dev/pytest/issues/1556&gt;`_: pytest now supports ``pyproject.toml`` files for configuration.

  The configuration options is similar to the one available in other formats, but must be defined
  in a ``[tool.pytest.ini_options]`` table to be picked up by pytest:

  .. code-block:: toml

       pyproject.toml
      [tool.pytest.ini_options]
      minversion = &quot;6.0&quot;
      addopts = &quot;-ra -q&quot;
      testpaths = [
          &quot;tests&quot;,
          &quot;integration&quot;,
      ]

  More information can be found `in the docs &lt;https://docs.pytest.org/en/stable/customize.html#configuration-file-formats&gt;`__.


- `3342 &lt;https://github.com/pytest-dev/pytest/issues/3342&gt;`_: pytest now includes inline type annotations and exposes them to user programs.
  Most of the user-facing API is covered, as well as internal code.

  If you are running a type checker such as mypy on your tests, you may start
  noticing type errors indicating incorrect usage. If you run into an error that
  you believe to be incorrect, please let us know in an issue.

  The types were developed against mypy version 0.780. Versions before 0.750
  are known not to work. We recommend using the latest version. Other type
  checkers may work as well, but they are not officially verified to work by
  pytest yet.


- `4049 &lt;https://github.com/pytest-dev/pytest/issues/4049&gt;`_: Introduced a new hook named `pytest_warning_recorded` to convey information about warnings captured by the internal `pytest` warnings plugin.

  This hook is meant to replace `pytest_warning_captured`, which is deprecated and will be removed in a future release.


- `6471 &lt;https://github.com/pytest-dev/pytest/issues/6471&gt;`_: New command-line flags:

  * `--no-header`: disables the initial header, including platform, version, and plugins.
  * `--no-summary`: disables the final test summary, including warnings.


- `6856 &lt;https://github.com/pytest-dev/pytest/issues/6856&gt;`_: A warning is now shown when an unknown key is read from a config INI file.

  The `--strict-config` flag has been added to treat these warnings as errors.


- `6906 &lt;https://github.com/pytest-dev/pytest/issues/6906&gt;`_: Added `--code-highlight` command line option to enable/disable code highlighting in terminal output.


- `7245 &lt;https://github.com/pytest-dev/pytest/issues/7245&gt;`_: New ``--import-mode=importlib`` option that uses `importlib &lt;https://docs.python.org/3/library/importlib.html&gt;`__ to import test modules.

  Traditionally pytest used ``__import__`` while changing ``sys.path`` to import test modules (which
  also changes ``sys.modules`` as a side-effect), which works but has a number of drawbacks, like requiring test modules
  that don&#39;t live in packages to have unique names (as they need to reside under a unique name in ``sys.modules``).

  ``--import-mode=importlib`` uses more fine grained import mechanisms from ``importlib`` which don&#39;t
  require pytest to change ``sys.path`` or ``sys.modules`` at all, eliminating much of the drawbacks
  of the previous mode.

  We intend to make ``--import-mode=importlib`` the default in future versions, so users are encouraged
  to try the new mode and provide feedback (both positive or negative) in issue `7245 &lt;https://github.com/pytest-dev/pytest/issues/7245&gt;`__.

  You can read more about this option in `the documentation &lt;https://docs.pytest.org/en/latest/pythonpath.html#import-modes&gt;`__.


- `7305 &lt;https://github.com/pytest-dev/pytest/issues/7305&gt;`_: New ``required_plugins`` configuration option allows the user to specify a list of plugins, including version information, that are required for pytest to run. An error is raised if any required plugins are not found when running pytest.


Improvements
------------

- `4375 &lt;https://github.com/pytest-dev/pytest/issues/4375&gt;`_: The ``pytest`` command now suppresses the ``BrokenPipeError`` error message that
  is printed to stderr when the output of ``pytest`` is piped and and the pipe is
  closed by the piped-to program (common examples are ``less`` and ``head``).


- `4391 &lt;https://github.com/pytest-dev/pytest/issues/4391&gt;`_: Improved precision of test durations measurement. ``CallInfo`` items now have a new ``&lt;CallInfo&gt;.duration`` attribute, created using ``time.perf_counter()``. This attribute is used to fill the ``&lt;TestReport&gt;.duration`` attribute, which is more accurate than the previous ``&lt;CallInfo&gt;.stop - &lt;CallInfo&gt;.start`` (as these are based on ``time.time()``).


- `4675 &lt;https://github.com/pytest-dev/pytest/issues/4675&gt;`_: Rich comparison for dataclasses and `attrs`-classes is now recursive.


- `6285 &lt;https://github.com/pytest-dev/pytest/issues/6285&gt;`_: Exposed the `pytest.FixtureLookupError` exception which is raised by `request.getfixturevalue()`
  (where `request` is a `FixtureRequest` fixture) when a fixture with the given name cannot be returned.


- `6433 &lt;https://github.com/pytest-dev/pytest/issues/6433&gt;`_: If an error is encountered while formatting the message in a logging call, for
  example ``logging.warning(&quot;oh no!: %s: %s&quot;, &quot;first&quot;)`` (a second argument is
  missing), pytest now propagates the error, likely causing the test to fail.

  Previously, such a mistake would cause an error to be printed to stderr, which
  is not displayed by default for passing tests. This change makes the mistake
  visible during testing.

  You may supress this behavior temporarily or permanently by setting
  ``logging.raiseExceptions = False``.


- `6817 &lt;https://github.com/pytest-dev/pytest/issues/6817&gt;`_: Explicit new-lines in help texts of command-line options are preserved, allowing plugins better control
  of the help displayed to users.


- `6940 &lt;https://github.com/pytest-dev/pytest/issues/6940&gt;`_: When using the ``--duration`` option, the terminal message output is now more precise about the number and duration of hidden items.


- `6991 &lt;https://github.com/pytest-dev/pytest/issues/6991&gt;`_: Collected files are displayed after any reports from hooks, e.g. the status from ``--lf``.


- `7091 &lt;https://github.com/pytest-dev/pytest/issues/7091&gt;`_: When ``fd`` capturing is used, through ``--capture=fd`` or the ``capfd`` and
  ``capfdbinary`` fixtures, and the file descriptor (0, 1, 2) cannot be
  duplicated, FD capturing is still performed. Previously, direct writes to the
  file descriptors would fail or be lost in this case.


- `7119 &lt;https://github.com/pytest-dev/pytest/issues/7119&gt;`_: Exit with an error if the ``--basetemp`` argument is empty, is the current working directory or is one of the parent directories.
  This is done to protect against accidental data loss, as any directory passed to this argument is cleared.


- `7128 &lt;https://github.com/pytest-dev/pytest/issues/7128&gt;`_: `pytest --version` now displays just the pytest version, while `pytest --version --version` displays more verbose information including plugins. This is more consistent with how other tools show `--version`.


- `7133 &lt;https://github.com/pytest-dev/pytest/issues/7133&gt;`_: :meth:`caplog.set_level() &lt;_pytest.logging.LogCaptureFixture.set_level&gt;` will now override any :confval:`log_level` set via the CLI or configuration file.


- `7159 &lt;https://github.com/pytest-dev/pytest/issues/7159&gt;`_: :meth:`caplog.set_level() &lt;_pytest.logging.LogCaptureFixture.set_level&gt;` and :meth:`caplog.at_level() &lt;_pytest.logging.LogCaptureFixture.at_level&gt;` no longer affect
  the level of logs that are shown in the *Captured log report* report section.


- `7348 &lt;https://github.com/pytest-dev/pytest/issues/7348&gt;`_: Improve recursive diff report for comparison asserts on dataclasses / attrs.


- `7385 &lt;https://github.com/pytest-dev/pytest/issues/7385&gt;`_: ``--junitxml`` now includes the exception cause in the ``message`` XML attribute for failures during setup and teardown.

  Previously:

  .. code-block:: xml

      &lt;error message=&quot;test setup failure&quot;&gt;

  Now:

  .. code-block:: xml

      &lt;error message=&quot;failed on setup with &amp;quot;ValueError: Some error during setup&amp;quot;&quot;&gt;



Bug Fixes
---------

- `1120 &lt;https://github.com/pytest-dev/pytest/issues/1120&gt;`_: Fix issue where directories from :fixture:`tmpdir` are not removed properly when multiple instances of pytest are running in parallel.


- `4583 &lt;https://github.com/pytest-dev/pytest/issues/4583&gt;`_: Prevent crashing and provide a user-friendly error when a marker expression (`-m`) invoking of :func:`eval` raises any exception.


- `4677 &lt;https://github.com/pytest-dev/pytest/issues/4677&gt;`_: The path shown in the summary report for SKIPPED tests is now always relative. Previously it was sometimes absolute.


- `5456 &lt;https://github.com/pytest-dev/pytest/issues/5456&gt;`_: Fix a possible race condition when trying to remove lock files used to control access to folders
  created by :fixture:`tmp_path` and :fixture:`tmpdir`.


- `6240 &lt;https://github.com/pytest-dev/pytest/issues/6240&gt;`_: Fixes an issue where logging during collection step caused duplication of log
  messages to stderr.


- `6428 &lt;https://github.com/pytest-dev/pytest/issues/6428&gt;`_: Paths appearing in error messages are now correct in case the current working directory has
  changed since the start of the session.


- `6755 &lt;https://github.com/pytest-dev/pytest/issues/6755&gt;`_: Support deleting paths longer than 260 characters on windows created inside :fixture:`tmpdir`.


- `6871 &lt;https://github.com/pytest-dev/pytest/issues/6871&gt;`_: Fix crash with captured output when using :fixture:`capsysbinary`.


- `6909 &lt;https://github.com/pytest-dev/pytest/issues/6909&gt;`_: Revert the change introduced by `#6330 &lt;https://github.com/pytest-dev/pytest/pull/6330&gt;`_, which required all arguments to ``pytest.mark.parametrize`` to be explicitly defined in the function signature.

  The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.


- `6910 &lt;https://github.com/pytest-dev/pytest/issues/6910&gt;`_: Fix crash when plugins return an unknown stats while using the ``--reportlog`` option.


- `6924 &lt;https://github.com/pytest-dev/pytest/issues/6924&gt;`_: Ensure a ``unittest.IsolatedAsyncioTestCase`` is actually awaited.


- `6925 &lt;https://github.com/pytest-dev/pytest/issues/6925&gt;`_: Fix `TerminalRepr` instances to be hashable again.


- `6947 &lt;https://github.com/pytest-dev/pytest/issues/6947&gt;`_: Fix regression where functions registered with :meth:`unittest.TestCase.addCleanup` were not being called on test failures.


- `6951 &lt;https://github.com/pytest-dev/pytest/issues/6951&gt;`_: Allow users to still set the deprecated ``TerminalReporter.writer`` attribute.


- `6956 &lt;https://github.com/pytest-dev/pytest/issues/6956&gt;`_: Prevent pytest from printing `ConftestImportFailure` traceback to stdout.


- `6991 &lt;https://github.com/pytest-dev/pytest/issues/6991&gt;`_: Fix regressions with `--lf` filtering too much since pytest 5.4.


- `6992 &lt;https://github.com/pytest-dev/pytest/issues/6992&gt;`_: Revert &quot;tmpdir: clean up indirection via config for factories&quot; `#6767 &lt;https://github.com/pytest-dev/pytest/issues/6767&gt;`_ as it breaks pytest-xdist.


- `7061 &lt;https://github.com/pytest-dev/pytest/issues/7061&gt;`_: When a yielding fixture fails to yield a value, report a test setup error instead of crashing.


- `7076 &lt;https://github.com/pytest-dev/pytest/issues/7076&gt;`_: The path of file skipped by ``pytest.mark.skip`` in the SKIPPED report is now relative to invocation directory. Previously it was relative to root directory.


- `7110 &lt;https://github.com/pytest-dev/pytest/issues/7110&gt;`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.


- `7126 &lt;https://github.com/pytest-dev/pytest/issues/7126&gt;`_: ``--setup-show`` now doesn&#39;t raise an error when a bytes value is used as a ``parametrize``
  parameter when Python is called with the ``-bb`` flag.


- `7143 &lt;https://github.com/pytest-dev/pytest/issues/7143&gt;`_: Fix :meth:`pytest.File.from_parent` so it forwards extra keyword arguments to the constructor.


- `7145 &lt;https://github.com/pytest-dev/pytest/issues/7145&gt;`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.


- `7150 &lt;https://github.com/pytest-dev/pytest/issues/7150&gt;`_: Prevent hiding the underlying exception when ``ConfTestImportFailure`` is raised.


- `7180 &lt;https://github.com/pytest-dev/pytest/issues/7180&gt;`_: Fix ``_is_setup_py`` for files encoded differently than locale.


- `7215 &lt;https://github.com/pytest-dev/pytest/issues/7215&gt;`_: Fix regression where running with ``--pdb`` would call :meth:`unittest.TestCase.tearDown` for skipped tests.


- `7253 &lt;https://github.com/pytest-dev/pytest/issues/7253&gt;`_: When using ``pytest.fixture`` on a function directly, as in ``pytest.fixture(func)``,
  if the ``autouse`` or ``params`` arguments are also passed, the function is no longer
  ignored, but is marked as a fixture.


- `7360 &lt;https://github.com/pytest-dev/pytest/issues/7360&gt;`_: Fix possibly incorrect evaluation of string expressions passed to ``pytest.mark.skipif`` and ``pytest.mark.xfail``,
  in rare circumstances where the exact same string is used but refers to different global values.


- `7383 &lt;https://github.com/pytest-dev/pytest/issues/7383&gt;`_: Fixed exception causes all over the codebase, i.e. use `raise new_exception from old_exception` when wrapping an exception.



Improved Documentation
----------------------

- `7202 &lt;https://github.com/pytest-dev/pytest/issues/7202&gt;`_: The development guide now links to the contributing section of the docs and `RELEASING.rst` on GitHub.


- `7233 &lt;https://github.com/pytest-dev/pytest/issues/7233&gt;`_: Add a note about ``--strict`` and ``--strict-markers`` and the preference for the latter one.


- `7345 &lt;https://github.com/pytest-dev/pytest/issues/7345&gt;`_: Explain indirect parametrization and markers for fixtures.



Trivial/Internal Changes
------------------------

- `7035 &lt;https://github.com/pytest-dev/pytest/issues/7035&gt;`_: The ``originalname`` attribute of ``_pytest.python.Function`` now defaults to ``name`` if not
  provided explicitly, and is always set.


- `7264 &lt;https://github.com/pytest-dev/pytest/issues/7264&gt;`_: The dependency on the ``wcwidth`` package has been removed.


- `7291 &lt;https://github.com/pytest-dev/pytest/issues/7291&gt;`_: Replaced ``py.iniconfig`` with `iniconfig &lt;https://pypi.org/project/iniconfig/&gt;`__.


- `7295 &lt;https://github.com/pytest-dev/pytest/issues/7295&gt;`_: ``src/_pytest/config/__init__.py`` now uses the ``warnings`` module to report warnings instead of ``sys.stderr.write``.


- `7356 &lt;https://github.com/pytest-dev/pytest/issues/7356&gt;`_: Remove last internal uses of deprecated *slave* term from old ``pytest-xdist``.


- `7357 &lt;https://github.com/pytest-dev/pytest/issues/7357&gt;`_: ``py``&gt;=1.8.2 is now required.
   ```
   
  
  
   ### 5.4.3
   ```
   =========================

Bug Fixes
---------

- `6428 &lt;https://github.com/pytest-dev/pytest/issues/6428&gt;`_: Paths appearing in error messages are now correct in case the current working directory has
  changed since the start of the session.


- `6755 &lt;https://github.com/pytest-dev/pytest/issues/6755&gt;`_: Support deleting paths longer than 260 characters on windows created inside tmpdir.


- `6956 &lt;https://github.com/pytest-dev/pytest/issues/6956&gt;`_: Prevent pytest from printing ConftestImportFailure traceback to stdout.


- `7150 &lt;https://github.com/pytest-dev/pytest/issues/7150&gt;`_: Prevent hiding the underlying exception when ``ConfTestImportFailure`` is raised.


- `7215 &lt;https://github.com/pytest-dev/pytest/issues/7215&gt;`_: Fix regression where running with ``--pdb`` would call the ``tearDown`` methods of ``unittest.TestCase``
  subclasses for skipped tests.
   ```
   
  
  
   ### 5.4.2
   ```
   =========================

Bug Fixes
---------

- `6871 &lt;https://github.com/pytest-dev/pytest/issues/6871&gt;`_: Fix crash with captured output when using the :fixture:`capsysbinary fixture &lt;capsysbinary&gt;`.


- `6924 &lt;https://github.com/pytest-dev/pytest/issues/6924&gt;`_: Ensure a ``unittest.IsolatedAsyncioTestCase`` is actually awaited.


- `6925 &lt;https://github.com/pytest-dev/pytest/issues/6925&gt;`_: Fix TerminalRepr instances to be hashable again.


- `6947 &lt;https://github.com/pytest-dev/pytest/issues/6947&gt;`_: Fix regression where functions registered with ``TestCase.addCleanup`` were not being called on test failures.


- `6951 &lt;https://github.com/pytest-dev/pytest/issues/6951&gt;`_: Allow users to still set the deprecated ``TerminalReporter.writer`` attribute.


- `6992 &lt;https://github.com/pytest-dev/pytest/issues/6992&gt;`_: Revert &quot;tmpdir: clean up indirection via config for factories&quot; #6767 as it breaks pytest-xdist.


- `7110 &lt;https://github.com/pytest-dev/pytest/issues/7110&gt;`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.


- `7143 &lt;https://github.com/pytest-dev/pytest/issues/7143&gt;`_: Fix ``File.from_parent`` so it forwards extra keyword arguments to the constructor.


- `7145 &lt;https://github.com/pytest-dev/pytest/issues/7145&gt;`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.


- `7180 &lt;https://github.com/pytest-dev/pytest/issues/7180&gt;`_: Fix ``_is_setup_py`` for files encoded differently than locale.
   ```
   
  
  
   ### 5.4.1
   ```
   =========================

Bug Fixes
---------

- `6909 &lt;https://github.com/pytest-dev/pytest/issues/6909&gt;`_: Revert the change introduced by `#6330 &lt;https://github.com/pytest-dev/pytest/pull/6330&gt;`_, which required all arguments to ``pytest.mark.parametrize`` to be explicitly defined in the function signature.

  The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.


- `6910 &lt;https://github.com/pytest-dev/pytest/issues/6910&gt;`_: Fix crash when plugins return an unknown stats while using the ``--reportlog`` option.
   ```
   
  
  
   ### 5.4.0
   ```
   =========================

Breaking Changes
----------------

- `6316 &lt;https://github.com/pytest-dev/pytest/issues/6316&gt;`_: Matching of ``-k EXPRESSION`` to test names is now case-insensitive.


- `6443 &lt;https://github.com/pytest-dev/pytest/issues/6443&gt;`_: Plugins specified with ``-p`` are now loaded after internal plugins, which results in their hooks being called *before* the internal ones.

  This makes the ``-p`` behavior consistent with ``PYTEST_PLUGINS``.


- `6637 &lt;https://github.com/pytest-dev/pytest/issues/6637&gt;`_: Removed the long-deprecated ``pytest_itemstart`` hook.

  This hook has been marked as deprecated and not been even called by pytest for over 10 years now.


- `6673 &lt;https://github.com/pytest-dev/pytest/issues/6673&gt;`_: Reversed / fix meaning of &quot;+/-&quot; in error diffs.  &quot;-&quot; means that sth. expected is missing in the result and &quot;+&quot; means that there are unexpected extras in the result.


- `6737 &lt;https://github.com/pytest-dev/pytest/issues/6737&gt;`_: The ``cached_result`` attribute of ``FixtureDef`` is now set to ``None`` when
  the result is unavailable, instead of being deleted.

  If your plugin performs checks like ``hasattr(fixturedef, &#39;cached_result&#39;)``,
  for example in a ``pytest_fixture_post_finalizer`` hook implementation, replace
  it with ``fixturedef.cached_result is not None``. If you ``del`` the attribute,
  set it to ``None`` instead.



Deprecations
------------

- `3238 &lt;https://github.com/pytest-dev/pytest/issues/3238&gt;`_: Option ``--no-print-logs`` is deprecated and meant to be removed in a future release. If you use ``--no-print-logs``, please try out ``--show-capture`` and
  provide feedback.

  ``--show-capture`` command-line option was added in ``pytest 3.5.0`` and allows to specify how to
  display captured output when tests fail: ``no``, ``stdout``, ``stderr``, ``log`` or ``all`` (the default).


- `571 &lt;https://github.com/pytest-dev/pytest/issues/571&gt;`_: Deprecate the unused/broken `pytest_collect_directory` hook.
  It was misaligned since the removal of the ``Directory`` collector in 2010
  and incorrect/unusable as soon as collection was split from test execution.


- `5975 &lt;https://github.com/pytest-dev/pytest/issues/5975&gt;`_: Deprecate using direct constructors for ``Nodes``.

  Instead they are now constructed via ``Node.from_parent``.

  This transitional mechanism enables us to untangle the very intensely
  entangled ``Node`` relationships by enforcing more controlled creation/configuration patterns.

  As part of this change, session/config are already disallowed parameters and as we work on the details we might need disallow a few more as well.

  Subclasses are expected to use `super().from_parent` if they intend to expand the creation of `Nodes`.


- `6779 &lt;https://github.com/pytest-dev/pytest/issues/6779&gt;`_: The ``TerminalReporter.writer`` attribute has been deprecated and should no longer be used. This
  was inadvertently exposed as part of the public API of that plugin and ties it too much
  with ``py.io.TerminalWriter``.



Features
--------

- `4597 &lt;https://github.com/pytest-dev/pytest/issues/4597&gt;`_: New :ref:`--capture=tee-sys &lt;capture-method&gt;` option to allow both live printing and capturing of test output.


- `5712 &lt;https://github.com/pytest-dev/pytest/issues/5712&gt;`_: Now all arguments to ``pytest.mark.parametrize`` need to be explicitly declared in the function signature or via ``indirect``.
  Previously it was possible to omit an argument if a fixture with the same name existed, which was just an accident of implementation and was not meant to be a part of the API.


- `6454 &lt;https://github.com/pytest-dev/pytest/issues/6454&gt;`_: Changed default for `-r` to `fE`, which displays failures and errors in the :ref:`short test summary &lt;pytest.detailed_failed_tests_usage&gt;`.  `-rN` can be used to disable it (the old behavior).


- `6469 &lt;https://github.com/pytest-dev/pytest/issues/6469&gt;`_: New options have been added to the :confval:`junit_logging` option: ``log``, ``out-err``, and ``all``.


- `6834 &lt;https://github.com/pytest-dev/pytest/issues/6834&gt;`_: Excess warning summaries are now collapsed per file to ensure readable display of warning summaries.



Improvements
------------

- `1857 &lt;https://github.com/pytest-dev/pytest/issues/1857&gt;`_: ``pytest.mark.parametrize`` accepts integers for ``ids`` again, converting it to strings.


- `449 &lt;https://github.com/pytest-dev/pytest/issues/449&gt;`_: Use &quot;yellow&quot; main color with any XPASSED tests.


- `4639 &lt;https://github.com/pytest-dev/pytest/issues/4639&gt;`_: Revert &quot;A warning is now issued when assertions are made for ``None``&quot;.

  The warning proved to be less useful than initially expected and had quite a
  few false positive cases.


- `5686 &lt;https://github.com/pytest-dev/pytest/issues/5686&gt;`_: ``tmpdir_factory.mktemp`` now fails when given absolute and non-normalized paths.


- `5984 &lt;https://github.com/pytest-dev/pytest/issues/5984&gt;`_: The ``pytest_warning_captured`` hook now receives a ``location`` parameter with the code location that generated the warning.


- `6213 &lt;https://github.com/pytest-dev/pytest/issues/6213&gt;`_: pytester: the ``testdir`` fixture respects environment settings from the ``monkeypatch`` fixture for inner runs.


- `6247 &lt;https://github.com/pytest-dev/pytest/issues/6247&gt;`_: ``--fulltrace`` is honored with collection errors.


- `6384 &lt;https://github.com/pytest-dev/pytest/issues/6384&gt;`_: Make `--showlocals` work also with `--tb=short`.


- `6653 &lt;https://github.com/pytest-dev/pytest/issues/6653&gt;`_: Add support for matching lines consecutively with :attr:`LineMatcher &lt;_pytest.pytester.LineMatcher&gt;`&#39;s :func:`~_pytest.pytester.LineMatcher.fnmatch_lines` and :func:`~_pytest.pytester.LineMatcher.re_match_lines`.


- `6658 &lt;https://github.com/pytest-dev/pytest/issues/6658&gt;`_: Code is now highlighted in tracebacks when ``pygments`` is installed.

  Users are encouraged to install ``pygments`` into their environment and provide feedback, because
  the plan is to make ``pygments`` a regular dependency in the future.


- `6795 &lt;https://github.com/pytest-dev/pytest/issues/6795&gt;`_: Import usage error message with invalid `-o` option.


- `759 &lt;https://github.com/pytest-dev/pytest/issues/759&gt;`_: ``pytest.mark.parametrize`` supports iterators and generators for ``ids``.



Bug Fixes
---------

- `310 &lt;https://github.com/pytest-dev/pytest/issues/310&gt;`_: Add support for calling `pytest.xfail()` and `pytest.importorskip()` with doctests.


- `3823 &lt;https://github.com/pytest-dev/pytest/issues/3823&gt;`_: ``--trace`` now works with unittests.


- `4445 &lt;https://github.com/pytest-dev/pytest/issues/4445&gt;`_: Fixed some warning reports produced by pytest to point to the correct location of the warning in the user&#39;s code.


- `5301 &lt;https://github.com/pytest-dev/pytest/issues/5301&gt;`_: Fix ``--last-failed`` to collect new tests from files with known failures.


- `5928 &lt;https://github.com/pytest-dev/pytest/issues/5928&gt;`_: Report ``PytestUnknownMarkWarning`` at the level of the user&#39;s code, not ``pytest``&#39;s.


- `5991 &lt;https://github.com/pytest-dev/pytest/issues/5991&gt;`_: Fix interaction with ``--pdb`` and unittests: do not use unittest&#39;s ``TestCase.debug()``.


- `6334 &lt;https://github.com/pytest-dev/pytest/issues/6334&gt;`_: Fix summary entries appearing twice when ``f/F`` and ``s/S`` report chars were used at the same time in the ``-r`` command-line option (for example ``-rFf``).

  The upper case variants were never documented and the preferred form should be the lower case.


- `6409 &lt;https://github.com/pytest-dev/pytest/issues/6409&gt;`_: Fallback to green (instead of yellow) for non-last items without previous passes with colored terminal progress indicator.


- `6454 &lt;https://github.com/pytest-dev/pytest/issues/6454&gt;`_: `--disable-warnings` is honored with `-ra` and `-rA`.


- `6497 &lt;https://github.com/pytest-dev/pytest/issues/6497&gt;`_: Fix bug in the comparison of request key with cached key in fixture.

  A construct ``if key == cached_key:`` can fail either because ``==`` is explicitly disallowed, or for, e.g., NumPy arrays, where the result of ``a == b`` cannot generally be converted to `bool`.
  The implemented fix replaces `==` with ``is``.


- `6557 &lt;https://github.com/pytest-dev/pytest/issues/6557&gt;`_: Make capture output streams ``.write()`` method return the same return value from original streams.


- `6566 &lt;https://github.com/pytest-dev/pytest/issues/6566&gt;`_: Fix ``EncodedFile.writelines`` to call the underlying buffer&#39;s ``writelines`` method.


- `6575 &lt;https://github.com/pytest-dev/pytest/issues/6575&gt;`_: Fix internal crash when ``faulthandler`` starts initialized
  (for example with ``PYTHONFAULTHANDLER=1`` environment variable set) and ``faulthandler_timeout`` defined
  in the configuration file.


- `6597 &lt;https://github.com/pytest-dev/pytest/issues/6597&gt;`_: Fix node ids which contain a parametrized empty-string variable.


- `6646 &lt;https://github.com/pytest-dev/pytest/issues/6646&gt;`_: Assertion rewriting hooks are (re)stored for the current item, which fixes them being still used after e.g. pytester&#39;s :func:`testdir.runpytest &lt;_pytest.pytester.Testdir.runpytest&gt;` etc.


- `6660 &lt;https://github.com/pytest-dev/pytest/issues/6660&gt;`_: :py:func:`pytest.exit` is handled when emitted from the :func:`pytest_sessionfinish &lt;_pytest.hookspec.pytest_sessionfinish&gt;` hook.  This includes quitting from a debugger.


- `6752 &lt;https://github.com/pytest-dev/pytest/issues/6752&gt;`_: When :py:func:`pytest.raises` is used as a function (as opposed to a context manager),
  a `match` keyword argument is now passed through to the tested function. Previously
  it was swallowed and ignored (regression in pytest 5.1.0).


- `6801 &lt;https://github.com/pytest-dev/pytest/issues/6801&gt;`_: Do not display empty lines inbetween traceback for unexpected exceptions with doctests.


- `6802 &lt;https://github.com/pytest-dev/pytest/issues/6802&gt;`_: The :fixture:`testdir fixture &lt;testdir&gt;` works within doctests now.



Improved Documentation
----------------------

- `6696 &lt;https://github.com/pytest-dev/pytest/issues/6696&gt;`_: Add list of fixtures to start of fixture chapter.


- `6742 &lt;https://github.com/pytest-dev/pytest/issues/6742&gt;`_: Expand first sentence on fixtures into a paragraph.



Trivial/Internal Changes
------------------------

- `6404 &lt;https://github.com/pytest-dev/pytest/issues/6404&gt;`_: Remove usage of ``parser`` module, deprecated in Python 3.9.
   ```
   
  
  
   ### 5.3.5
   ```
   =========================

Bug Fixes
---------

- `6517 &lt;https://github.com/pytest-dev/pytest/issues/6517&gt;`_: Fix regression in pytest 5.3.4 causing an INTERNALERROR due to a wrong assertion.
   ```
   
  
  
   ### 5.3.4
   ```
   =========================

Bug Fixes
---------

- `6496 &lt;https://github.com/pytest-dev/pytest/issues/6496&gt;`_: Revert `#6436 &lt;https://github.com/pytest-dev/pytest/issues/6436&gt;`__: unfortunately this change has caused a number of regressions in many suites,
  so the team decided to revert this change and make a new release while we continue to look for a solution.
   ```
   
  
  
   ### 5.3.3
   ```
   =========================

Bug Fixes
---------

- `2780 &lt;https://github.com/pytest-dev/pytest/issues/2780&gt;`_: Captured output during teardown is shown with ``-rP``.


- `5971 &lt;https://github.com/pytest-dev/pytest/issues/5971&gt;`_: Fix a ``pytest-xdist`` crash when dealing with exceptions raised in subprocesses created by the
  ``multiprocessing`` module.


- `6436 &lt;https://github.com/pytest-dev/pytest/issues/6436&gt;`_: :class:`FixtureDef &lt;_pytest.fixtures.FixtureDef&gt;` objects now properly register their finalizers with autouse and
  parameterized fixtures that execute before them in the fixture stack so they are torn
  down at the right times, and in the right order.


- `6532 &lt;https://github.com/pytest-dev/pytest/issues/6532&gt;`_: Fix parsing of outcomes containing multiple errors with ``testdir`` results (regression in 5.3.0).



Trivial/Internal Changes
------------------------

- `6350 &lt;https://github.com/pytest-dev/pytest/issues/6350&gt;`_: Optimized automatic renaming of test parameter IDs.
   ```
   
  
  
   ### 5.3.2
   ```
   =========================

Improvements
------------

- `4639 &lt;https://github.com/pytest-dev/pytest/issues/4639&gt;`_: Revert &quot;A warning is now issued when assertions are made for ``None``&quot;.

  The warning proved to be less useful than initially expected and had quite a
  few false positive cases.



Bug Fixes
---------

- `5430 &lt;https://github.com/pytest-dev/pytest/issues/5430&gt;`_: junitxml: Logs for failed test are now passed to junit report in case the test fails during call phase.


- `6290 &lt;https://github.com/pytest-dev/pytest/issues/6290&gt;`_: The supporting files in the ``.pytest_cache`` directory are kept with ``--cache-clear``, which only clears cached values now.


- `6301 &lt;https://github.com/pytest-dev/pytest/issues/6301&gt;`_: Fix assertion rewriting for egg-based distributions and ``editable`` installs (``pip install --editable``).
   ```
   
  
  
   ### 5.3.1
   ```
   =========================

Improvements
------------

- `6231 &lt;https://github.com/pytest-dev/pytest/issues/6231&gt;`_: Improve check for misspelling of :ref:`pytest.mark.parametrize ref`.


- `6257 &lt;https://github.com/pytest-dev/pytest/issues/6257&gt;`_: Handle :py:func:`pytest.exit` being used via :py:func:`~_pytest.hookspec.pytest_internalerror`, e.g. when quitting pdb from post mortem.



Bug Fixes
---------

- `5914 &lt;https://github.com/pytest-dev/pytest/issues/5914&gt;`_: pytester: fix :py:func:`~_pytest.pytester.LineMatcher.no_fnmatch_line` when used after positive matching.


- `6082 &lt;https://github.com/pytest-dev/pytest/issues/6082&gt;`_: Fix line detection for doctest samples inside :py:class:`python:property` docstrings, as a workaround to `bpo-17446 &lt;https://bugs.python.org/issue17446&gt;`__.


- `6254 &lt;https://github.com/pytest-dev/pytest/issues/6254&gt;`_: Fix compatibility with pytest-parallel (regression in pytest 5.3.0).


- `6255 &lt;https://github.com/pytest-dev/pytest/issues/6255&gt;`_: Clear the :py:data:`sys.last_traceback`, :py:data:`sys.last_type`
  and :py:data:`sys.last_value` attributes by deleting them instead
  of setting them to ``None``. This better matches the behaviour of
  the Python standard library.
   ```
   
  
  
   ### 5.3.0
   ```
   =========================

Deprecations
------------

- `6179 &lt;https://github.com/pytest-dev/pytest/issues/6179&gt;`_: The default value of :confval:`junit_family` option will change to ``&quot;xunit2&quot;`` in pytest 6.0, given
  that this is the version supported by default in modern tools that manipulate this type of file.

  In order to smooth the transition, pytest will issue a warning in case the ``--junitxml`` o…
bors bot added a commit to aragilar/spaceplot that referenced this issue Apr 17, 2021
6: Pin pytest to latest version 6.2.3 r=aragilar a=pyup-bot


This PR pins [pytest](https://pypi.org/project/pytest) to the latest release **6.2.3**.



<details>
  <summary>Changelog</summary>
  
  
   ### 6.2.2
   ```
   =========================

Bug Fixes
---------

- `8152 &lt;https://github.com/pytest-dev/pytest/issues/8152&gt;`_: Fixed &quot;(&lt;Skipped instance&gt;)&quot; being shown as a skip reason in the verbose test summary line when the reason is empty.


- `8249 &lt;https://github.com/pytest-dev/pytest/issues/8249&gt;`_: Fix the ``faulthandler`` plugin for occasions when running with ``twisted.logger`` and using ``pytest --capture=no``.
   ```
   
  
  
   ### 6.2.1
   ```
   =========================

Bug Fixes
---------

- `7678 &lt;https://github.com/pytest-dev/pytest/issues/7678&gt;`_: Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in
  the host and loaded later from an UNC mounted path (Windows).


- `8132 &lt;https://github.com/pytest-dev/pytest/issues/8132&gt;`_: Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises
  ``TypeError`` when dealing with non-numeric types, falling back to normal comparison.
  Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
  and happened to compare correctly to a scalar if they had only one element.
  After 6.2.0, these types began failing, because they inherited neither from
  standard Python number hierarchy nor from ``numpy.ndarray``.

  ``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array
  protocol and are not scalars. This treats array-like objects like numpy arrays,
  regardless of size.
   ```
   
  
  
   ### 6.2.0
   ```
   =========================

Breaking Changes
----------------

- `7808 &lt;https://github.com/pytest-dev/pytest/issues/7808&gt;`_: pytest now supports python3.6+ only.



Deprecations
------------

- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_: Directly constructing/calling the following classes/functions is now deprecated:

  - ``_pytest.cacheprovider.Cache``
  - ``_pytest.cacheprovider.Cache.for_config()``
  - ``_pytest.cacheprovider.Cache.clear_cache()``
  - ``_pytest.cacheprovider.Cache.cache_dir_from_config()``
  - ``_pytest.capture.CaptureFixture``
  - ``_pytest.fixtures.FixtureRequest``
  - ``_pytest.fixtures.SubRequest``
  - ``_pytest.logging.LogCaptureFixture``
  - ``_pytest.pytester.Pytester``
  - ``_pytest.pytester.Testdir``
  - ``_pytest.recwarn.WarningsRecorder``
  - ``_pytest.recwarn.WarningsChecker``
  - ``_pytest.tmpdir.TempPathFactory``
  - ``_pytest.tmpdir.TempdirFactory``

  These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.


- `7530 &lt;https://github.com/pytest-dev/pytest/issues/7530&gt;`_: The ``--strict`` command-line option has been deprecated, use ``--strict-markers`` instead.

  We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing flag for all strictness
  related options (``--strict-markers`` and ``--strict-config`` at the moment, more might be introduced in the future).


- `7988 &lt;https://github.com/pytest-dev/pytest/issues/7988&gt;`_: The ``pytest.yield_fixture`` decorator/function is now deprecated. Use :func:`pytest.fixture` instead.

  ``yield_fixture`` has been an alias for ``fixture`` for a very long time, so can be search/replaced safely.



Features
--------

- `5299 &lt;https://github.com/pytest-dev/pytest/issues/5299&gt;`_: pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python&gt;=3.8.
  See :ref:`unraisable` for more information.


- `7425 &lt;https://github.com/pytest-dev/pytest/issues/7425&gt;`_: New :fixture:`pytester` fixture, which is identical to :fixture:`testdir` but its methods return :class:`pathlib.Path` when appropriate instead of ``py.path.local``.

  This is part of the movement to use :class:`pathlib.Path` objects internally, in order to remove the dependency to ``py`` in the future.

  Internally, the old :class:`Testdir &lt;_pytest.pytester.Testdir&gt;` is now a thin wrapper around :class:`Pytester &lt;_pytest.pytester.Pytester&gt;`, preserving the old interface.


- `7695 &lt;https://github.com/pytest-dev/pytest/issues/7695&gt;`_: A new hook was added, `pytest_markeval_namespace` which should return a dictionary.
  This dictionary will be used to augment the &quot;global&quot; variables available to evaluate skipif/xfail/xpass markers.

  Pseudo example

  ``conftest.py``:

  .. code-block:: python

     def pytest_markeval_namespace():
         return {&quot;color&quot;: &quot;red&quot;}

  ``test_func.py``:

  .. code-block:: python

     pytest.mark.skipif(&quot;color == &#39;blue&#39;&quot;, reason=&quot;Color is not red&quot;)
     def test_func():
         assert False


- `8006 &lt;https://github.com/pytest-dev/pytest/issues/8006&gt;`_: It is now possible to construct a :class:`~pytest.MonkeyPatch` object directly as ``pytest.MonkeyPatch()``,
  in cases when the :fixture:`monkeypatch` fixture cannot be used. Previously some users imported it
  from the private `_pytest.monkeypatch.MonkeyPatch` namespace.

  Additionally, :meth:`MonkeyPatch.context &lt;pytest.MonkeyPatch.context&gt;` is now a classmethod,
  and can be used as ``with MonkeyPatch.context() as mp: ...``. This is the recommended way to use
  ``MonkeyPatch`` directly, since unlike the ``monkeypatch`` fixture, an instance created directly
  is not ``undo()``-ed automatically.



Improvements
------------

- `1265 &lt;https://github.com/pytest-dev/pytest/issues/1265&gt;`_: Added an ``__str__`` implementation to the :class:`~pytest.pytester.LineMatcher` class which is returned from ``pytester.run_pytest().stdout`` and similar. It returns the entire output, like the existing ``str()`` method.


- `2044 &lt;https://github.com/pytest-dev/pytest/issues/2044&gt;`_: Verbose mode now shows the reason that a test was skipped in the test&#39;s terminal line after the &quot;SKIPPED&quot;, &quot;XFAIL&quot; or &quot;XPASS&quot;.


- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_ The types of builtin pytest fixtures are now exported so they may be used in type annotations of test functions.
  The newly-exported types are:

  - ``pytest.FixtureRequest`` for the :fixture:`request` fixture.
  - ``pytest.Cache`` for the :fixture:`cache` fixture.
  - ``pytest.CaptureFixture[str]`` for the :fixture:`capfd` and :fixture:`capsys` fixtures.
  - ``pytest.CaptureFixture[bytes]`` for the :fixture:`capfdbinary` and :fixture:`capsysbinary` fixtures.
  - ``pytest.LogCaptureFixture`` for the :fixture:`caplog` fixture.
  - ``pytest.Pytester`` for the :fixture:`pytester` fixture.
  - ``pytest.Testdir`` for the :fixture:`testdir` fixture.
  - ``pytest.TempdirFactory`` for the :fixture:`tmpdir_factory` fixture.
  - ``pytest.TempPathFactory`` for the :fixture:`tmp_path_factory` fixture.
  - ``pytest.MonkeyPatch`` for the :fixture:`monkeypatch` fixture.
  - ``pytest.WarningsRecorder`` for the :fixture:`recwarn` fixture.

  Constructing them is not supported (except for `MonkeyPatch`); they are only meant for use in type annotations.
  Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.

  Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.


- `7527 &lt;https://github.com/pytest-dev/pytest/issues/7527&gt;`_: When a comparison between :func:`namedtuple &lt;collections.namedtuple&gt;` instances of the same type fails, pytest now shows the differing field names (possibly nested) instead of their indexes.


- `7615 &lt;https://github.com/pytest-dev/pytest/issues/7615&gt;`_: :meth:`Node.warn &lt;_pytest.nodes.Node.warn&gt;` now permits any subclass of :class:`Warning`, not just :class:`PytestWarning &lt;pytest.PytestWarning&gt;`.


- `7701 &lt;https://github.com/pytest-dev/pytest/issues/7701&gt;`_: Improved reporting when using ``--collected-only``. It will now show the number of collected tests in the summary stats.


- `7710 &lt;https://github.com/pytest-dev/pytest/issues/7710&gt;`_: Use strict equality comparison for non-numeric types in :func:`pytest.approx` instead of
  raising :class:`TypeError`.

  This was the undocumented behavior before 3.7, but is now officially a supported feature.


- `7938 &lt;https://github.com/pytest-dev/pytest/issues/7938&gt;`_: New ``--sw-skip`` argument which is a shorthand for ``--stepwise-skip``.


- `8023 &lt;https://github.com/pytest-dev/pytest/issues/8023&gt;`_: Added ``&#39;node_modules&#39;`` to default value for :confval:`norecursedirs`.


- `8032 &lt;https://github.com/pytest-dev/pytest/issues/8032&gt;`_: :meth:`doClassCleanups &lt;unittest.TestCase.doClassCleanups&gt;` (introduced in :mod:`unittest` in Python and 3.8) is now called appropriately.



Bug Fixes
---------

- `4824 &lt;https://github.com/pytest-dev/pytest/issues/4824&gt;`_: Fixed quadratic behavior and improved performance of collection of items using autouse fixtures and xunit fixtures.


- `7758 &lt;https://github.com/pytest-dev/pytest/issues/7758&gt;`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.


- `7911 &lt;https://github.com/pytest-dev/pytest/issues/7911&gt;`_: Directories created by by :fixture:`tmp_path` and :fixture:`tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.


- `7913 &lt;https://github.com/pytest-dev/pytest/issues/7913&gt;`_: Fixed a crash or hang in :meth:`pytester.spawn &lt;_pytest.pytester.Pytester.spawn&gt;` when the :mod:`readline` module is involved.


- `7951 &lt;https://github.com/pytest-dev/pytest/issues/7951&gt;`_: Fixed handling of recursive symlinks when collecting tests.


- `7981 &lt;https://github.com/pytest-dev/pytest/issues/7981&gt;`_: Fixed symlinked directories not being followed during collection. Regressed in pytest 6.1.0.


- `8016 &lt;https://github.com/pytest-dev/pytest/issues/8016&gt;`_: Fixed only one doctest being collected when using ``pytest --doctest-modules path/to/an/__init__.py``.



Improved Documentation
----------------------

- `7429 &lt;https://github.com/pytest-dev/pytest/issues/7429&gt;`_: Add more information and use cases about skipping doctests.


- `7780 &lt;https://github.com/pytest-dev/pytest/issues/7780&gt;`_: Classes which should not be inherited from are now marked ``final class`` in the API reference.


- `7872 &lt;https://github.com/pytest-dev/pytest/issues/7872&gt;`_: ``_pytest.config.argparsing.Parser.addini()`` accepts explicit ``None`` and ``&quot;string&quot;``.


- `7878 &lt;https://github.com/pytest-dev/pytest/issues/7878&gt;`_: In pull request section, ask to commit after editing changelog and authors file.



Trivial/Internal Changes
------------------------

- `7802 &lt;https://github.com/pytest-dev/pytest/issues/7802&gt;`_: The ``attrs`` dependency requirement is now &gt;=19.2.0 instead of &gt;=17.4.0.


- `8014 &lt;https://github.com/pytest-dev/pytest/issues/8014&gt;`_: `.pyc` files created by pytest&#39;s assertion rewriting now conform to the newer PEP-552 format on Python&gt;=3.7.
  (These files are internal and only interpreted by pytest itself.)
   ```
   
  
  
   ### 6.1.2
   ```
   =========================

Bug Fixes
---------

- `7758 &lt;https://github.com/pytest-dev/pytest/issues/7758&gt;`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.


- `7911 &lt;https://github.com/pytest-dev/pytest/issues/7911&gt;`_: Directories created by `tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.



Improved Documentation
----------------------

- `7815 &lt;https://github.com/pytest-dev/pytest/issues/7815&gt;`_: Improve deprecation warning message for ``pytest._fillfuncargs()``.
   ```
   
  
  
   ### 6.1.1
   ```
   =========================

Bug Fixes
---------

- `7807 &lt;https://github.com/pytest-dev/pytest/issues/7807&gt;`_: Fixed regression in pytest 6.1.0 causing incorrect rootdir to be determined in some non-trivial cases where parent directories have config files as well.


- `7814 &lt;https://github.com/pytest-dev/pytest/issues/7814&gt;`_: Fixed crash in header reporting when :confval:`testpaths` is used and contains absolute paths (regression in 6.1.0).
   ```
   
  
  
   ### 6.1.0
   ```
   =========================

Breaking Changes
----------------

- `5585 &lt;https://github.com/pytest-dev/pytest/issues/5585&gt;`_: As per our policy, the following features which have been deprecated in the 5.X series are now
  removed:

  * The ``funcargnames`` read-only property of ``FixtureRequest``, ``Metafunc``, and ``Function`` classes. Use ``fixturenames`` attribute.

  * ``pytest.fixture`` no longer supports positional arguments, pass all arguments by keyword instead.

  * Direct construction of ``Node`` subclasses now raise an error, use ``from_parent`` instead.

  * The default value for ``junit_family`` has changed to ``xunit2``. If you require the old format, add ``junit_family=xunit1`` to your configuration file.

  * The ``TerminalReporter`` no longer has a ``writer`` attribute. Plugin authors may use the public functions of the ``TerminalReporter`` instead of accessing the ``TerminalWriter`` object directly.

  * The ``--result-log`` option has been removed. Users are recommended to use the `pytest-reportlog &lt;https://github.com/pytest-dev/pytest-reportlog&gt;`__ plugin instead.


  For more information consult
  `Deprecations and Removals &lt;https://docs.pytest.org/en/stable/deprecations.html&gt;`__ in the docs.



Deprecations
------------

- `6981 &lt;https://github.com/pytest-dev/pytest/issues/6981&gt;`_: The ``pytest.collect`` module is deprecated: all its names can be imported from ``pytest`` directly.


- `7097 &lt;https://github.com/pytest-dev/pytest/issues/7097&gt;`_: The ``pytest._fillfuncargs`` function is deprecated. This function was kept
  for backward compatibility with an older plugin.

  It&#39;s functionality is not meant to be used directly, but if you must replace
  it, use `function._request._fillfixtures()` instead, though note this is not
  a public API and may break in the future.


- `7210 &lt;https://github.com/pytest-dev/pytest/issues/7210&gt;`_: The special ``-k &#39;-expr&#39;`` syntax to ``-k`` is deprecated. Use ``-k &#39;not expr&#39;``
  instead.

  The special ``-k &#39;expr:&#39;`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.


- `7255 &lt;https://github.com/pytest-dev/pytest/issues/7255&gt;`_: The :func:`pytest_warning_captured &lt;_pytest.hookspec.pytest_warning_captured&gt;` hook is deprecated in favor
  of :func:`pytest_warning_recorded &lt;_pytest.hookspec.pytest_warning_recorded&gt;`, and will be removed in a future version.


- `7648 &lt;https://github.com/pytest-dev/pytest/issues/7648&gt;`_: The ``gethookproxy()`` and ``isinitpath()`` methods of ``FSCollector`` and ``Package`` are deprecated;
  use ``self.session.gethookproxy()`` and ``self.session.isinitpath()`` instead.
  This should work on all pytest versions.



Features
--------

- `7667 &lt;https://github.com/pytest-dev/pytest/issues/7667&gt;`_: New ``--durations-min`` command-line flag controls the minimal duration for inclusion in the slowest list of tests shown by ``--durations``. Previously this was hard-coded to ``0.005s``.



Improvements
------------

- `6681 &lt;https://github.com/pytest-dev/pytest/issues/6681&gt;`_: Internal pytest warnings issued during the early stages of initialization are now properly handled and can filtered through :confval:`filterwarnings` or ``--pythonwarnings/-W``.

  This also fixes a number of long standing issues: `2891 &lt;https://github.com/pytest-dev/pytest/issues/2891&gt;`__, `#7620 &lt;https://github.com/pytest-dev/pytest/issues/7620&gt;`__, `#7426 &lt;https://github.com/pytest-dev/pytest/issues/7426&gt;`__.


- `7572 &lt;https://github.com/pytest-dev/pytest/issues/7572&gt;`_: When a plugin listed in ``required_plugins`` is missing or an unknown config key is used with ``--strict-config``, a simple error message is now shown instead of a stacktrace.


- `7685 &lt;https://github.com/pytest-dev/pytest/issues/7685&gt;`_: Added two new attributes :attr:`rootpath &lt;_pytest.config.Config.rootpath&gt;` and :attr:`inipath &lt;_pytest.config.Config.inipath&gt;` to :class:`Config &lt;_pytest.config.Config&gt;`.
  These attributes are :class:`pathlib.Path` versions of the existing :attr:`rootdir &lt;_pytest.config.Config.rootdir&gt;` and :attr:`inifile &lt;_pytest.config.Config.inifile&gt;` attributes,
  and should be preferred over them when possible.


- `7780 &lt;https://github.com/pytest-dev/pytest/issues/7780&gt;`_: Public classes which are not designed to be inherited from are now marked `final &lt;https://docs.python.org/3/library/typing.html#typing.final&gt;`_.
  Code which inherits from these classes will trigger a type-checking (e.g. mypy) error, but will still work in runtime.
  Currently the ``final`` designation does not appear in the API Reference but hopefully will in the future.



Bug Fixes
---------

- `1953 &lt;https://github.com/pytest-dev/pytest/issues/1953&gt;`_: Fixed error when overwriting a parametrized fixture, while also reusing the super fixture value.

  .. code-block:: python

       conftest.py
      import pytest


      pytest.fixture(params=[1, 2])
      def foo(request):
          return request.param


       test_foo.py
      import pytest


      pytest.fixture
      def foo(foo):
          return foo * 2


- `4984 &lt;https://github.com/pytest-dev/pytest/issues/4984&gt;`_: Fixed an internal error crash with ``IndexError: list index out of range`` when
  collecting a module which starts with a decorated function, the decorator
  raises, and assertion rewriting is enabled.


- `7591 &lt;https://github.com/pytest-dev/pytest/issues/7591&gt;`_: pylint shouldn&#39;t complain anymore about unimplemented abstract methods when inheriting from :ref:`File &lt;non-python tests&gt;`.


- `7628 &lt;https://github.com/pytest-dev/pytest/issues/7628&gt;`_: Fixed test collection when a full path without a drive letter was passed to pytest on Windows (for example ``\projects\tests\test.py`` instead of ``c:\projects\tests\pytest.py``).


- `7638 &lt;https://github.com/pytest-dev/pytest/issues/7638&gt;`_: Fix handling of command-line options that appear as paths but trigger an OS-level syntax error on Windows, such as the options used internally by ``pytest-xdist``.


- `7742 &lt;https://github.com/pytest-dev/pytest/issues/7742&gt;`_: Fixed INTERNALERROR when accessing locals / globals with faulty ``exec``.



Improved Documentation
----------------------

- `1477 &lt;https://github.com/pytest-dev/pytest/issues/1477&gt;`_: Removed faq.rst and its reference in contents.rst.



Trivial/Internal Changes
------------------------

- `7536 &lt;https://github.com/pytest-dev/pytest/issues/7536&gt;`_: The internal ``junitxml`` plugin has rewritten to use ``xml.etree.ElementTree``.
  The order of attributes in XML elements might differ. Some unneeded escaping is
  no longer performed.


- `7587 &lt;https://github.com/pytest-dev/pytest/issues/7587&gt;`_: The dependency on the ``more-itertools`` package has been removed.


- `7631 &lt;https://github.com/pytest-dev/pytest/issues/7631&gt;`_: The result type of :meth:`capfd.readouterr() &lt;_pytest.capture.CaptureFixture.readouterr&gt;` (and similar) is no longer a namedtuple,
  but should behave like one in all respects. This was done for technical reasons.


- `7671 &lt;https://github.com/pytest-dev/pytest/issues/7671&gt;`_: When collecting tests, pytest finds test classes and functions by examining the
  attributes of python objects (modules, classes and instances). To speed up this
  process, pytest now ignores builtin attributes (like ``__class__``,
  ``__delattr__`` and ``__new__``) without consulting the :confval:`python_classes` and
  :confval:`python_functions` configuration options and without passing them to plugins
  using the :func:`pytest_pycollect_makeitem &lt;_pytest.hookspec.pytest_pycollect_makeitem&gt;` hook.
   ```
   
  
  
   ### 6.0.2
   ```
   =========================

Bug Fixes
---------

- `7148 &lt;https://github.com/pytest-dev/pytest/issues/7148&gt;`_: Fixed ``--log-cli`` potentially causing unrelated ``print`` output to be swallowed.


- `7672 &lt;https://github.com/pytest-dev/pytest/issues/7672&gt;`_: Fixed log-capturing level restored incorrectly if ``caplog.set_level`` is called more than once.


- `7686 &lt;https://github.com/pytest-dev/pytest/issues/7686&gt;`_: Fixed `NotSetType.token` being used as the parameter ID when the parametrization list is empty.
  Regressed in pytest 6.0.0.


- `7707 &lt;https://github.com/pytest-dev/pytest/issues/7707&gt;`_: Fix internal error when handling some exceptions that contain multiple lines or the style uses multiple lines (``--tb=line`` for example).
   ```
   
  
  
   ### 6.0.1
   ```
   =========================

Bug Fixes
---------

- `7394 &lt;https://github.com/pytest-dev/pytest/issues/7394&gt;`_: Passing an empty ``help`` value to ``Parser.add_option`` is now accepted instead of crashing when running ``pytest --help``.
  Passing ``None`` raises a more informative ``TypeError``.


- `7558 &lt;https://github.com/pytest-dev/pytest/issues/7558&gt;`_: Fix pylint ``not-callable`` lint on ``pytest.mark.parametrize()`` and the other builtin marks:
  ``skip``, ``skipif``, ``xfail``, ``usefixtures``, ``filterwarnings``.


- `7559 &lt;https://github.com/pytest-dev/pytest/issues/7559&gt;`_: Fix regression in plugins using ``TestReport.longreprtext`` (such as ``pytest-html``) when ``TestReport.longrepr`` is not a string.


- `7569 &lt;https://github.com/pytest-dev/pytest/issues/7569&gt;`_: Fix logging capture handler&#39;s level not reset on teardown after a call to ``caplog.set_level()``.
   ```
   
  
  
   ### 6.0.0
   ```
   =========================

(**Please see the full set of changes for this release also in the 6.0.0rc1 notes below**)

Breaking Changes
----------------

- `5584 &lt;https://github.com/pytest-dev/pytest/issues/5584&gt;`_: **PytestDeprecationWarning are now errors by default.**

  Following our plan to remove deprecated features with as little disruption as
  possible, all warnings of type ``PytestDeprecationWarning`` now generate errors
  instead of warning messages.

  **The affected features will be effectively removed in pytest 6.1**, so please consult the
  `Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`__
  section in the docs for directions on how to update existing code.

  In the pytest ``6.0.X`` series, it is possible to change the errors back into warnings as a
  stopgap measure by adding this to your ``pytest.ini`` file:

  .. code-block:: ini

      [pytest]
      filterwarnings =
          ignore::pytest.PytestDeprecationWarning

  But this will stop working when pytest ``6.1`` is released.

  **If you have concerns** about the removal of a specific feature, please add a
  comment to `5584 &lt;https://github.com/pytest-dev/pytest/issues/5584&gt;`__.


- `7472 &lt;https://github.com/pytest-dev/pytest/issues/7472&gt;`_: The ``exec_()`` and ``is_true()`` methods of ``_pytest._code.Frame`` have been removed.



Features
--------

- `7464 &lt;https://github.com/pytest-dev/pytest/issues/7464&gt;`_: Added support for :envvar:`NO_COLOR` and :envvar:`FORCE_COLOR` environment variables to control colored output.



Improvements
------------

- `7467 &lt;https://github.com/pytest-dev/pytest/issues/7467&gt;`_: ``--log-file`` CLI option and ``log_file`` ini marker now create subdirectories if needed.


- `7489 &lt;https://github.com/pytest-dev/pytest/issues/7489&gt;`_: The :func:`pytest.raises` function has a clearer error message when ``match`` equals the obtained string but is not a regex match. In this case it is suggested to escape the regex.



Bug Fixes
---------

- `7392 &lt;https://github.com/pytest-dev/pytest/issues/7392&gt;`_: Fix the reported location of tests skipped with ``pytest.mark.skip`` when ``--runxfail`` is used.


- `7491 &lt;https://github.com/pytest-dev/pytest/issues/7491&gt;`_: :fixture:`tmpdir` and :fixture:`tmp_path` no longer raise an error if the lock to check for
  stale temporary directories is not accessible.


- `7517 &lt;https://github.com/pytest-dev/pytest/issues/7517&gt;`_: Preserve line endings when captured via ``capfd``.


- `7534 &lt;https://github.com/pytest-dev/pytest/issues/7534&gt;`_: Restored the previous formatting of ``TracebackEntry.__str__`` which was changed by accident.



Improved Documentation
----------------------

- `7422 &lt;https://github.com/pytest-dev/pytest/issues/7422&gt;`_: Clarified when the ``usefixtures`` mark can apply fixtures to test.


- `7441 &lt;https://github.com/pytest-dev/pytest/issues/7441&gt;`_: Add a note about ``-q`` option used in getting started guide.



Trivial/Internal Changes
------------------------

- `7389 &lt;https://github.com/pytest-dev/pytest/issues/7389&gt;`_: Fixture scope ``package`` is no longer considered experimental.
   ```
   
  
  
   ### 6.0.0rc1
   ```
   ============================

Breaking Changes
----------------

- `1316 &lt;https://github.com/pytest-dev/pytest/issues/1316&gt;`_: ``TestReport.longrepr`` is now always an instance of ``ReprExceptionInfo``. Previously it was a ``str`` when a test failed with ``pytest.fail(..., pytrace=False)``.


- `5965 &lt;https://github.com/pytest-dev/pytest/issues/5965&gt;`_: symlinks are no longer resolved during collection and matching `conftest.py` files with test file paths.

  Resolving symlinks for the current directory and during collection was introduced as a bugfix in 3.9.0, but it actually is a new feature which had unfortunate consequences in Windows and surprising results in other platforms.

  The team decided to step back on resolving symlinks at all, planning to review this in the future with a more solid solution (see discussion in
  `6523 &lt;https://github.com/pytest-dev/pytest/pull/6523&gt;`__ for details).

  This might break test suites which made use of this feature; the fix is to create a symlink
  for the entire test tree, and not only to partial files/tress as it was possible previously.


- `6505 &lt;https://github.com/pytest-dev/pytest/issues/6505&gt;`_: ``Testdir.run().parseoutcomes()`` now always returns the parsed nouns in plural form.

  Originally ``parseoutcomes()`` would always returns the nouns in plural form, but a change
  meant to improve the terminal summary by using singular form single items (``1 warning`` or ``1 error``)
  caused an unintended regression by changing the keys returned by ``parseoutcomes()``.

  Now the API guarantees to always return the plural form, so calls like this:

  .. code-block:: python

      result = testdir.runpytest()
      result.assert_outcomes(error=1)

  Need to be changed to:


  .. code-block:: python

      result = testdir.runpytest()
      result.assert_outcomes(errors=1)


- `6903 &lt;https://github.com/pytest-dev/pytest/issues/6903&gt;`_: The ``os.dup()`` function is now assumed to exist. We are not aware of any
  supported Python 3 implementations which do not provide it.


- `7040 &lt;https://github.com/pytest-dev/pytest/issues/7040&gt;`_: ``-k`` no longer matches against the names of the directories outside the test session root.

  Also, ``pytest.Package.name`` is now just the name of the directory containing the package&#39;s
  ``__init__.py`` file, instead of the full path. This is consistent with how the other nodes
  are named, and also one of the reasons why ``-k`` would match against any directory containing
  the test suite.


- `7122 &lt;https://github.com/pytest-dev/pytest/issues/7122&gt;`_: Expressions given to the ``-m`` and ``-k`` options are no longer evaluated using Python&#39;s :func:`eval`.
  The format supports ``or``, ``and``, ``not``, parenthesis and general identifiers to match against.
  Python constants, keywords or other operators are no longer evaluated differently.


- `7135 &lt;https://github.com/pytest-dev/pytest/issues/7135&gt;`_: Pytest now uses its own ``TerminalWriter`` class instead of using the one from the ``py`` library.
  Plugins generally access this class through ``TerminalReporter.writer``, ``TerminalReporter.write()``
  (and similar methods), or ``_pytest.config.create_terminal_writer()``.

  The following breaking changes were made:

  - Output (``write()`` method and others) no longer flush implicitly; the flushing behavior
    of the underlying file is respected. To flush explicitly (for example, if you
    want output to be shown before an end-of-line is printed), use ``write(flush=True)`` or
    ``terminal_writer.flush()``.
  - Explicit Windows console support was removed, delegated to the colorama library.
  - Support for writing ``bytes`` was removed.
  - The ``reline`` method and ``chars_on_current_line`` property were removed.
  - The ``stringio`` and ``encoding`` arguments was removed.
  - Support for passing a callable instead of a file was removed.


- `7224 &lt;https://github.com/pytest-dev/pytest/issues/7224&gt;`_: The `item.catch_log_handler` and `item.catch_log_handlers` attributes, set by the
  logging plugin and never meant to be public, are no longer available.

  The deprecated ``--no-print-logs`` option and ``log_print`` ini option are removed. Use ``--show-capture`` instead.


- `7226 &lt;https://github.com/pytest-dev/pytest/issues/7226&gt;`_: Removed the unused ``args`` parameter from ``pytest.Function.__init__``.


- `7418 &lt;https://github.com/pytest-dev/pytest/issues/7418&gt;`_: Removed the `pytest_doctest_prepare_content` hook specification. This hook
  hasn&#39;t been triggered by pytest for at least 10 years.


- `7438 &lt;https://github.com/pytest-dev/pytest/issues/7438&gt;`_: Some changes were made to the internal ``_pytest._code.source``, listed here
  for the benefit of plugin authors who may be using it:

  - The ``deindent`` argument to ``Source()`` has been removed, now it is always true.
  - Support for zero or multiple arguments to ``Source()`` has been removed.
  - Support for comparing ``Source`` with an ``str`` has been removed.
  - The methods ``Source.isparseable()`` and ``Source.putaround()`` have been removed.
  - The method ``Source.compile()`` and function ``_pytest._code.compile()`` have
    been removed; use plain ``compile()`` instead.
  - The function ``_pytest._code.source.getsource()`` has been removed; use
    ``Source()`` directly instead.



Deprecations
------------

- `7210 &lt;https://github.com/pytest-dev/pytest/issues/7210&gt;`_: The special ``-k &#39;-expr&#39;`` syntax to ``-k`` is deprecated. Use ``-k &#39;not expr&#39;``
  instead.

  The special ``-k &#39;expr:&#39;`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.

- `4049 &lt;https://github.com/pytest-dev/pytest/issues/4049&gt;`_: ``pytest_warning_captured`` is deprecated in favor of the ``pytest_warning_recorded`` hook.


Features
--------

- `1556 &lt;https://github.com/pytest-dev/pytest/issues/1556&gt;`_: pytest now supports ``pyproject.toml`` files for configuration.

  The configuration options is similar to the one available in other formats, but must be defined
  in a ``[tool.pytest.ini_options]`` table to be picked up by pytest:

  .. code-block:: toml

       pyproject.toml
      [tool.pytest.ini_options]
      minversion = &quot;6.0&quot;
      addopts = &quot;-ra -q&quot;
      testpaths = [
          &quot;tests&quot;,
          &quot;integration&quot;,
      ]

  More information can be found `in the docs &lt;https://docs.pytest.org/en/stable/customize.html#configuration-file-formats&gt;`__.


- `3342 &lt;https://github.com/pytest-dev/pytest/issues/3342&gt;`_: pytest now includes inline type annotations and exposes them to user programs.
  Most of the user-facing API is covered, as well as internal code.

  If you are running a type checker such as mypy on your tests, you may start
  noticing type errors indicating incorrect usage. If you run into an error that
  you believe to be incorrect, please let us know in an issue.

  The types were developed against mypy version 0.780. Versions before 0.750
  are known not to work. We recommend using the latest version. Other type
  checkers may work as well, but they are not officially verified to work by
  pytest yet.


- `4049 &lt;https://github.com/pytest-dev/pytest/issues/4049&gt;`_: Introduced a new hook named `pytest_warning_recorded` to convey information about warnings captured by the internal `pytest` warnings plugin.

  This hook is meant to replace `pytest_warning_captured`, which is deprecated and will be removed in a future release.


- `6471 &lt;https://github.com/pytest-dev/pytest/issues/6471&gt;`_: New command-line flags:

  * `--no-header`: disables the initial header, including platform, version, and plugins.
  * `--no-summary`: disables the final test summary, including warnings.


- `6856 &lt;https://github.com/pytest-dev/pytest/issues/6856&gt;`_: A warning is now shown when an unknown key is read from a config INI file.

  The `--strict-config` flag has been added to treat these warnings as errors.


- `6906 &lt;https://github.com/pytest-dev/pytest/issues/6906&gt;`_: Added `--code-highlight` command line option to enable/disable code highlighting in terminal output.


- `7245 &lt;https://github.com/pytest-dev/pytest/issues/7245&gt;`_: New ``--import-mode=importlib`` option that uses `importlib &lt;https://docs.python.org/3/library/importlib.html&gt;`__ to import test modules.

  Traditionally pytest used ``__import__`` while changing ``sys.path`` to import test modules (which
  also changes ``sys.modules`` as a side-effect), which works but has a number of drawbacks, like requiring test modules
  that don&#39;t live in packages to have unique names (as they need to reside under a unique name in ``sys.modules``).

  ``--import-mode=importlib`` uses more fine grained import mechanisms from ``importlib`` which don&#39;t
  require pytest to change ``sys.path`` or ``sys.modules`` at all, eliminating much of the drawbacks
  of the previous mode.

  We intend to make ``--import-mode=importlib`` the default in future versions, so users are encouraged
  to try the new mode and provide feedback (both positive or negative) in issue `7245 &lt;https://github.com/pytest-dev/pytest/issues/7245&gt;`__.

  You can read more about this option in `the documentation &lt;https://docs.pytest.org/en/latest/pythonpath.html#import-modes&gt;`__.


- `7305 &lt;https://github.com/pytest-dev/pytest/issues/7305&gt;`_: New ``required_plugins`` configuration option allows the user to specify a list of plugins, including version information, that are required for pytest to run. An error is raised if any required plugins are not found when running pytest.


Improvements
------------

- `4375 &lt;https://github.com/pytest-dev/pytest/issues/4375&gt;`_: The ``pytest`` command now suppresses the ``BrokenPipeError`` error message that
  is printed to stderr when the output of ``pytest`` is piped and and the pipe is
  closed by the piped-to program (common examples are ``less`` and ``head``).


- `4391 &lt;https://github.com/pytest-dev/pytest/issues/4391&gt;`_: Improved precision of test durations measurement. ``CallInfo`` items now have a new ``&lt;CallInfo&gt;.duration`` attribute, created using ``time.perf_counter()``. This attribute is used to fill the ``&lt;TestReport&gt;.duration`` attribute, which is more accurate than the previous ``&lt;CallInfo&gt;.stop - &lt;CallInfo&gt;.start`` (as these are based on ``time.time()``).


- `4675 &lt;https://github.com/pytest-dev/pytest/issues/4675&gt;`_: Rich comparison for dataclasses and `attrs`-classes is now recursive.


- `6285 &lt;https://github.com/pytest-dev/pytest/issues/6285&gt;`_: Exposed the `pytest.FixtureLookupError` exception which is raised by `request.getfixturevalue()`
  (where `request` is a `FixtureRequest` fixture) when a fixture with the given name cannot be returned.


- `6433 &lt;https://github.com/pytest-dev/pytest/issues/6433&gt;`_: If an error is encountered while formatting the message in a logging call, for
  example ``logging.warning(&quot;oh no!: %s: %s&quot;, &quot;first&quot;)`` (a second argument is
  missing), pytest now propagates the error, likely causing the test to fail.

  Previously, such a mistake would cause an error to be printed to stderr, which
  is not displayed by default for passing tests. This change makes the mistake
  visible during testing.

  You may supress this behavior temporarily or permanently by setting
  ``logging.raiseExceptions = False``.


- `6817 &lt;https://github.com/pytest-dev/pytest/issues/6817&gt;`_: Explicit new-lines in help texts of command-line options are preserved, allowing plugins better control
  of the help displayed to users.


- `6940 &lt;https://github.com/pytest-dev/pytest/issues/6940&gt;`_: When using the ``--duration`` option, the terminal message output is now more precise about the number and duration of hidden items.


- `6991 &lt;https://github.com/pytest-dev/pytest/issues/6991&gt;`_: Collected files are displayed after any reports from hooks, e.g. the status from ``--lf``.


- `7091 &lt;https://github.com/pytest-dev/pytest/issues/7091&gt;`_: When ``fd`` capturing is used, through ``--capture=fd`` or the ``capfd`` and
  ``capfdbinary`` fixtures, and the file descriptor (0, 1, 2) cannot be
  duplicated, FD capturing is still performed. Previously, direct writes to the
  file descriptors would fail or be lost in this case.


- `7119 &lt;https://github.com/pytest-dev/pytest/issues/7119&gt;`_: Exit with an error if the ``--basetemp`` argument is empty, is the current working directory or is one of the parent directories.
  This is done to protect against accidental data loss, as any directory passed to this argument is cleared.


- `7128 &lt;https://github.com/pytest-dev/pytest/issues/7128&gt;`_: `pytest --version` now displays just the pytest version, while `pytest --version --version` displays more verbose information including plugins. This is more consistent with how other tools show `--version`.


- `7133 &lt;https://github.com/pytest-dev/pytest/issues/7133&gt;`_: :meth:`caplog.set_level() &lt;_pytest.logging.LogCaptureFixture.set_level&gt;` will now override any :confval:`log_level` set via the CLI or configuration file.


- `7159 &lt;https://github.com/pytest-dev/pytest/issues/7159&gt;`_: :meth:`caplog.set_level() &lt;_pytest.logging.LogCaptureFixture.set_level&gt;` and :meth:`caplog.at_level() &lt;_pytest.logging.LogCaptureFixture.at_level&gt;` no longer affect
  the level of logs that are shown in the *Captured log report* report section.


- `7348 &lt;https://github.com/pytest-dev/pytest/issues/7348&gt;`_: Improve recursive diff report for comparison asserts on dataclasses / attrs.


- `7385 &lt;https://github.com/pytest-dev/pytest/issues/7385&gt;`_: ``--junitxml`` now includes the exception cause in the ``message`` XML attribute for failures during setup and teardown.

  Previously:

  .. code-block:: xml

      &lt;error message=&quot;test setup failure&quot;&gt;

  Now:

  .. code-block:: xml

      &lt;error message=&quot;failed on setup with &amp;quot;ValueError: Some error during setup&amp;quot;&quot;&gt;



Bug Fixes
---------

- `1120 &lt;https://github.com/pytest-dev/pytest/issues/1120&gt;`_: Fix issue where directories from :fixture:`tmpdir` are not removed properly when multiple instances of pytest are running in parallel.


- `4583 &lt;https://github.com/pytest-dev/pytest/issues/4583&gt;`_: Prevent crashing and provide a user-friendly error when a marker expression (`-m`) invoking of :func:`eval` raises any exception.


- `4677 &lt;https://github.com/pytest-dev/pytest/issues/4677&gt;`_: The path shown in the summary report for SKIPPED tests is now always relative. Previously it was sometimes absolute.


- `5456 &lt;https://github.com/pytest-dev/pytest/issues/5456&gt;`_: Fix a possible race condition when trying to remove lock files used to control access to folders
  created by :fixture:`tmp_path` and :fixture:`tmpdir`.


- `6240 &lt;https://github.com/pytest-dev/pytest/issues/6240&gt;`_: Fixes an issue where logging during collection step caused duplication of log
  messages to stderr.


- `6428 &lt;https://github.com/pytest-dev/pytest/issues/6428&gt;`_: Paths appearing in error messages are now correct in case the current working directory has
  changed since the start of the session.


- `6755 &lt;https://github.com/pytest-dev/pytest/issues/6755&gt;`_: Support deleting paths longer than 260 characters on windows created inside :fixture:`tmpdir`.


- `6871 &lt;https://github.com/pytest-dev/pytest/issues/6871&gt;`_: Fix crash with captured output when using :fixture:`capsysbinary`.


- `6909 &lt;https://github.com/pytest-dev/pytest/issues/6909&gt;`_: Revert the change introduced by `#6330 &lt;https://github.com/pytest-dev/pytest/pull/6330&gt;`_, which required all arguments to ``pytest.mark.parametrize`` to be explicitly defined in the function signature.

  The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.


- `6910 &lt;https://github.com/pytest-dev/pytest/issues/6910&gt;`_: Fix crash when plugins return an unknown stats while using the ``--reportlog`` option.


- `6924 &lt;https://github.com/pytest-dev/pytest/issues/6924&gt;`_: Ensure a ``unittest.IsolatedAsyncioTestCase`` is actually awaited.


- `6925 &lt;https://github.com/pytest-dev/pytest/issues/6925&gt;`_: Fix `TerminalRepr` instances to be hashable again.


- `6947 &lt;https://github.com/pytest-dev/pytest/issues/6947&gt;`_: Fix regression where functions registered with :meth:`unittest.TestCase.addCleanup` were not being called on test failures.


- `6951 &lt;https://github.com/pytest-dev/pytest/issues/6951&gt;`_: Allow users to still set the deprecated ``TerminalReporter.writer`` attribute.


- `6956 &lt;https://github.com/pytest-dev/pytest/issues/6956&gt;`_: Prevent pytest from printing `ConftestImportFailure` traceback to stdout.


- `6991 &lt;https://github.com/pytest-dev/pytest/issues/6991&gt;`_: Fix regressions with `--lf` filtering too much since pytest 5.4.


- `6992 &lt;https://github.com/pytest-dev/pytest/issues/6992&gt;`_: Revert &quot;tmpdir: clean up indirection via config for factories&quot; `#6767 &lt;https://github.com/pytest-dev/pytest/issues/6767&gt;`_ as it breaks pytest-xdist.


- `7061 &lt;https://github.com/pytest-dev/pytest/issues/7061&gt;`_: When a yielding fixture fails to yield a value, report a test setup error instead of crashing.


- `7076 &lt;https://github.com/pytest-dev/pytest/issues/7076&gt;`_: The path of file skipped by ``pytest.mark.skip`` in the SKIPPED report is now relative to invocation directory. Previously it was relative to root directory.


- `7110 &lt;https://github.com/pytest-dev/pytest/issues/7110&gt;`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.


- `7126 &lt;https://github.com/pytest-dev/pytest/issues/7126&gt;`_: ``--setup-show`` now doesn&#39;t raise an error when a bytes value is used as a ``parametrize``
  parameter when Python is called with the ``-bb`` flag.


- `7143 &lt;https://github.com/pytest-dev/pytest/issues/7143&gt;`_: Fix :meth:`pytest.File.from_parent` so it forwards extra keyword arguments to the constructor.


- `7145 &lt;https://github.com/pytest-dev/pytest/issues/7145&gt;`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.


- `7150 &lt;https://github.com/pytest-dev/pytest/issues/7150&gt;`_: Prevent hiding the underlying exception when ``ConfTestImportFailure`` is raised.


- `7180 &lt;https://github.com/pytest-dev/pytest/issues/7180&gt;`_: Fix ``_is_setup_py`` for files encoded differently than locale.


- `7215 &lt;https://github.com/pytest-dev/pytest/issues/7215&gt;`_: Fix regression where running with ``--pdb`` would call :meth:`unittest.TestCase.tearDown` for skipped tests.


- `7253 &lt;https://github.com/pytest-dev/pytest/issues/7253&gt;`_: When using ``pytest.fixture`` on a function directly, as in ``pytest.fixture(func)``,
  if the ``autouse`` or ``params`` arguments are also passed, the function is no longer
  ignored, but is marked as a fixture.


- `7360 &lt;https://github.com/pytest-dev/pytest/issues/7360&gt;`_: Fix possibly incorrect evaluation of string expressions passed to ``pytest.mark.skipif`` and ``pytest.mark.xfail``,
  in rare circumstances where the exact same string is used but refers to different global values.


- `7383 &lt;https://github.com/pytest-dev/pytest/issues/7383&gt;`_: Fixed exception causes all over the codebase, i.e. use `raise new_exception from old_exception` when wrapping an exception.



Improved Documentation
----------------------

- `7202 &lt;https://github.com/pytest-dev/pytest/issues/7202&gt;`_: The development guide now links to the contributing section of the docs and `RELEASING.rst` on GitHub.


- `7233 &lt;https://github.com/pytest-dev/pytest/issues/7233&gt;`_: Add a note about ``--strict`` and ``--strict-markers`` and the preference for the latter one.


- `7345 &lt;https://github.com/pytest-dev/pytest/issues/7345&gt;`_: Explain indirect parametrization and markers for fixtures.



Trivial/Internal Changes
------------------------

- `7035 &lt;https://github.com/pytest-dev/pytest/issues/7035&gt;`_: The ``originalname`` attribute of ``_pytest.python.Function`` now defaults to ``name`` if not
  provided explicitly, and is always set.


- `7264 &lt;https://github.com/pytest-dev/pytest/issues/7264&gt;`_: The dependency on the ``wcwidth`` package has been removed.


- `7291 &lt;https://github.com/pytest-dev/pytest/issues/7291&gt;`_: Replaced ``py.iniconfig`` with `iniconfig &lt;https://pypi.org/project/iniconfig/&gt;`__.


- `7295 &lt;https://github.com/pytest-dev/pytest/issues/7295&gt;`_: ``src/_pytest/config/__init__.py`` now uses the ``warnings`` module to report warnings instead of ``sys.stderr.write``.


- `7356 &lt;https://github.com/pytest-dev/pytest/issues/7356&gt;`_: Remove last internal uses of deprecated *slave* term from old ``pytest-xdist``.


- `7357 &lt;https://github.com/pytest-dev/pytest/issues/7357&gt;`_: ``py``&gt;=1.8.2 is now required.
   ```
   
  
  
   ### 5.4.3
   ```
   =========================

Bug Fixes
---------

- `6428 &lt;https://github.com/pytest-dev/pytest/issues/6428&gt;`_: Paths appearing in error messages are now correct in case the current working directory has
  changed since the start of the session.


- `6755 &lt;https://github.com/pytest-dev/pytest/issues/6755&gt;`_: Support deleting paths longer than 260 characters on windows created inside tmpdir.


- `6956 &lt;https://github.com/pytest-dev/pytest/issues/6956&gt;`_: Prevent pytest from printing ConftestImportFailure traceback to stdout.


- `7150 &lt;https://github.com/pytest-dev/pytest/issues/7150&gt;`_: Prevent hiding the underlying exception when ``ConfTestImportFailure`` is raised.


- `7215 &lt;https://github.com/pytest-dev/pytest/issues/7215&gt;`_: Fix regression where running with ``--pdb`` would call the ``tearDown`` methods of ``unittest.TestCase``
  subclasses for skipped tests.
   ```
   
  
  
   ### 5.4.2
   ```
   =========================

Bug Fixes
---------

- `6871 &lt;https://github.com/pytest-dev/pytest/issues/6871&gt;`_: Fix crash with captured output when using the :fixture:`capsysbinary fixture &lt;capsysbinary&gt;`.


- `6924 &lt;https://github.com/pytest-dev/pytest/issues/6924&gt;`_: Ensure a ``unittest.IsolatedAsyncioTestCase`` is actually awaited.


- `6925 &lt;https://github.com/pytest-dev/pytest/issues/6925&gt;`_: Fix TerminalRepr instances to be hashable again.


- `6947 &lt;https://github.com/pytest-dev/pytest/issues/6947&gt;`_: Fix regression where functions registered with ``TestCase.addCleanup`` were not being called on test failures.


- `6951 &lt;https://github.com/pytest-dev/pytest/issues/6951&gt;`_: Allow users to still set the deprecated ``TerminalReporter.writer`` attribute.


- `6992 &lt;https://github.com/pytest-dev/pytest/issues/6992&gt;`_: Revert &quot;tmpdir: clean up indirection via config for factories&quot; #6767 as it breaks pytest-xdist.


- `7110 &lt;https://github.com/pytest-dev/pytest/issues/7110&gt;`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.


- `7143 &lt;https://github.com/pytest-dev/pytest/issues/7143&gt;`_: Fix ``File.from_parent`` so it forwards extra keyword arguments to the constructor.


- `7145 &lt;https://github.com/pytest-dev/pytest/issues/7145&gt;`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.


- `7180 &lt;https://github.com/pytest-dev/pytest/issues/7180&gt;`_: Fix ``_is_setup_py`` for files encoded differently than locale.
   ```
   
  
  
   ### 5.4.1
   ```
   =========================

Bug Fixes
---------

- `6909 &lt;https://github.com/pytest-dev/pytest/issues/6909&gt;`_: Revert the change introduced by `#6330 &lt;https://github.com/pytest-dev/pytest/pull/6330&gt;`_, which required all arguments to ``pytest.mark.parametrize`` to be explicitly defined in the function signature.

  The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.


- `6910 &lt;https://github.com/pytest-dev/pytest/issues/6910&gt;`_: Fix crash when plugins return an unknown stats while using the ``--reportlog`` option.
   ```
   
  
  
   ### 5.4.0
   ```
   =========================

Breaking Changes
----------------

- `6316 &lt;https://github.com/pytest-dev/pytest/issues/6316&gt;`_: Matching of ``-k EXPRESSION`` to test names is now case-insensitive.


- `6443 &lt;https://github.com/pytest-dev/pytest/issues/6443&gt;`_: Plugins specified with ``-p`` are now loaded after internal plugins, which results in their hooks being called *before* the internal ones.

  This makes the ``-p`` behavior consistent with ``PYTEST_PLUGINS``.


- `6637 &lt;https://github.com/pytest-dev/pytest/issues/6637&gt;`_: Removed the long-deprecated ``pytest_itemstart`` hook.

  This hook has been marked as deprecated and not been even called by pytest for over 10 years now.


- `6673 &lt;https://github.com/pytest-dev/pytest/issues/6673&gt;`_: Reversed / fix meaning of &quot;+/-&quot; in error diffs.  &quot;-&quot; means that sth. expected is missing in the result and &quot;+&quot; means that there are unexpected extras in the result.


- `6737 &lt;https://github.com/pytest-dev/pytest/issues/6737&gt;`_: The ``cached_result`` attribute of ``FixtureDef`` is now set to ``None`` when
  the result is unavailable, instead of being deleted.

  If your plugin performs checks like ``hasattr(fixturedef, &#39;cached_result&#39;)``,
  for example in a ``pytest_fixture_post_finalizer`` hook implementation, replace
  it with ``fixturedef.cached_result is not None``. If you ``del`` the attribute,
  set it to ``None`` instead.



Deprecations
------------

- `3238 &lt;https://github.com/pytest-dev/pytest/issues/3238&gt;`_: Option ``--no-print-logs`` is deprecated and meant to be removed in a future release. If you use ``--no-print-logs``, please try out ``--show-capture`` and
  provide feedback.

  ``--show-capture`` command-line option was added in ``pytest 3.5.0`` and allows to specify how to
  display captured output when tests fail: ``no``, ``stdout``, ``stderr``, ``log`` or ``all`` (the default).


- `571 &lt;https://github.com/pytest-dev/pytest/issues/571&gt;`_: Deprecate the unused/broken `pytest_collect_directory` hook.
  It was misaligned since the removal of the ``Directory`` collector in 2010
  and incorrect/unusable as soon as collection was split from test execution.


- `5975 &lt;https://github.com/pytest-dev/pytest/issues/5975&gt;`_: Deprecate using direct constructors for ``Nodes``.

  Instead they are now constructed via ``Node.from_parent``.

  This transitional mechanism enables us to untangle the very intensely
  entangled ``Node`` relationships by enforcing more controlled creation/configuration patterns.

  As part of this change, session/config are already disallowed parameters and as we work on the details we might need disallow a few more as well.

  Subclasses are expected to use `super().from_parent` if they intend to expand the creation of `Nodes`.


- `6779 &lt;https://github.com/pytest-dev/pytest/issues/6779&gt;`_: The ``TerminalReporter.writer`` attribute has been deprecated and should no longer be used. This
  was inadvertently exposed as part of the public API of that plugin and ties it too much
  with ``py.io.TerminalWriter``.



Features
--------

- `4597 &lt;https://github.com/pytest-dev/pytest/issues/4597&gt;`_: New :ref:`--capture=tee-sys &lt;capture-method&gt;` option to allow both live printing and capturing of test output.


- `5712 &lt;https://github.com/pytest-dev/pytest/issues/5712&gt;`_: Now all arguments to ``pytest.mark.parametrize`` need to be explicitly declared in the function signature or via ``indirect``.
  Previously it was possible to omit an argument if a fixture with the same name existed, which was just an accident of implementation and was not meant to be a part of the API.


- `6454 &lt;https://github.com/pytest-dev/pytest/issues/6454&gt;`_: Changed default for `-r` to `fE`, which displays failures and errors in the :ref:`short test summary &lt;pytest.detailed_failed_tests_usage&gt;`.  `-rN` can be used to disable it (the old behavior).


- `6469 &lt;https://github.com/pytest-dev/pytest/issues/6469&gt;`_: New options have been added to the :confval:`junit_logging` option: ``log``, ``out-err``, and ``all``.


- `6834 &lt;https://github.com/pytest-dev/pytest/issues/6834&gt;`_: Excess warning summaries are now collapsed per file to ensure readable display of warning summaries.



Improvements
------------

- `1857 &lt;https://github.com/pytest-dev/pytest/issues/1857&gt;`_: ``pytest.mark.parametrize`` accepts integers for ``ids`` again, converting it to strings.


- `449 &lt;https://github.com/pytest-dev/pytest/issues/449&gt;`_: Use &quot;yellow&quot; main color with any XPASSED tests.


- `4639 &lt;https://github.com/pytest-dev/pytest/issues/4639&gt;`_: Revert &quot;A warning is now issued when assertions are made for ``None``&quot;.

  The warning proved to be less useful than initially expected and had quite a
  few false positive cases.


- `5686 &lt;https://github.com/pytest-dev/pytest/issues/5686&gt;`_: ``tmpdir_factory.mktemp`` now fails when given absolute and non-normalized paths.


- `5984 &lt;https://github.com/pytest-dev/pytest/issues/5984&gt;`_: The ``pytest_warning_captured`` hook now receives a ``location`` parameter with the code location that generated the warning.


- `6213 &lt;https://github.com/pytest-dev/pytest/issues/6213&gt;`_: pytester: the ``testdir`` fixture respects environment settings from the ``monkeypatch`` fixture for inner runs.


- `6247 &lt;https://github.com/pytest-dev/pytest/issues/6247&gt;`_: ``--fulltrace`` is honored with collection errors.


- `6384 &lt;https://github.com/pytest-dev/pytest/issues/6384&gt;`_: Make `--showlocals` work also with `--tb=short`.


- `6653 &lt;https://github.com/pytest-dev/pytest/issues/6653&gt;`_: Add support for matching lines consecutively with :attr:`LineMatcher &lt;_pytest.pytester.LineMatcher&gt;`&#39;s :func:`~_pytest.pytester.LineMatcher.fnmatch_lines` and :func:`~_pytest.pytester.LineMatcher.re_match_lines`.


- `6658 &lt;https://github.com/pytest-dev/pytest/issues/6658&gt;`_: Code is now highlighted in tracebacks when ``pygments`` is installed.

  Users are encouraged to install ``pygments`` into their environment and provide feedback, because
  the plan is to make ``pygments`` a regular dependency in the future.


- `6795 &lt;https://github.com/pytest-dev/pytest/issues/6795&gt;`_: Import usage error message with invalid `-o` option.


- `759 &lt;https://github.com/pytest-dev/pytest/issues/759&gt;`_: ``pytest.mark.parametrize`` supports iterators and generators for ``ids``.



Bug Fixes
---------

- `310 &lt;https://github.com/pytest-dev/pytest/issues/310&gt;`_: Add support for calling `pytest.xfail()` and `pytest.importorskip()` with doctests.


- `3823 &lt;https://github.com/pytest-dev/pytest/issues/3823&gt;`_: ``--trace`` now works with unittests.


- `4445 &lt;https://github.com/pytest-dev/pytest/issues/4445&gt;`_: Fixed some warning reports produced by pytest to point to the correct location of the warning in the user&#39;s code.


- `5301 &lt;https://github.com/pytest-dev/pytest/issues/5301&gt;`_: Fix ``--last-failed`` to collect new tests from files with known failures.


- `5928 &lt;https://github.com/pytest-dev/pytest/issues/5928&gt;`_: Report ``PytestUnknownMarkWarning`` at the level of the user&#39;s code, not ``pytest``&#39;s.


- `5991 &lt;https://github.com/pytest-dev/pytest/issues/5991&gt;`_: Fix interaction with ``--pdb`` and unittests: do not use unittest&#39;s ``TestCase.debug()``.


- `6334 &lt;https://github.com/pytest-dev/pytest/issues/6334&gt;`_: Fix summary entries appearing twice when ``f/F`` and ``s/S`` report chars were used at the same time in the ``-r`` command-line option (for example ``-rFf``).

  The upper case variants were never documented and the preferred form should be the lower case.


- `6409 &lt;https://github.com/pytest-dev/pytest/issues/6409&gt;`_: Fallback to green (instead of yellow) for non-last items without previous passes with colored terminal progress indicator.


- `6454 &lt;https://github.com/pytest-dev/pytest/issues/6454&gt;`_: `--disable-warnings` is honored with `-ra` and `-rA`.


- `6497 &lt;https://github.com/pytest-dev/pytest/issues/6497&gt;`_: Fix bug in the comparison of request key with cached key in fixture.

  A construct ``if key == cached_key:`` can fail either because ``==`` is explicitly disallowed, or for, e.g., NumPy arrays, where the result of ``a == b`` cannot generally be converted to `bool`.
  The implemented fix replaces `==` with ``is``.


- `6557 &lt;https://github.com/pytest-dev/pytest/issues/6557&gt;`_: Make capture output streams ``.write()`` method return the same return value from original streams.


- `6566 &lt;https://github.com/pytest-dev/pytest/issues/6566&gt;`_: Fix ``EncodedFile.writelines`` to call the underlying buffer&#39;s ``writelines`` method.


- `6575 &lt;https://github.com/pytest-dev/pytest/issues/6575&gt;`_: Fix internal crash when ``faulthandler`` starts initialized
  (for example with ``PYTHONFAULTHANDLER=1`` environment variable set) and ``faulthandler_timeout`` defined
  in the configuration file.


- `6597 &lt;https://github.com/pytest-dev/pytest/issues/6597&gt;`_: Fix node ids which contain a parametrized empty-string variable.


- `6646 &lt;https://github.com/pytest-dev/pytest/issues/6646&gt;`_: Assertion rewriting hooks are (re)stored for the current item, which fixes them being still used after e.g. pytester&#39;s :func:`testdir.runpytest &lt;_pytest.pytester.Testdir.runpytest&gt;` etc.


- `6660 &lt;https://github.com/pytest-dev/pytest/issues/6660&gt;`_: :py:func:`pytest.exit` is handled when emitted from the :func:`pytest_sessionfinish &lt;_pytest.hookspec.pytest_sessionfinish&gt;` hook.  This includes quitting from a debugger.


- `6752 &lt;https://github.com/pytest-dev/pytest/issues/6752&gt;`_: When :py:func:`pytest.raises` is used as a function (as opposed to a context manager),
  a `match` keyword argument is now passed through to the tested function. Previously
  it was swallowed and ignored (regression in pytest 5.1.0).


- `6801 &lt;https://github.com/pytest-dev/pytest/issues/6801&gt;`_: Do not display empty lines inbetween traceback for unexpected exceptions with doctests.


- `6802 &lt;https://github.com/pytest-dev/pytest/issues/6802&gt;`_: The :fixture:`testdir fixture &lt;testdir&gt;` works within doctests now.



Improved Documentation
----------------------

- `6696 &lt;https://github.com/pytest-dev/pytest/issues/6696&gt;`_: Add list of fixtures to start of fixture chapter.


- `6742 &lt;https://github.com/pytest-dev/pytest/issues/6742&gt;`_: Expand first sentence on fixtures into a paragraph.



Trivial/Internal Changes
------------------------

- `6404 &lt;https://github.com/pytest-dev/pytest/issues/6404&gt;`_: Remove usage of ``parser`` module, deprecated in Python 3.9.
   ```
   
  
  
   ### 5.3.5
   ```
   =========================

Bug Fixes
---------

- `6517 &lt;https://github.com/pytest-dev/pytest/issues/6517&gt;`_: Fix regression in pytest 5.3.4 causing an INTERNALERROR due to a wrong assertion.
   ```
   
  
  
   ### 5.3.4
   ```
   =========================

Bug Fixes
---------

- `6496 &lt;https://github.com/pytest-dev/pytest/issues/6496&gt;`_: Revert `#6436 &lt;https://github.com/pytest-dev/pytest/issues/6436&gt;`__: unfortunately this change has caused a number of regressions in many suites,
  so the team decided to revert this change and make a new release while we continue to look for a solution.
   ```
   
  
  
   ### 5.3.3
   ```
   =========================

Bug Fixes
---------

- `2780 &lt;https://github.com/pytest-dev/pytest/issues/2780&gt;`_: Captured output during teardown is shown with ``-rP``.


- `5971 &lt;https://github.com/pytest-dev/pytest/issues/5971&gt;`_: Fix a ``pytest-xdist`` crash when dealing with exceptions raised in subprocesses created by the
  ``multiprocessing`` module.


- `6436 &lt;https://github.com/pytest-dev/pytest/issues/6436&gt;`_: :class:`FixtureDef &lt;_pytest.fixtures.FixtureDef&gt;` objects now properly register their finalizers with autouse and
  parameterized fixtures that execute before them in the fixture stack so they are torn
  down at the right times, and in the right order.


- `6532 &lt;https://github.com/pytest-dev/pytest/issues/6532&gt;`_: Fix parsing of outcomes containing multiple errors with ``testdir`` results (regression in 5.3.0).



Trivial/Internal Changes
------------------------

- `6350 &lt;https://github.com/pytest-dev/pytest/issues/6350&gt;`_: Optimized automatic renaming of test parameter IDs.
   ```
   
  
  
   ### 5.3.2
   ```
   =========================

Improvements
------------

- `4639 &lt;https://github.com/pytest-dev/pytest/issues/4639&gt;`_: Revert &quot;A warning is now issued when assertions are made for ``None``&quot;.

  The warning proved to be less useful than initially expected and had quite a
  few false positive cases.



Bug Fixes
---------

- `5430 &lt;https://github.com/pytest-dev/pytest/issues/5430&gt;`_: junitxml: Logs for failed test are now passed to junit report in case the test fails during call phase.


- `6290 &lt;https://github.com/pytest-dev/pytest/issues/6290&gt;`_: The supporting files in the ``.pytest_cache`` directory are kept with ``--cache-clear``, which only clears cached values now.


- `6301 &lt;https://github.com/pytest-dev/pytest/issues/6301&gt;`_: Fix assertion rewriting for egg-based distributions and ``editable`` installs (``pip install --editable``).
   ```
   
  
  
   ### 5.3.1
   ```
   =========================

Improvements
------------

- `6231 &lt;https://github.com/pytest-dev/pytest/issues/6231&gt;`_: Improve check for misspelling of :ref:`pytest.mark.parametrize ref`.


- `6257 &lt;https://github.com/pytest-dev/pytest/issues/6257&gt;`_: Handle :py:func:`pytest.exit` being used via :py:func:`~_pytest.hookspec.pytest_internalerror`, e.g. when quitting pdb from post mortem.



Bug Fixes
---------

- `5914 &lt;https://github.com/pytest-dev/pytest/issues/5914&gt;`_: pytester: fix :py:func:`~_pytest.pytester.LineMatcher.no_fnmatch_line` when used after positive matching.


- `6082 &lt;https://github.com/pytest-dev/pytest/issues/6082&gt;`_: Fix line detection for doctest samples inside :py:class:`python:property` docstrings, as a workaround to `bpo-17446 &lt;https://bugs.python.org/issue17446&gt;`__.


- `6254 &lt;https://github.com/pytest-dev/pytest/issues/6254&gt;`_: Fix compatibility with pytest-parallel (regression in pytest 5.3.0).


- `6255 &lt;https://github.com/pytest-dev/pytest/issues/6255&gt;`_: Clear the :py:data:`sys.last_traceback`, :py:data:`sys.last_type`
  and :py:data:`sys.last_value` attributes by deleting them instead
  of setting them to ``None``. This better matches the behaviour of
  the Python standard library.
   ```
   
  
  
   ### 5.3.0
   ```
   =========================

Deprecations
------------

- `6179 &lt;https://github.com/pytest-dev/pytest/issues/6179&gt;`_: The default value of :confval:`junit_family` option will change to ``&quot;xunit2&quot;`` in pytest 6.0, given
  that this is the version supported by default in modern tools that manipulate this type of file.

  In order to smooth the transition, pytest will issue a warning in case the ``--junitxml`` opti…
bors bot added a commit to aragilar/spaceplot that referenced this issue Aug 6, 2021
3: Pin sphinx_rtd_theme to latest version 0.5.1 r=aragilar a=pyup-bot


This PR pins [sphinx_rtd_theme](https://pypi.org/project/sphinx_rtd_theme) to the latest release **0.5.1**.



*The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)*

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/sphinx-rtd-theme
  - Repo: https://github.com/readthedocs/sphinx_rtd_theme
</details>



4: Pin pytest to latest version 6.2.2 r=aragilar a=pyup-bot


This PR pins [pytest](https://pypi.org/project/pytest) to the latest release **6.2.2**.



<details>
  <summary>Changelog</summary>
  
  
   ### 6.2.2
   ```
   =========================

Bug Fixes
---------

- `8152 &lt;https://github.com/pytest-dev/pytest/issues/8152&gt;`_: Fixed &quot;(&lt;Skipped instance&gt;)&quot; being shown as a skip reason in the verbose test summary line when the reason is empty.


- `8249 &lt;https://github.com/pytest-dev/pytest/issues/8249&gt;`_: Fix the ``faulthandler`` plugin for occasions when running with ``twisted.logger`` and using ``pytest --capture=no``.
   ```
   
  
  
   ### 6.2.1
   ```
   =========================

Bug Fixes
---------

- `7678 &lt;https://github.com/pytest-dev/pytest/issues/7678&gt;`_: Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in
  the host and loaded later from an UNC mounted path (Windows).


- `8132 &lt;https://github.com/pytest-dev/pytest/issues/8132&gt;`_: Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises
  ``TypeError`` when dealing with non-numeric types, falling back to normal comparison.
  Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
  and happened to compare correctly to a scalar if they had only one element.
  After 6.2.0, these types began failing, because they inherited neither from
  standard Python number hierarchy nor from ``numpy.ndarray``.

  ``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array
  protocol and are not scalars. This treats array-like objects like numpy arrays,
  regardless of size.
   ```
   
  
  
   ### 6.2.0
   ```
   =========================

Breaking Changes
----------------

- `7808 &lt;https://github.com/pytest-dev/pytest/issues/7808&gt;`_: pytest now supports python3.6+ only.



Deprecations
------------

- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_: Directly constructing/calling the following classes/functions is now deprecated:

  - ``_pytest.cacheprovider.Cache``
  - ``_pytest.cacheprovider.Cache.for_config()``
  - ``_pytest.cacheprovider.Cache.clear_cache()``
  - ``_pytest.cacheprovider.Cache.cache_dir_from_config()``
  - ``_pytest.capture.CaptureFixture``
  - ``_pytest.fixtures.FixtureRequest``
  - ``_pytest.fixtures.SubRequest``
  - ``_pytest.logging.LogCaptureFixture``
  - ``_pytest.pytester.Pytester``
  - ``_pytest.pytester.Testdir``
  - ``_pytest.recwarn.WarningsRecorder``
  - ``_pytest.recwarn.WarningsChecker``
  - ``_pytest.tmpdir.TempPathFactory``
  - ``_pytest.tmpdir.TempdirFactory``

  These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.


- `7530 &lt;https://github.com/pytest-dev/pytest/issues/7530&gt;`_: The ``--strict`` command-line option has been deprecated, use ``--strict-markers`` instead.

  We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing flag for all strictness
  related options (``--strict-markers`` and ``--strict-config`` at the moment, more might be introduced in the future).


- `7988 &lt;https://github.com/pytest-dev/pytest/issues/7988&gt;`_: The ``pytest.yield_fixture`` decorator/function is now deprecated. Use :func:`pytest.fixture` instead.

  ``yield_fixture`` has been an alias for ``fixture`` for a very long time, so can be search/replaced safely.



Features
--------

- `5299 &lt;https://github.com/pytest-dev/pytest/issues/5299&gt;`_: pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python&gt;=3.8.
  See :ref:`unraisable` for more information.


- `7425 &lt;https://github.com/pytest-dev/pytest/issues/7425&gt;`_: New :fixture:`pytester` fixture, which is identical to :fixture:`testdir` but its methods return :class:`pathlib.Path` when appropriate instead of ``py.path.local``.

  This is part of the movement to use :class:`pathlib.Path` objects internally, in order to remove the dependency to ``py`` in the future.

  Internally, the old :class:`Testdir &lt;_pytest.pytester.Testdir&gt;` is now a thin wrapper around :class:`Pytester &lt;_pytest.pytester.Pytester&gt;`, preserving the old interface.


- `7695 &lt;https://github.com/pytest-dev/pytest/issues/7695&gt;`_: A new hook was added, `pytest_markeval_namespace` which should return a dictionary.
  This dictionary will be used to augment the &quot;global&quot; variables available to evaluate skipif/xfail/xpass markers.

  Pseudo example

  ``conftest.py``:

  .. code-block:: python

     def pytest_markeval_namespace():
         return {&quot;color&quot;: &quot;red&quot;}

  ``test_func.py``:

  .. code-block:: python

     pytest.mark.skipif(&quot;color == &#39;blue&#39;&quot;, reason=&quot;Color is not red&quot;)
     def test_func():
         assert False


- `8006 &lt;https://github.com/pytest-dev/pytest/issues/8006&gt;`_: It is now possible to construct a :class:`~pytest.MonkeyPatch` object directly as ``pytest.MonkeyPatch()``,
  in cases when the :fixture:`monkeypatch` fixture cannot be used. Previously some users imported it
  from the private `_pytest.monkeypatch.MonkeyPatch` namespace.

  Additionally, :meth:`MonkeyPatch.context &lt;pytest.MonkeyPatch.context&gt;` is now a classmethod,
  and can be used as ``with MonkeyPatch.context() as mp: ...``. This is the recommended way to use
  ``MonkeyPatch`` directly, since unlike the ``monkeypatch`` fixture, an instance created directly
  is not ``undo()``-ed automatically.



Improvements
------------

- `1265 &lt;https://github.com/pytest-dev/pytest/issues/1265&gt;`_: Added an ``__str__`` implementation to the :class:`~pytest.pytester.LineMatcher` class which is returned from ``pytester.run_pytest().stdout`` and similar. It returns the entire output, like the existing ``str()`` method.


- `2044 &lt;https://github.com/pytest-dev/pytest/issues/2044&gt;`_: Verbose mode now shows the reason that a test was skipped in the test&#39;s terminal line after the &quot;SKIPPED&quot;, &quot;XFAIL&quot; or &quot;XPASS&quot;.


- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_ The types of builtin pytest fixtures are now exported so they may be used in type annotations of test functions.
  The newly-exported types are:

  - ``pytest.FixtureRequest`` for the :fixture:`request` fixture.
  - ``pytest.Cache`` for the :fixture:`cache` fixture.
  - ``pytest.CaptureFixture[str]`` for the :fixture:`capfd` and :fixture:`capsys` fixtures.
  - ``pytest.CaptureFixture[bytes]`` for the :fixture:`capfdbinary` and :fixture:`capsysbinary` fixtures.
  - ``pytest.LogCaptureFixture`` for the :fixture:`caplog` fixture.
  - ``pytest.Pytester`` for the :fixture:`pytester` fixture.
  - ``pytest.Testdir`` for the :fixture:`testdir` fixture.
  - ``pytest.TempdirFactory`` for the :fixture:`tmpdir_factory` fixture.
  - ``pytest.TempPathFactory`` for the :fixture:`tmp_path_factory` fixture.
  - ``pytest.MonkeyPatch`` for the :fixture:`monkeypatch` fixture.
  - ``pytest.WarningsRecorder`` for the :fixture:`recwarn` fixture.

  Constructing them is not supported (except for `MonkeyPatch`); they are only meant for use in type annotations.
  Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.

  Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.


- `7527 &lt;https://github.com/pytest-dev/pytest/issues/7527&gt;`_: When a comparison between :func:`namedtuple &lt;collections.namedtuple&gt;` instances of the same type fails, pytest now shows the differing field names (possibly nested) instead of their indexes.


- `7615 &lt;https://github.com/pytest-dev/pytest/issues/7615&gt;`_: :meth:`Node.warn &lt;_pytest.nodes.Node.warn&gt;` now permits any subclass of :class:`Warning`, not just :class:`PytestWarning &lt;pytest.PytestWarning&gt;`.


- `7701 &lt;https://github.com/pytest-dev/pytest/issues/7701&gt;`_: Improved reporting when using ``--collected-only``. It will now show the number of collected tests in the summary stats.


- `7710 &lt;https://github.com/pytest-dev/pytest/issues/7710&gt;`_: Use strict equality comparison for non-numeric types in :func:`pytest.approx` instead of
  raising :class:`TypeError`.

  This was the undocumented behavior before 3.7, but is now officially a supported feature.


- `7938 &lt;https://github.com/pytest-dev/pytest/issues/7938&gt;`_: New ``--sw-skip`` argument which is a shorthand for ``--stepwise-skip``.


- `8023 &lt;https://github.com/pytest-dev/pytest/issues/8023&gt;`_: Added ``&#39;node_modules&#39;`` to default value for :confval:`norecursedirs`.


- `8032 &lt;https://github.com/pytest-dev/pytest/issues/8032&gt;`_: :meth:`doClassCleanups &lt;unittest.TestCase.doClassCleanups&gt;` (introduced in :mod:`unittest` in Python and 3.8) is now called appropriately.



Bug Fixes
---------

- `4824 &lt;https://github.com/pytest-dev/pytest/issues/4824&gt;`_: Fixed quadratic behavior and improved performance of collection of items using autouse fixtures and xunit fixtures.


- `7758 &lt;https://github.com/pytest-dev/pytest/issues/7758&gt;`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.


- `7911 &lt;https://github.com/pytest-dev/pytest/issues/7911&gt;`_: Directories created by by :fixture:`tmp_path` and :fixture:`tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.


- `7913 &lt;https://github.com/pytest-dev/pytest/issues/7913&gt;`_: Fixed a crash or hang in :meth:`pytester.spawn &lt;_pytest.pytester.Pytester.spawn&gt;` when the :mod:`readline` module is involved.


- `7951 &lt;https://github.com/pytest-dev/pytest/issues/7951&gt;`_: Fixed handling of recursive symlinks when collecting tests.


- `7981 &lt;https://github.com/pytest-dev/pytest/issues/7981&gt;`_: Fixed symlinked directories not being followed during collection. Regressed in pytest 6.1.0.


- `8016 &lt;https://github.com/pytest-dev/pytest/issues/8016&gt;`_: Fixed only one doctest being collected when using ``pytest --doctest-modules path/to/an/__init__.py``.



Improved Documentation
----------------------

- `7429 &lt;https://github.com/pytest-dev/pytest/issues/7429&gt;`_: Add more information and use cases about skipping doctests.


- `7780 &lt;https://github.com/pytest-dev/pytest/issues/7780&gt;`_: Classes which should not be inherited from are now marked ``final class`` in the API reference.


- `7872 &lt;https://github.com/pytest-dev/pytest/issues/7872&gt;`_: ``_pytest.config.argparsing.Parser.addini()`` accepts explicit ``None`` and ``&quot;string&quot;``.


- `7878 &lt;https://github.com/pytest-dev/pytest/issues/7878&gt;`_: In pull request section, ask to commit after editing changelog and authors file.



Trivial/Internal Changes
------------------------

- `7802 &lt;https://github.com/pytest-dev/pytest/issues/7802&gt;`_: The ``attrs`` dependency requirement is now &gt;=19.2.0 instead of &gt;=17.4.0.


- `8014 &lt;https://github.com/pytest-dev/pytest/issues/8014&gt;`_: `.pyc` files created by pytest&#39;s assertion rewriting now conform to the newer PEP-552 format on Python&gt;=3.7.
  (These files are internal and only interpreted by pytest itself.)
   ```
   
  
  
   ### 6.1.2
   ```
   =========================

Bug Fixes
---------

- `7758 &lt;https://github.com/pytest-dev/pytest/issues/7758&gt;`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.


- `7911 &lt;https://github.com/pytest-dev/pytest/issues/7911&gt;`_: Directories created by `tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.



Improved Documentation
----------------------

- `7815 &lt;https://github.com/pytest-dev/pytest/issues/7815&gt;`_: Improve deprecation warning message for ``pytest._fillfuncargs()``.
   ```
   
  
  
   ### 6.1.1
   ```
   =========================

Bug Fixes
---------

- `7807 &lt;https://github.com/pytest-dev/pytest/issues/7807&gt;`_: Fixed regression in pytest 6.1.0 causing incorrect rootdir to be determined in some non-trivial cases where parent directories have config files as well.


- `7814 &lt;https://github.com/pytest-dev/pytest/issues/7814&gt;`_: Fixed crash in header reporting when :confval:`testpaths` is used and contains absolute paths (regression in 6.1.0).
   ```
   
  
  
   ### 6.1.0
   ```
   =========================

Breaking Changes
----------------

- `5585 &lt;https://github.com/pytest-dev/pytest/issues/5585&gt;`_: As per our policy, the following features which have been deprecated in the 5.X series are now
  removed:

  * The ``funcargnames`` read-only property of ``FixtureRequest``, ``Metafunc``, and ``Function`` classes. Use ``fixturenames`` attribute.

  * ``pytest.fixture`` no longer supports positional arguments, pass all arguments by keyword instead.

  * Direct construction of ``Node`` subclasses now raise an error, use ``from_parent`` instead.

  * The default value for ``junit_family`` has changed to ``xunit2``. If you require the old format, add ``junit_family=xunit1`` to your configuration file.

  * The ``TerminalReporter`` no longer has a ``writer`` attribute. Plugin authors may use the public functions of the ``TerminalReporter`` instead of accessing the ``TerminalWriter`` object directly.

  * The ``--result-log`` option has been removed. Users are recommended to use the `pytest-reportlog &lt;https://github.com/pytest-dev/pytest-reportlog&gt;`__ plugin instead.


  For more information consult
  `Deprecations and Removals &lt;https://docs.pytest.org/en/stable/deprecations.html&gt;`__ in the docs.



Deprecations
------------

- `6981 &lt;https://github.com/pytest-dev/pytest/issues/6981&gt;`_: The ``pytest.collect`` module is deprecated: all its names can be imported from ``pytest`` directly.


- `7097 &lt;https://github.com/pytest-dev/pytest/issues/7097&gt;`_: The ``pytest._fillfuncargs`` function is deprecated. This function was kept
  for backward compatibility with an older plugin.

  It&#39;s functionality is not meant to be used directly, but if you must replace
  it, use `function._request._fillfixtures()` instead, though note this is not
  a public API and may break in the future.


- `7210 &lt;https://github.com/pytest-dev/pytest/issues/7210&gt;`_: The special ``-k &#39;-expr&#39;`` syntax to ``-k`` is deprecated. Use ``-k &#39;not expr&#39;``
  instead.

  The special ``-k &#39;expr:&#39;`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.


- `7255 &lt;https://github.com/pytest-dev/pytest/issues/7255&gt;`_: The :func:`pytest_warning_captured &lt;_pytest.hookspec.pytest_warning_captured&gt;` hook is deprecated in favor
  of :func:`pytest_warning_recorded &lt;_pytest.hookspec.pytest_warning_recorded&gt;`, and will be removed in a future version.


- `7648 &lt;https://github.com/pytest-dev/pytest/issues/7648&gt;`_: The ``gethookproxy()`` and ``isinitpath()`` methods of ``FSCollector`` and ``Package`` are deprecated;
  use ``self.session.gethookproxy()`` and ``self.session.isinitpath()`` instead.
  This should work on all pytest versions.



Features
--------

- `7667 &lt;https://github.com/pytest-dev/pytest/issues/7667&gt;`_: New ``--durations-min`` command-line flag controls the minimal duration for inclusion in the slowest list of tests shown by ``--durations``. Previously this was hard-coded to ``0.005s``.



Improvements
------------

- `6681 &lt;https://github.com/pytest-dev/pytest/issues/6681&gt;`_: Internal pytest warnings issued during the early stages of initialization are now properly handled and can filtered through :confval:`filterwarnings` or ``--pythonwarnings/-W``.

  This also fixes a number of long standing issues: `2891 &lt;https://github.com/pytest-dev/pytest/issues/2891&gt;`__, `#7620 &lt;https://github.com/pytest-dev/pytest/issues/7620&gt;`__, `#7426 &lt;https://github.com/pytest-dev/pytest/issues/7426&gt;`__.


- `7572 &lt;https://github.com/pytest-dev/pytest/issues/7572&gt;`_: When a plugin listed in ``required_plugins`` is missing or an unknown config key is used with ``--strict-config``, a simple error message is now shown instead of a stacktrace.


- `7685 &lt;https://github.com/pytest-dev/pytest/issues/7685&gt;`_: Added two new attributes :attr:`rootpath &lt;_pytest.config.Config.rootpath&gt;` and :attr:`inipath &lt;_pytest.config.Config.inipath&gt;` to :class:`Config &lt;_pytest.config.Config&gt;`.
  These attributes are :class:`pathlib.Path` versions of the existing :attr:`rootdir &lt;_pytest.config.Config.rootdir&gt;` and :attr:`inifile &lt;_pytest.config.Config.inifile&gt;` attributes,
  and should be preferred over them when possible.


- `7780 &lt;https://github.com/pytest-dev/pytest/issues/7780&gt;`_: Public classes which are not designed to be inherited from are now marked `final &lt;https://docs.python.org/3/library/typing.html#typing.final&gt;`_.
  Code which inherits from these classes will trigger a type-checking (e.g. mypy) error, but will still work in runtime.
  Currently the ``final`` designation does not appear in the API Reference but hopefully will in the future.



Bug Fixes
---------

- `1953 &lt;https://github.com/pytest-dev/pytest/issues/1953&gt;`_: Fixed error when overwriting a parametrized fixture, while also reusing the super fixture value.

  .. code-block:: python

       conftest.py
      import pytest


      pytest.fixture(params=[1, 2])
      def foo(request):
          return request.param


       test_foo.py
      import pytest


      pytest.fixture
      def foo(foo):
          return foo * 2


- `4984 &lt;https://github.com/pytest-dev/pytest/issues/4984&gt;`_: Fixed an internal error crash with ``IndexError: list index out of range`` when
  collecting a module which starts with a decorated function, the decorator
  raises, and assertion rewriting is enabled.


- `7591 &lt;https://github.com/pytest-dev/pytest/issues/7591&gt;`_: pylint shouldn&#39;t complain anymore about unimplemented abstract methods when inheriting from :ref:`File &lt;non-python tests&gt;`.


- `7628 &lt;https://github.com/pytest-dev/pytest/issues/7628&gt;`_: Fixed test collection when a full path without a drive letter was passed to pytest on Windows (for example ``\projects\tests\test.py`` instead of ``c:\projects\tests\pytest.py``).


- `7638 &lt;https://github.com/pytest-dev/pytest/issues/7638&gt;`_: Fix handling of command-line options that appear as paths but trigger an OS-level syntax error on Windows, such as the options used internally by ``pytest-xdist``.


- `7742 &lt;https://github.com/pytest-dev/pytest/issues/7742&gt;`_: Fixed INTERNALERROR when accessing locals / globals with faulty ``exec``.



Improved Documentation
----------------------

- `1477 &lt;https://github.com/pytest-dev/pytest/issues/1477&gt;`_: Removed faq.rst and its reference in contents.rst.



Trivial/Internal Changes
------------------------

- `7536 &lt;https://github.com/pytest-dev/pytest/issues/7536&gt;`_: The internal ``junitxml`` plugin has rewritten to use ``xml.etree.ElementTree``.
  The order of attributes in XML elements might differ. Some unneeded escaping is
  no longer performed.


- `7587 &lt;https://github.com/pytest-dev/pytest/issues/7587&gt;`_: The dependency on the ``more-itertools`` package has been removed.


- `7631 &lt;https://github.com/pytest-dev/pytest/issues/7631&gt;`_: The result type of :meth:`capfd.readouterr() &lt;_pytest.capture.CaptureFixture.readouterr&gt;` (and similar) is no longer a namedtuple,
  but should behave like one in all respects. This was done for technical reasons.


- `7671 &lt;https://github.com/pytest-dev/pytest/issues/7671&gt;`_: When collecting tests, pytest finds test classes and functions by examining the
  attributes of python objects (modules, classes and instances). To speed up this
  process, pytest now ignores builtin attributes (like ``__class__``,
  ``__delattr__`` and ``__new__``) without consulting the :confval:`python_classes` and
  :confval:`python_functions` configuration options and without passing them to plugins
  using the :func:`pytest_pycollect_makeitem &lt;_pytest.hookspec.pytest_pycollect_makeitem&gt;` hook.
   ```
   
  
  
   ### 6.0.2
   ```
   =========================

Bug Fixes
---------

- `7148 &lt;https://github.com/pytest-dev/pytest/issues/7148&gt;`_: Fixed ``--log-cli`` potentially causing unrelated ``print`` output to be swallowed.


- `7672 &lt;https://github.com/pytest-dev/pytest/issues/7672&gt;`_: Fixed log-capturing level restored incorrectly if ``caplog.set_level`` is called more than once.


- `7686 &lt;https://github.com/pytest-dev/pytest/issues/7686&gt;`_: Fixed `NotSetType.token` being used as the parameter ID when the parametrization list is empty.
  Regressed in pytest 6.0.0.


- `7707 &lt;https://github.com/pytest-dev/pytest/issues/7707&gt;`_: Fix internal error when handling some exceptions that contain multiple lines or the style uses multiple lines (``--tb=line`` for example).
   ```
   
  
  
   ### 6.0.1
   ```
   =========================

Bug Fixes
---------

- `7394 &lt;https://github.com/pytest-dev/pytest/issues/7394&gt;`_: Passing an empty ``help`` value to ``Parser.add_option`` is now accepted instead of crashing when running ``pytest --help``.
  Passing ``None`` raises a more informative ``TypeError``.


- `7558 &lt;https://github.com/pytest-dev/pytest/issues/7558&gt;`_: Fix pylint ``not-callable`` lint on ``pytest.mark.parametrize()`` and the other builtin marks:
  ``skip``, ``skipif``, ``xfail``, ``usefixtures``, ``filterwarnings``.


- `7559 &lt;https://github.com/pytest-dev/pytest/issues/7559&gt;`_: Fix regression in plugins using ``TestReport.longreprtext`` (such as ``pytest-html``) when ``TestReport.longrepr`` is not a string.


- `7569 &lt;https://github.com/pytest-dev/pytest/issues/7569&gt;`_: Fix logging capture handler&#39;s level not reset on teardown after a call to ``caplog.set_level()``.
   ```
   
  
  
   ### 6.0.0
   ```
   =========================

(**Please see the full set of changes for this release also in the 6.0.0rc1 notes below**)

Breaking Changes
----------------

- `5584 &lt;https://github.com/pytest-dev/pytest/issues/5584&gt;`_: **PytestDeprecationWarning are now errors by default.**

  Following our plan to remove deprecated features with as little disruption as
  possible, all warnings of type ``PytestDeprecationWarning`` now generate errors
  instead of warning messages.

  **The affected features will be effectively removed in pytest 6.1**, so please consult the
  `Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`__
  section in the docs for directions on how to update existing code.

  In the pytest ``6.0.X`` series, it is possible to change the errors back into warnings as a
  stopgap measure by adding this to your ``pytest.ini`` file:

  .. code-block:: ini

      [pytest]
      filterwarnings =
          ignore::pytest.PytestDeprecationWarning

  But this will stop working when pytest ``6.1`` is released.

  **If you have concerns** about the removal of a specific feature, please add a
  comment to `5584 &lt;https://github.com/pytest-dev/pytest/issues/5584&gt;`__.


- `7472 &lt;https://github.com/pytest-dev/pytest/issues/7472&gt;`_: The ``exec_()`` and ``is_true()`` methods of ``_pytest._code.Frame`` have been removed.



Features
--------

- `7464 &lt;https://github.com/pytest-dev/pytest/issues/7464&gt;`_: Added support for :envvar:`NO_COLOR` and :envvar:`FORCE_COLOR` environment variables to control colored output.



Improvements
------------

- `7467 &lt;https://github.com/pytest-dev/pytest/issues/7467&gt;`_: ``--log-file`` CLI option and ``log_file`` ini marker now create subdirectories if needed.


- `7489 &lt;https://github.com/pytest-dev/pytest/issues/7489&gt;`_: The :func:`pytest.raises` function has a clearer error message when ``match`` equals the obtained string but is not a regex match. In this case it is suggested to escape the regex.



Bug Fixes
---------

- `7392 &lt;https://github.com/pytest-dev/pytest/issues/7392&gt;`_: Fix the reported location of tests skipped with ``pytest.mark.skip`` when ``--runxfail`` is used.


- `7491 &lt;https://github.com/pytest-dev/pytest/issues/7491&gt;`_: :fixture:`tmpdir` and :fixture:`tmp_path` no longer raise an error if the lock to check for
  stale temporary directories is not accessible.


- `7517 &lt;https://github.com/pytest-dev/pytest/issues/7517&gt;`_: Preserve line endings when captured via ``capfd``.


- `7534 &lt;https://github.com/pytest-dev/pytest/issues/7534&gt;`_: Restored the previous formatting of ``TracebackEntry.__str__`` which was changed by accident.



Improved Documentation
----------------------

- `7422 &lt;https://github.com/pytest-dev/pytest/issues/7422&gt;`_: Clarified when the ``usefixtures`` mark can apply fixtures to test.


- `7441 &lt;https://github.com/pytest-dev/pytest/issues/7441&gt;`_: Add a note about ``-q`` option used in getting started guide.



Trivial/Internal Changes
------------------------

- `7389 &lt;https://github.com/pytest-dev/pytest/issues/7389&gt;`_: Fixture scope ``package`` is no longer considered experimental.
   ```
   
  
  
   ### 6.0.0rc1
   ```
   ============================

Breaking Changes
----------------

- `1316 &lt;https://github.com/pytest-dev/pytest/issues/1316&gt;`_: ``TestReport.longrepr`` is now always an instance of ``ReprExceptionInfo``. Previously it was a ``str`` when a test failed with ``pytest.fail(..., pytrace=False)``.


- `5965 &lt;https://github.com/pytest-dev/pytest/issues/5965&gt;`_: symlinks are no longer resolved during collection and matching `conftest.py` files with test file paths.

  Resolving symlinks for the current directory and during collection was introduced as a bugfix in 3.9.0, but it actually is a new feature which had unfortunate consequences in Windows and surprising results in other platforms.

  The team decided to step back on resolving symlinks at all, planning to review this in the future with a more solid solution (see discussion in
  `6523 &lt;https://github.com/pytest-dev/pytest/pull/6523&gt;`__ for details).

  This might break test suites which made use of this feature; the fix is to create a symlink
  for the entire test tree, and not only to partial files/tress as it was possible previously.


- `6505 &lt;https://github.com/pytest-dev/pytest/issues/6505&gt;`_: ``Testdir.run().parseoutcomes()`` now always returns the parsed nouns in plural form.

  Originally ``parseoutcomes()`` would always returns the nouns in plural form, but a change
  meant to improve the terminal summary by using singular form single items (``1 warning`` or ``1 error``)
  caused an unintended regression by changing the keys returned by ``parseoutcomes()``.

  Now the API guarantees to always return the plural form, so calls like this:

  .. code-block:: python

      result = testdir.runpytest()
      result.assert_outcomes(error=1)

  Need to be changed to:


  .. code-block:: python

      result = testdir.runpytest()
      result.assert_outcomes(errors=1)


- `6903 &lt;https://github.com/pytest-dev/pytest/issues/6903&gt;`_: The ``os.dup()`` function is now assumed to exist. We are not aware of any
  supported Python 3 implementations which do not provide it.


- `7040 &lt;https://github.com/pytest-dev/pytest/issues/7040&gt;`_: ``-k`` no longer matches against the names of the directories outside the test session root.

  Also, ``pytest.Package.name`` is now just the name of the directory containing the package&#39;s
  ``__init__.py`` file, instead of the full path. This is consistent with how the other nodes
  are named, and also one of the reasons why ``-k`` would match against any directory containing
  the test suite.


- `7122 &lt;https://github.com/pytest-dev/pytest/issues/7122&gt;`_: Expressions given to the ``-m`` and ``-k`` options are no longer evaluated using Python&#39;s :func:`eval`.
  The format supports ``or``, ``and``, ``not``, parenthesis and general identifiers to match against.
  Python constants, keywords or other operators are no longer evaluated differently.


- `7135 &lt;https://github.com/pytest-dev/pytest/issues/7135&gt;`_: Pytest now uses its own ``TerminalWriter`` class instead of using the one from the ``py`` library.
  Plugins generally access this class through ``TerminalReporter.writer``, ``TerminalReporter.write()``
  (and similar methods), or ``_pytest.config.create_terminal_writer()``.

  The following breaking changes were made:

  - Output (``write()`` method and others) no longer flush implicitly; the flushing behavior
    of the underlying file is respected. To flush explicitly (for example, if you
    want output to be shown before an end-of-line is printed), use ``write(flush=True)`` or
    ``terminal_writer.flush()``.
  - Explicit Windows console support was removed, delegated to the colorama library.
  - Support for writing ``bytes`` was removed.
  - The ``reline`` method and ``chars_on_current_line`` property were removed.
  - The ``stringio`` and ``encoding`` arguments was removed.
  - Support for passing a callable instead of a file was removed.


- `7224 &lt;https://github.com/pytest-dev/pytest/issues/7224&gt;`_: The `item.catch_log_handler` and `item.catch_log_handlers` attributes, set by the
  logging plugin and never meant to be public, are no longer available.

  The deprecated ``--no-print-logs`` option and ``log_print`` ini option are removed. Use ``--show-capture`` instead.


- `7226 &lt;https://github.com/pytest-dev/pytest/issues/7226&gt;`_: Removed the unused ``args`` parameter from ``pytest.Function.__init__``.


- `7418 &lt;https://github.com/pytest-dev/pytest/issues/7418&gt;`_: Removed the `pytest_doctest_prepare_content` hook specification. This hook
  hasn&#39;t been triggered by pytest for at least 10 years.


- `7438 &lt;https://github.com/pytest-dev/pytest/issues/7438&gt;`_: Some changes were made to the internal ``_pytest._code.source``, listed here
  for the benefit of plugin authors who may be using it:

  - The ``deindent`` argument to ``Source()`` has been removed, now it is always true.
  - Support for zero or multiple arguments to ``Source()`` has been removed.
  - Support for comparing ``Source`` with an ``str`` has been removed.
  - The methods ``Source.isparseable()`` and ``Source.putaround()`` have been removed.
  - The method ``Source.compile()`` and function ``_pytest._code.compile()`` have
    been removed; use plain ``compile()`` instead.
  - The function ``_pytest._code.source.getsource()`` has been removed; use
    ``Source()`` directly instead.



Deprecations
------------

- `7210 &lt;https://github.com/pytest-dev/pytest/issues/7210&gt;`_: The special ``-k &#39;-expr&#39;`` syntax to ``-k`` is deprecated. Use ``-k &#39;not expr&#39;``
  instead.

  The special ``-k &#39;expr:&#39;`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.

- `4049 &lt;https://github.com/pytest-dev/pytest/issues/4049&gt;`_: ``pytest_warning_captured`` is deprecated in favor of the ``pytest_warning_recorded`` hook.


Features
--------

- `1556 &lt;https://github.com/pytest-dev/pytest/issues/1556&gt;`_: pytest now supports ``pyproject.toml`` files for configuration.

  The configuration options is similar to the one available in other formats, but must be defined
  in a ``[tool.pytest.ini_options]`` table to be picked up by pytest:

  .. code-block:: toml

       pyproject.toml
      [tool.pytest.ini_options]
      minversion = &quot;6.0&quot;
      addopts = &quot;-ra -q&quot;
      testpaths = [
          &quot;tests&quot;,
          &quot;integration&quot;,
      ]

  More information can be found `in the docs &lt;https://docs.pytest.org/en/stable/customize.html#configuration-file-formats&gt;`__.


- `3342 &lt;https://github.com/pytest-dev/pytest/issues/3342&gt;`_: pytest now includes inline type annotations and exposes them to user programs.
  Most of the user-facing API is covered, as well as internal code.

  If you are running a type checker such as mypy on your tests, you may start
  noticing type errors indicating incorrect usage. If you run into an error that
  you believe to be incorrect, please let us know in an issue.

  The types were developed against mypy version 0.780. Versions before 0.750
  are known not to work. We recommend using the latest version. Other type
  checkers may work as well, but they are not officially verified to work by
  pytest yet.


- `4049 &lt;https://github.com/pytest-dev/pytest/issues/4049&gt;`_: Introduced a new hook named `pytest_warning_recorded` to convey information about warnings captured by the internal `pytest` warnings plugin.

  This hook is meant to replace `pytest_warning_captured`, which is deprecated and will be removed in a future release.


- `6471 &lt;https://github.com/pytest-dev/pytest/issues/6471&gt;`_: New command-line flags:

  * `--no-header`: disables the initial header, including platform, version, and plugins.
  * `--no-summary`: disables the final test summary, including warnings.


- `6856 &lt;https://github.com/pytest-dev/pytest/issues/6856&gt;`_: A warning is now shown when an unknown key is read from a config INI file.

  The `--strict-config` flag has been added to treat these warnings as errors.


- `6906 &lt;https://github.com/pytest-dev/pytest/issues/6906&gt;`_: Added `--code-highlight` command line option to enable/disable code highlighting in terminal output.


- `7245 &lt;https://github.com/pytest-dev/pytest/issues/7245&gt;`_: New ``--import-mode=importlib`` option that uses `importlib &lt;https://docs.python.org/3/library/importlib.html&gt;`__ to import test modules.

  Traditionally pytest used ``__import__`` while changing ``sys.path`` to import test modules (which
  also changes ``sys.modules`` as a side-effect), which works but has a number of drawbacks, like requiring test modules
  that don&#39;t live in packages to have unique names (as they need to reside under a unique name in ``sys.modules``).

  ``--import-mode=importlib`` uses more fine grained import mechanisms from ``importlib`` which don&#39;t
  require pytest to change ``sys.path`` or ``sys.modules`` at all, eliminating much of the drawbacks
  of the previous mode.

  We intend to make ``--import-mode=importlib`` the default in future versions, so users are encouraged
  to try the new mode and provide feedback (both positive or negative) in issue `7245 &lt;https://github.com/pytest-dev/pytest/issues/7245&gt;`__.

  You can read more about this option in `the documentation &lt;https://docs.pytest.org/en/latest/pythonpath.html#import-modes&gt;`__.


- `7305 &lt;https://github.com/pytest-dev/pytest/issues/7305&gt;`_: New ``required_plugins`` configuration option allows the user to specify a list of plugins, including version information, that are required for pytest to run. An error is raised if any required plugins are not found when running pytest.


Improvements
------------

- `4375 &lt;https://github.com/pytest-dev/pytest/issues/4375&gt;`_: The ``pytest`` command now suppresses the ``BrokenPipeError`` error message that
  is printed to stderr when the output of ``pytest`` is piped and and the pipe is
  closed by the piped-to program (common examples are ``less`` and ``head``).


- `4391 &lt;https://github.com/pytest-dev/pytest/issues/4391&gt;`_: Improved precision of test durations measurement. ``CallInfo`` items now have a new ``&lt;CallInfo&gt;.duration`` attribute, created using ``time.perf_counter()``. This attribute is used to fill the ``&lt;TestReport&gt;.duration`` attribute, which is more accurate than the previous ``&lt;CallInfo&gt;.stop - &lt;CallInfo&gt;.start`` (as these are based on ``time.time()``).


- `4675 &lt;https://github.com/pytest-dev/pytest/issues/4675&gt;`_: Rich comparison for dataclasses and `attrs`-classes is now recursive.


- `6285 &lt;https://github.com/pytest-dev/pytest/issues/6285&gt;`_: Exposed the `pytest.FixtureLookupError` exception which is raised by `request.getfixturevalue()`
  (where `request` is a `FixtureRequest` fixture) when a fixture with the given name cannot be returned.


- `6433 &lt;https://github.com/pytest-dev/pytest/issues/6433&gt;`_: If an error is encountered while formatting the message in a logging call, for
  example ``logging.warning(&quot;oh no!: %s: %s&quot;, &quot;first&quot;)`` (a second argument is
  missing), pytest now propagates the error, likely causing the test to fail.

  Previously, such a mistake would cause an error to be printed to stderr, which
  is not displayed by default for passing tests. This change makes the mistake
  visible during testing.

  You may supress this behavior temporarily or permanently by setting
  ``logging.raiseExceptions = False``.


- `6817 &lt;https://github.com/pytest-dev/pytest/issues/6817&gt;`_: Explicit new-lines in help texts of command-line options are preserved, allowing plugins better control
  of the help displayed to users.


- `6940 &lt;https://github.com/pytest-dev/pytest/issues/6940&gt;`_: When using the ``--duration`` option, the terminal message output is now more precise about the number and duration of hidden items.


- `6991 &lt;https://github.com/pytest-dev/pytest/issues/6991&gt;`_: Collected files are displayed after any reports from hooks, e.g. the status from ``--lf``.


- `7091 &lt;https://github.com/pytest-dev/pytest/issues/7091&gt;`_: When ``fd`` capturing is used, through ``--capture=fd`` or the ``capfd`` and
  ``capfdbinary`` fixtures, and the file descriptor (0, 1, 2) cannot be
  duplicated, FD capturing is still performed. Previously, direct writes to the
  file descriptors would fail or be lost in this case.


- `7119 &lt;https://github.com/pytest-dev/pytest/issues/7119&gt;`_: Exit with an error if the ``--basetemp`` argument is empty, is the current working directory or is one of the parent directories.
  This is done to protect against accidental data loss, as any directory passed to this argument is cleared.


- `7128 &lt;https://github.com/pytest-dev/pytest/issues/7128&gt;`_: `pytest --version` now displays just the pytest version, while `pytest --version --version` displays more verbose information including plugins. This is more consistent with how other tools show `--version`.


- `7133 &lt;https://github.com/pytest-dev/pytest/issues/7133&gt;`_: :meth:`caplog.set_level() &lt;_pytest.logging.LogCaptureFixture.set_level&gt;` will now override any :confval:`log_level` set via the CLI or configuration file.


- `7159 &lt;https://github.com/pytest-dev/pytest/issues/7159&gt;`_: :meth:`caplog.set_level() &lt;_pytest.logging.LogCaptureFixture.set_level&gt;` and :meth:`caplog.at_level() &lt;_pytest.logging.LogCaptureFixture.at_level&gt;` no longer affect
  the level of logs that are shown in the *Captured log report* report section.


- `7348 &lt;https://github.com/pytest-dev/pytest/issues/7348&gt;`_: Improve recursive diff report for comparison asserts on dataclasses / attrs.


- `7385 &lt;https://github.com/pytest-dev/pytest/issues/7385&gt;`_: ``--junitxml`` now includes the exception cause in the ``message`` XML attribute for failures during setup and teardown.

  Previously:

  .. code-block:: xml

      &lt;error message=&quot;test setup failure&quot;&gt;

  Now:

  .. code-block:: xml

      &lt;error message=&quot;failed on setup with &amp;quot;ValueError: Some error during setup&amp;quot;&quot;&gt;



Bug Fixes
---------

- `1120 &lt;https://github.com/pytest-dev/pytest/issues/1120&gt;`_: Fix issue where directories from :fixture:`tmpdir` are not removed properly when multiple instances of pytest are running in parallel.


- `4583 &lt;https://github.com/pytest-dev/pytest/issues/4583&gt;`_: Prevent crashing and provide a user-friendly error when a marker expression (`-m`) invoking of :func:`eval` raises any exception.


- `4677 &lt;https://github.com/pytest-dev/pytest/issues/4677&gt;`_: The path shown in the summary report for SKIPPED tests is now always relative. Previously it was sometimes absolute.


- `5456 &lt;https://github.com/pytest-dev/pytest/issues/5456&gt;`_: Fix a possible race condition when trying to remove lock files used to control access to folders
  created by :fixture:`tmp_path` and :fixture:`tmpdir`.


- `6240 &lt;https://github.com/pytest-dev/pytest/issues/6240&gt;`_: Fixes an issue where logging during collection step caused duplication of log
  messages to stderr.


- `6428 &lt;https://github.com/pytest-dev/pytest/issues/6428&gt;`_: Paths appearing in error messages are now correct in case the current working directory has
  changed since the start of the session.


- `6755 &lt;https://github.com/pytest-dev/pytest/issues/6755&gt;`_: Support deleting paths longer than 260 characters on windows created inside :fixture:`tmpdir`.


- `6871 &lt;https://github.com/pytest-dev/pytest/issues/6871&gt;`_: Fix crash with captured output when using :fixture:`capsysbinary`.


- `6909 &lt;https://github.com/pytest-dev/pytest/issues/6909&gt;`_: Revert the change introduced by `#6330 &lt;https://github.com/pytest-dev/pytest/pull/6330&gt;`_, which required all arguments to ``pytest.mark.parametrize`` to be explicitly defined in the function signature.

  The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.


- `6910 &lt;https://github.com/pytest-dev/pytest/issues/6910&gt;`_: Fix crash when plugins return an unknown stats while using the ``--reportlog`` option.


- `6924 &lt;https://github.com/pytest-dev/pytest/issues/6924&gt;`_: Ensure a ``unittest.IsolatedAsyncioTestCase`` is actually awaited.


- `6925 &lt;https://github.com/pytest-dev/pytest/issues/6925&gt;`_: Fix `TerminalRepr` instances to be hashable again.


- `6947 &lt;https://github.com/pytest-dev/pytest/issues/6947&gt;`_: Fix regression where functions registered with :meth:`unittest.TestCase.addCleanup` were not being called on test failures.


- `6951 &lt;https://github.com/pytest-dev/pytest/issues/6951&gt;`_: Allow users to still set the deprecated ``TerminalReporter.writer`` attribute.


- `6956 &lt;https://github.com/pytest-dev/pytest/issues/6956&gt;`_: Prevent pytest from printing `ConftestImportFailure` traceback to stdout.


- `6991 &lt;https://github.com/pytest-dev/pytest/issues/6991&gt;`_: Fix regressions with `--lf` filtering too much since pytest 5.4.


- `6992 &lt;https://github.com/pytest-dev/pytest/issues/6992&gt;`_: Revert &quot;tmpdir: clean up indirection via config for factories&quot; `#6767 &lt;https://github.com/pytest-dev/pytest/issues/6767&gt;`_ as it breaks pytest-xdist.


- `7061 &lt;https://github.com/pytest-dev/pytest/issues/7061&gt;`_: When a yielding fixture fails to yield a value, report a test setup error instead of crashing.


- `7076 &lt;https://github.com/pytest-dev/pytest/issues/7076&gt;`_: The path of file skipped by ``pytest.mark.skip`` in the SKIPPED report is now relative to invocation directory. Previously it was relative to root directory.


- `7110 &lt;https://github.com/pytest-dev/pytest/issues/7110&gt;`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.


- `7126 &lt;https://github.com/pytest-dev/pytest/issues/7126&gt;`_: ``--setup-show`` now doesn&#39;t raise an error when a bytes value is used as a ``parametrize``
  parameter when Python is called with the ``-bb`` flag.


- `7143 &lt;https://github.com/pytest-dev/pytest/issues/7143&gt;`_: Fix :meth:`pytest.File.from_parent` so it forwards extra keyword arguments to the constructor.


- `7145 &lt;https://github.com/pytest-dev/pytest/issues/7145&gt;`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.


- `7150 &lt;https://github.com/pytest-dev/pytest/issues/7150&gt;`_: Prevent hiding the underlying exception when ``ConfTestImportFailure`` is raised.


- `7180 &lt;https://github.com/pytest-dev/pytest/issues/7180&gt;`_: Fix ``_is_setup_py`` for files encoded differently than locale.


- `7215 &lt;https://github.com/pytest-dev/pytest/issues/7215&gt;`_: Fix regression where running with ``--pdb`` would call :meth:`unittest.TestCase.tearDown` for skipped tests.


- `7253 &lt;https://github.com/pytest-dev/pytest/issues/7253&gt;`_: When using ``pytest.fixture`` on a function directly, as in ``pytest.fixture(func)``,
  if the ``autouse`` or ``params`` arguments are also passed, the function is no longer
  ignored, but is marked as a fixture.


- `7360 &lt;https://github.com/pytest-dev/pytest/issues/7360&gt;`_: Fix possibly incorrect evaluation of string expressions passed to ``pytest.mark.skipif`` and ``pytest.mark.xfail``,
  in rare circumstances where the exact same string is used but refers to different global values.


- `7383 &lt;https://github.com/pytest-dev/pytest/issues/7383&gt;`_: Fixed exception causes all over the codebase, i.e. use `raise new_exception from old_exception` when wrapping an exception.



Improved Documentation
----------------------

- `7202 &lt;https://github.com/pytest-dev/pytest/issues/7202&gt;`_: The development guide now links to the contributing section of the docs and `RELEASING.rst` on GitHub.


- `7233 &lt;https://github.com/pytest-dev/pytest/issues/7233&gt;`_: Add a note about ``--strict`` and ``--strict-markers`` and the preference for the latter one.


- `7345 &lt;https://github.com/pytest-dev/pytest/issues/7345&gt;`_: Explain indirect parametrization and markers for fixtures.



Trivial/Internal Changes
------------------------

- `7035 &lt;https://github.com/pytest-dev/pytest/issues/7035&gt;`_: The ``originalname`` attribute of ``_pytest.python.Function`` now defaults to ``name`` if not
  provided explicitly, and is always set.


- `7264 &lt;https://github.com/pytest-dev/pytest/issues/7264&gt;`_: The dependency on the ``wcwidth`` package has been removed.


- `7291 &lt;https://github.com/pytest-dev/pytest/issues/7291&gt;`_: Replaced ``py.iniconfig`` with `iniconfig &lt;https://pypi.org/project/iniconfig/&gt;`__.


- `7295 &lt;https://github.com/pytest-dev/pytest/issues/7295&gt;`_: ``src/_pytest/config/__init__.py`` now uses the ``warnings`` module to report warnings instead of ``sys.stderr.write``.


- `7356 &lt;https://github.com/pytest-dev/pytest/issues/7356&gt;`_: Remove last internal uses of deprecated *slave* term from old ``pytest-xdist``.


- `7357 &lt;https://github.com/pytest-dev/pytest/issues/7357&gt;`_: ``py``&gt;=1.8.2 is now required.
   ```
   
  
  
   ### 5.4.3
   ```
   =========================

Bug Fixes
---------

- `6428 &lt;https://github.com/pytest-dev/pytest/issues/6428&gt;`_: Paths appearing in error messages are now correct in case the current working directory has
  changed since the start of the session.


- `6755 &lt;https://github.com/pytest-dev/pytest/issues/6755&gt;`_: Support deleting paths longer than 260 characters on windows created inside tmpdir.


- `6956 &lt;https://github.com/pytest-dev/pytest/issues/6956&gt;`_: Prevent pytest from printing ConftestImportFailure traceback to stdout.


- `7150 &lt;https://github.com/pytest-dev/pytest/issues/7150&gt;`_: Prevent hiding the underlying exception when ``ConfTestImportFailure`` is raised.


- `7215 &lt;https://github.com/pytest-dev/pytest/issues/7215&gt;`_: Fix regression where running with ``--pdb`` would call the ``tearDown`` methods of ``unittest.TestCase``
  subclasses for skipped tests.
   ```
   
  
  
   ### 5.4.2
   ```
   =========================

Bug Fixes
---------

- `6871 &lt;https://github.com/pytest-dev/pytest/issues/6871&gt;`_: Fix crash with captured output when using the :fixture:`capsysbinary fixture &lt;capsysbinary&gt;`.


- `6924 &lt;https://github.com/pytest-dev/pytest/issues/6924&gt;`_: Ensure a ``unittest.IsolatedAsyncioTestCase`` is actually awaited.


- `6925 &lt;https://github.com/pytest-dev/pytest/issues/6925&gt;`_: Fix TerminalRepr instances to be hashable again.


- `6947 &lt;https://github.com/pytest-dev/pytest/issues/6947&gt;`_: Fix regression where functions registered with ``TestCase.addCleanup`` were not being called on test failures.


- `6951 &lt;https://github.com/pytest-dev/pytest/issues/6951&gt;`_: Allow users to still set the deprecated ``TerminalReporter.writer`` attribute.


- `6992 &lt;https://github.com/pytest-dev/pytest/issues/6992&gt;`_: Revert &quot;tmpdir: clean up indirection via config for factories&quot; #6767 as it breaks pytest-xdist.


- `7110 &lt;https://github.com/pytest-dev/pytest/issues/7110&gt;`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.


- `7143 &lt;https://github.com/pytest-dev/pytest/issues/7143&gt;`_: Fix ``File.from_constructor`` so it forwards extra keyword arguments to the constructor.


- `7145 &lt;https://github.com/pytest-dev/pytest/issues/7145&gt;`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.


- `7180 &lt;https://github.com/pytest-dev/pytest/issues/7180&gt;`_: Fix ``_is_setup_py`` for files encoded differently than locale.
   ```
   
  
  
   ### 5.4.1
   ```
   =========================

Bug Fixes
---------

- `6909 &lt;https://github.com/pytest-dev/pytest/issues/6909&gt;`_: Revert the change introduced by `#6330 &lt;https://github.com/pytest-dev/pytest/pull/6330&gt;`_, which required all arguments to ``pytest.mark.parametrize`` to be explicitly defined in the function signature.

  The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.


- `6910 &lt;https://github.com/pytest-dev/pytest/issues/6910&gt;`_: Fix crash when plugins return an unknown stats while using the ``--reportlog`` option.
   ```
   
  
  
   ### 5.4.0
   ```
   =========================

Breaking Changes
----------------

- `6316 &lt;https://github.com/pytest-dev/pytest/issues/6316&gt;`_: Matching of ``-k EXPRESSION`` to test names is now case-insensitive.


- `6443 &lt;https://github.com/pytest-dev/pytest/issues/6443&gt;`_: Plugins specified with ``-p`` are now loaded after internal plugins, which results in their hooks being called *before* the internal ones.

  This makes the ``-p`` behavior consistent with ``PYTEST_PLUGINS``.


- `6637 &lt;https://github.com/pytest-dev/pytest/issues/6637&gt;`_: Removed the long-deprecated ``pytest_itemstart`` hook.

  This hook has been marked as deprecated and not been even called by pytest for over 10 years now.


- `6673 &lt;https://github.com/pytest-dev/pytest/issues/6673&gt;`_: Reversed / fix meaning of &quot;+/-&quot; in error diffs.  &quot;-&quot; means that sth. expected is missing in the result and &quot;+&quot; means that there are unexpected extras in the result.


- `6737 &lt;https://github.com/pytest-dev/pytest/issues/6737&gt;`_: The ``cached_result`` attribute of ``FixtureDef`` is now set to ``None`` when
  the result is unavailable, instead of being deleted.

  If your plugin performs checks like ``hasattr(fixturedef, &#39;cached_result&#39;)``,
  for example in a ``pytest_fixture_post_finalizer`` hook implementation, replace
  it with ``fixturedef.cached_result is not None``. If you ``del`` the attribute,
  set it to ``None`` instead.



Deprecations
------------

- `3238 &lt;https://github.com/pytest-dev/pytest/issues/3238&gt;`_: Option ``--no-print-logs`` is deprecated and meant to be removed in a future release. If you use ``--no-print-logs``, please try out ``--show-capture`` and
  provide feedback.

  ``--show-capture`` command-line option was added in ``pytest 3.5.0`` and allows to specify how to
  display captured output when tests fail: ``no``, ``stdout``, ``stderr``, ``log`` or ``all`` (the default).


- `571 &lt;https://github.com/pytest-dev/pytest/issues/571&gt;`_: Deprecate the unused/broken `pytest_collect_directory` hook.
  It was misaligned since the removal of the ``Directory`` collector in 2010
  and incorrect/unusable as soon as collection was split from test execution.


- `5975 &lt;https://github.com/pytest-dev/pytest/issues/5975&gt;`_: Deprecate using direct constructors for ``Nodes``.

  Instead they are now constructed via ``Node.from_parent``.

  This transitional mechanism enables us to untangle the very intensely
  entangled ``Node`` relationships by enforcing more controlled creation/configuration patterns.

  As part of this change, session/config are already disallowed parameters and as we work on the details we might need disallow a few more as well.

  Subclasses are expected to use `super().from_parent` if they intend to expand the creation of `Nodes`.


- `6779 &lt;https://github.com/pytest-dev/pytest/issues/6779&gt;`_: The ``TerminalReporter.writer`` attribute has been deprecated and should no longer be used. This
  was inadvertently exposed as part of the public API of that plugin and ties it too much
  with ``py.io.TerminalWriter``.



Features
--------

- `4597 &lt;https://github.com/pytest-dev/pytest/issues/4597&gt;`_: New :ref:`--capture=tee-sys &lt;capture-method&gt;` option to allow both live printing and capturing of test output.


- `5712 &lt;https://github.com/pytest-dev/pytest/issues/5712&gt;`_: Now all arguments to ``pytest.mark.parametrize`` need to be explicitly declared in the function signature or via ``indirect``.
  Previously it was possible to omit an argument if a fixture with the same name existed, which was just an accident of implementation and was not meant to be a part of the API.


- `6454 &lt;https://github.com/pytest-dev/pytest/issues/6454&gt;`_: Changed default for `-r` to `fE`, which displays failures and errors in the :ref:`short test summary &lt;pytest.detailed_failed_tests_usage&gt;`.  `-rN` can be used to disable it (the old behavior).


- `6469 &lt;https://github.com/pytest-dev/pytest/issues/6469&gt;`_: New options have been added to the :confval:`junit_logging` option: ``log``, ``out-err``, and ``all``.


- `6834 &lt;https://github.com/pytest-dev/pytest/issues/6834&gt;`_: Excess warning summaries are now collapsed per file to ensure readable display of warning summaries.



Improvements
------------

- `1857 &lt;https://github.com/pytest-dev/pytest/issues/1857&gt;`_: ``pytest.mark.parametrize`` accepts integers for ``ids`` again, converting it to strings.


- `449 &lt;https://github.com/pytest-dev/pytest/issues/449&gt;`_: Use &quot;yellow&quot; main color with any XPASSED tests.


- `4639 &lt;https://github.com/pytest-dev/pytest/issues/4639&gt;`_: Revert &quot;A warning is now issued when assertions are made for ``None``&quot;.

  The warning proved to be less useful than initially expected and had quite a
  few false positive cases.


- `5686 &lt;https://github.com/pytest-dev/pytest/issues/5686&gt;`_: ``tmpdir_factory.mktemp`` now fails when given absolute and non-normalized paths.


- `5984 &lt;https://github.com/pytest-dev/pytest/issues/5984&gt;`_: The ``pytest_warning_captured`` hook now receives a ``location`` parameter with the code location that generated the warning.


- `6213 &lt;https://github.com/pytest-dev/pytest/issues/6213&gt;`_: pytester: the ``testdir`` fixture respects environment settings from the ``monkeypatch`` fixture for inner runs.


- `6247 &lt;https://github.com/pytest-dev/pytest/issues/6247&gt;`_: ``--fulltrace`` is honored with collection errors.


- `6384 &lt;https://github.com/pytest-dev/pytest/issues/6384&gt;`_: Make `--showlocals` work also with `--tb=short`.


- `6653 &lt;https://github.com/pytest-dev/pytest/issues/6653&gt;`_: Add support for matching lines consecutively with :attr:`LineMatcher &lt;_pytest.pytester.LineMatcher&gt;`&#39;s :func:`~_pytest.pytester.LineMatcher.fnmatch_lines` and :func:`~_pytest.pytester.LineMatcher.re_match_lines`.


- `6658 &lt;https://github.com/pytest-dev/pytest/issues/6658&gt;`_: Code is now highlighted in tracebacks when ``pygments`` is installed.

  Users are encouraged to install ``pygments`` into their environment and provide feedback, because
  the plan is to make ``pygments`` a regular dependency in the future.


- `6795 &lt;https://github.com/pytest-dev/pytest/issues/6795&gt;`_: Import usage error message with invalid `-o` option.


- `759 &lt;https://github.com/pytest-dev/pytest/issues/759&gt;`_: ``pytest.mark.parametrize`` supports iterators and generators for ``ids``.



Bug Fixes
---------

- `310 &lt;https://github.com/pytest-dev/pytest/issues/310&gt;`_: Add support for calling `pytest.xfail()` and `pytest.importorskip()` with doctests.


- `3823 &lt;https://github.com/pytest-dev/pytest/issues/3823&gt;`_: ``--trace`` now works with unittests.


- `4445 &lt;https://github.com/pytest-dev/pytest/issues/4445&gt;`_: Fixed some warning reports produced by pytest to point to the correct location of the warning in the user&#39;s code.


- `5301 &lt;https://github.com/pytest-dev/pytest/issues/5301&gt;`_: Fix ``--last-failed`` to collect new tests from files with known failures.


- `5928 &lt;https://github.com/pytest-dev/pytest/issues/5928&gt;`_: Report ``PytestUnknownMarkWarning`` at the level of the user&#39;s code, not ``pytest``&#39;s.


- `5991 &lt;https://github.com/pytest-dev/pytest/issues/5991&gt;`_: Fix interaction with ``--pdb`` and unittests: do not use unittest&#39;s ``TestCase.debug()``.


- `6334 &lt;https://github.com/pytest-dev/pytest/issues/6334&gt;`_: Fix summary entries appearing twice when ``f/F`` and ``s/S`` report chars were used at the same time in the ``-r`` command-line option (for example ``-rFf``).

  The upper case variants were never documented and the preferred form should be the lower case.


- `6409 &lt;https://github.com/pytest-dev/pytest/issues/6409&gt;`_: Fallback to green (instead of yellow) for non-last items without previous passes with colored terminal progress indicator.


- `6454 &lt;https://github.com/pytest-dev/pytest/issues/6454&gt;`_: `--disable-warnings` is honored with `-ra` and `-rA`.


- `6497 &lt;https://github.com/pytest-dev/pytest/issues/6497&gt;`_: Fix bug in the comparison of request key with cached key in fixture.

  A construct ``if key == cached_key:`` can fail either because ``==`` is explicitly disallowed, or for, e.g., NumPy arrays, where the result of ``a == b`` cannot generally be converted to `bool`.
  The implemented fix replaces `==` with ``is``.


- `6557 &lt;https://github.com/pytest-dev/pytest/issues/6557&gt;`_: Make capture output streams ``.write()`` method return the same return value from original streams.


- `6566 &lt;https://github.com/pytest-dev/pytest/issues/6566&gt;`_: Fix ``EncodedFile.writelines`` to call the underlying buffer&#39;s ``writelines`` method.


- `6575 &lt;https://github.com/pytest-dev/pytest/issues/6575&gt;`_: Fix internal crash when ``faulthandler`` starts initialized
  (for example with ``PYTHONFAULTHANDLER=1`` environment variable set) and ``faulthandler_timeout`` defined
  in the configuration file.


- `6597 &lt;https://github.com/pytest-dev/pytest/issues/6597&gt;`_: Fix node ids which contain a parametrized empty-string variable.


- `6646 &lt;https://github.com/pytest-dev/pytest/issues/6646&gt;`_: Assertion rewriting hooks are (re)stored for the current item, which fixes them being still used after e.g. pytester&#39;s :func:`testdir.runpytest &lt;_pytest.pytester.Testdir.runpytest&gt;` etc.


- `6660 &lt;https://github.com/pytest-dev/pytest/issues/6660&gt;`_: :py:func:`pytest.exit` is handled when emitted from the :func:`pytest_sessionfinish &lt;_pytest.hookspec.pytest_sessionfinish&gt;` hook.  This includes quitting from a debugger.


- `6752 &lt;https://github.com/pytest-dev/pytest/issues/6752&gt;`_: When :py:func:`pytest.raises` is used as a function (as opposed to a context manager),
  a `match` keyword argument is now passed through to the tested function. Previously
  it was swallowed and ignored (regression in pytest 5.1.0).


- `6801 &lt;https://github.com/pytest-dev/pytest/issues/6801&gt;`_: Do not display empty lines inbetween traceback for unexpected exceptions with doctests.


- `6802 &lt;https://github.com/pytest-dev/pytest/issues/6802&gt;`_: The :fixture:`testdir fixture &lt;testdir&gt;` works within doctests now.



Improved Documentation
----------------------

- `6696 &lt;https://github.com/pytest-dev/pytest/issues/6696&gt;`_: Add list of fixtures to start of fixture chapter.


- `6742 &lt;https://github.com/pytest-dev/pytest/issues/6742&gt;`_: Expand first sentence on fixtures into a paragraph.



Trivial/Internal Changes
------------------------

- `6404 &lt;https://github.com/pytest-dev/pytest/issues/6404&gt;`_: Remove usage of ``parser`` module, deprecated in Python 3.9.
   ```
   
  
  
   ### 5.3.5
   ```
   =========================

Bug Fixes
---------

- `6517 &lt;https://github.com/pytest-dev/pytest/issues/6517&gt;`_: Fix regression in pytest 5.3.4 causing an INTERNALERROR due to a wrong assertion.
   ```
   
  
  
   ### 5.3.4
   ```
   =========================

Bug Fixes
---------

- `6496 &lt;https://github.com/pytest-dev/pytest/issues/6496&gt;`_: Revert `#6436 &lt;https://github.com/pytest-dev/pytest/issues/6436&gt;`__: unfortunately this change has caused a number of regressions in many suites,
  so the team decided to revert this change and make a new release while we continue to look for a solution.
   ```
   
  
  
   ### 5.3.3
   ```
   =========================

Bug Fixes
---------

- `2780 &lt;https://github.com/pytest-dev/pytest/issues/2780&gt;`_: Captured output during teardown is shown with ``-rP``.


- `5971 &lt;https://github.com/pytest-dev/pytest/issues/5971&gt;`_: Fix a ``pytest-xdist`` crash when dealing with exceptions raised in subprocesses created by the
  ``multiprocessing`` module.


- `6436 &lt;https://github.com/pytest-dev/pytest/issues/6436&gt;`_: :class:`FixtureDef &lt;_pytest.fixtures.FixtureDef&gt;` objects now properly register their finalizers with autouse and
  parameterized fixtures that execute before them in the fixture stack so they are torn
  down at the right times, and in the right order.


- `6532 &lt;https://github.com/pytest-dev/pytest/issues/6532&gt;`_: Fix parsing of outcomes containing multiple errors with ``testdir`` results (regression in 5.3.0).



Trivial/Internal Changes
------------------------

- `6350 &lt;https://github.com/pytest-dev/pytest/issues/6350&gt;`_: Optimized automatic renaming of test parameter IDs.
   ```
   
  
  
   ### 5.3.2
   ```
   =========================

Improvements
------------

- `4639 &lt;https://github.com/pytest-dev/pytest/issues/4639&gt;`_: Revert &quot;A warning is now issued when assertions are made for ``None``&quot;.

  The warning proved to be less useful than initially expected and had quite a
  few false positive cases.



Bug Fixes
---------

- `5430 &lt;https://github.com/pytest-dev/pytest/issues/5430&gt;`_: junitxml: Logs for failed test are now passed to junit report in case the test fails during call phase.


- `6290 &lt;https://github.com/pytest-dev/pytest/issues/6290&gt;`_: The supporting files in the ``.pytest_cache`` directory are kept with ``--cache-clear``, which only clears cached values now.


- `6301 &lt;https://github.com/pytest-dev/pytest/issues/6301&gt;`_: Fix assertion rewriting for egg-based distributions and ``editable`` installs (``pip install --editable``).
   ```
   
  
  
   ### 5.3.1
   ```
   =========================

Improvements
------------

- `6231 &lt;https://github.com/pytest-dev/pytest/issues/6231&gt;`_: Improve check for misspelling of :ref:`pytest.mark.parametrize ref`.


- `6257 &lt;https://github.com/pytest-dev/pytest/issues/6257&gt;`_: Handle :py:func:`pytest.exit` being used via :py:func:`~_pytest.hookspec.pytest_internalerror`, e.g. when quitting pdb from post mortem.



Bug Fixes
---------

- `5914 &lt;https://github.com/pytest-dev/pytest/issues/5914&gt;`_: pytester: fix :py:func:`~_pytest.pytester.LineMatcher.no_fnmatch_line` when used after positive matching.


- `6082 &lt;https://github.com/pytest-dev/pytest/issues/6082&gt;`_: Fix line detection for doctest samples inside :py:class:`python:property` docstrings, as a workaround to `bpo-17446 &lt;https://bugs.python.org/issue17446&gt;`__.


- `6254 &lt;https://github.com/pytest-dev/pytest/issues/6254&gt;`_: Fix compatibility with pytest-parallel (regression in pytest 5.3.0).


- `6255 &lt;https://github.com/pytest-dev/pytest/issues/6255&gt;`_: Clear the :py:data:`sys.last_traceback`, :py:data:`sys.last_type`
  and :py:data:`sys.last_value` attributes by deleting them instead
  of setting them to ``None``. This better matches the behaviour of
  the Python standar…
bors bot added a commit to aragilar/spaceplot that referenced this issue Aug 6, 2021
7: Pin sphinx_rtd_theme to latest version 0.5.2 r=aragilar a=pyup-bot


This PR pins [sphinx_rtd_theme](https://pypi.org/project/sphinx_rtd_theme) to the latest release **0.5.2**.



*The bot wasn't able to find a changelog for this release. [Got an idea?](https://github.com/pyupio/changelogs/issues/new)*

<details>
  <summary>Links</summary>
  
  - PyPI: https://pypi.org/project/sphinx-rtd-theme
  - Repo: https://github.com/readthedocs/sphinx_rtd_theme
</details>



8: Pin pytest to latest version 6.2.4 r=aragilar a=pyup-bot


This PR pins [pytest](https://pypi.org/project/pytest) to the latest release **6.2.4**.



<details>
  <summary>Changelog</summary>
  
  
   ### 6.2.4
   ```
   =========================

Bug Fixes
---------

- `8539 &lt;https://github.com/pytest-dev/pytest/issues/8539&gt;`_: Fixed assertion rewriting on Python 3.10.
   ```
   
  
  
   ### 6.2.3
   ```
   =========================

Bug Fixes
---------

- `8414 &lt;https://github.com/pytest-dev/pytest/issues/8414&gt;`_: pytest used to create directories under ``/tmp`` with world-readable
  permissions. This means that any user in the system was able to read
  information written by tests in temporary directories (such as those created by
  the ``tmp_path``/``tmpdir`` fixture). Now the directories are created with
  private permissions.

  pytest used to silenty use a pre-existing ``/tmp/pytest-of-&lt;username&gt;`` directory,
  even if owned by another user. This means another user could pre-create such a
  directory and gain control of another user&#39;s temporary directory. Now such a
  condition results in an error.
   ```
   
  
  
   ### 6.2.2
   ```
   =========================

Bug Fixes
---------

- `8152 &lt;https://github.com/pytest-dev/pytest/issues/8152&gt;`_: Fixed &quot;(&lt;Skipped instance&gt;)&quot; being shown as a skip reason in the verbose test summary line when the reason is empty.


- `8249 &lt;https://github.com/pytest-dev/pytest/issues/8249&gt;`_: Fix the ``faulthandler`` plugin for occasions when running with ``twisted.logger`` and using ``pytest --capture=no``.
   ```
   
  
  
   ### 6.2.1
   ```
   =========================

Bug Fixes
---------

- `7678 &lt;https://github.com/pytest-dev/pytest/issues/7678&gt;`_: Fixed bug where ``ImportPathMismatchError`` would be raised for files compiled in
  the host and loaded later from an UNC mounted path (Windows).


- `8132 &lt;https://github.com/pytest-dev/pytest/issues/8132&gt;`_: Fixed regression in ``approx``: in 6.2.0 ``approx`` no longer raises
  ``TypeError`` when dealing with non-numeric types, falling back to normal comparison.
  Before 6.2.0, array types like tf.DeviceArray fell through to the scalar case,
  and happened to compare correctly to a scalar if they had only one element.
  After 6.2.0, these types began failing, because they inherited neither from
  standard Python number hierarchy nor from ``numpy.ndarray``.

  ``approx`` now converts arguments to ``numpy.ndarray`` if they expose the array
  protocol and are not scalars. This treats array-like objects like numpy arrays,
  regardless of size.
   ```
   
  
  
   ### 6.2.0
   ```
   =========================

Breaking Changes
----------------

- `7808 &lt;https://github.com/pytest-dev/pytest/issues/7808&gt;`_: pytest now supports python3.6+ only.



Deprecations
------------

- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_: Directly constructing/calling the following classes/functions is now deprecated:

  - ``_pytest.cacheprovider.Cache``
  - ``_pytest.cacheprovider.Cache.for_config()``
  - ``_pytest.cacheprovider.Cache.clear_cache()``
  - ``_pytest.cacheprovider.Cache.cache_dir_from_config()``
  - ``_pytest.capture.CaptureFixture``
  - ``_pytest.fixtures.FixtureRequest``
  - ``_pytest.fixtures.SubRequest``
  - ``_pytest.logging.LogCaptureFixture``
  - ``_pytest.pytester.Pytester``
  - ``_pytest.pytester.Testdir``
  - ``_pytest.recwarn.WarningsRecorder``
  - ``_pytest.recwarn.WarningsChecker``
  - ``_pytest.tmpdir.TempPathFactory``
  - ``_pytest.tmpdir.TempdirFactory``

  These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.


- `7530 &lt;https://github.com/pytest-dev/pytest/issues/7530&gt;`_: The ``--strict`` command-line option has been deprecated, use ``--strict-markers`` instead.

  We have plans to maybe in the future to reintroduce ``--strict`` and make it an encompassing flag for all strictness
  related options (``--strict-markers`` and ``--strict-config`` at the moment, more might be introduced in the future).


- `7988 &lt;https://github.com/pytest-dev/pytest/issues/7988&gt;`_: The ``pytest.yield_fixture`` decorator/function is now deprecated. Use :func:`pytest.fixture` instead.

  ``yield_fixture`` has been an alias for ``fixture`` for a very long time, so can be search/replaced safely.



Features
--------

- `5299 &lt;https://github.com/pytest-dev/pytest/issues/5299&gt;`_: pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python&gt;=3.8.
  See :ref:`unraisable` for more information.


- `7425 &lt;https://github.com/pytest-dev/pytest/issues/7425&gt;`_: New :fixture:`pytester` fixture, which is identical to :fixture:`testdir` but its methods return :class:`pathlib.Path` when appropriate instead of ``py.path.local``.

  This is part of the movement to use :class:`pathlib.Path` objects internally, in order to remove the dependency to ``py`` in the future.

  Internally, the old :class:`Testdir &lt;_pytest.pytester.Testdir&gt;` is now a thin wrapper around :class:`Pytester &lt;_pytest.pytester.Pytester&gt;`, preserving the old interface.


- `7695 &lt;https://github.com/pytest-dev/pytest/issues/7695&gt;`_: A new hook was added, `pytest_markeval_namespace` which should return a dictionary.
  This dictionary will be used to augment the &quot;global&quot; variables available to evaluate skipif/xfail/xpass markers.

  Pseudo example

  ``conftest.py``:

  .. code-block:: python

     def pytest_markeval_namespace():
         return {&quot;color&quot;: &quot;red&quot;}

  ``test_func.py``:

  .. code-block:: python

     pytest.mark.skipif(&quot;color == &#39;blue&#39;&quot;, reason=&quot;Color is not red&quot;)
     def test_func():
         assert False


- `8006 &lt;https://github.com/pytest-dev/pytest/issues/8006&gt;`_: It is now possible to construct a :class:`~pytest.MonkeyPatch` object directly as ``pytest.MonkeyPatch()``,
  in cases when the :fixture:`monkeypatch` fixture cannot be used. Previously some users imported it
  from the private `_pytest.monkeypatch.MonkeyPatch` namespace.

  Additionally, :meth:`MonkeyPatch.context &lt;pytest.MonkeyPatch.context&gt;` is now a classmethod,
  and can be used as ``with MonkeyPatch.context() as mp: ...``. This is the recommended way to use
  ``MonkeyPatch`` directly, since unlike the ``monkeypatch`` fixture, an instance created directly
  is not ``undo()``-ed automatically.



Improvements
------------

- `1265 &lt;https://github.com/pytest-dev/pytest/issues/1265&gt;`_: Added an ``__str__`` implementation to the :class:`~pytest.pytester.LineMatcher` class which is returned from ``pytester.run_pytest().stdout`` and similar. It returns the entire output, like the existing ``str()`` method.


- `2044 &lt;https://github.com/pytest-dev/pytest/issues/2044&gt;`_: Verbose mode now shows the reason that a test was skipped in the test&#39;s terminal line after the &quot;SKIPPED&quot;, &quot;XFAIL&quot; or &quot;XPASS&quot;.


- `7469 &lt;https://github.com/pytest-dev/pytest/issues/7469&gt;`_ The types of builtin pytest fixtures are now exported so they may be used in type annotations of test functions.
  The newly-exported types are:

  - ``pytest.FixtureRequest`` for the :fixture:`request` fixture.
  - ``pytest.Cache`` for the :fixture:`cache` fixture.
  - ``pytest.CaptureFixture[str]`` for the :fixture:`capfd` and :fixture:`capsys` fixtures.
  - ``pytest.CaptureFixture[bytes]`` for the :fixture:`capfdbinary` and :fixture:`capsysbinary` fixtures.
  - ``pytest.LogCaptureFixture`` for the :fixture:`caplog` fixture.
  - ``pytest.Pytester`` for the :fixture:`pytester` fixture.
  - ``pytest.Testdir`` for the :fixture:`testdir` fixture.
  - ``pytest.TempdirFactory`` for the :fixture:`tmpdir_factory` fixture.
  - ``pytest.TempPathFactory`` for the :fixture:`tmp_path_factory` fixture.
  - ``pytest.MonkeyPatch`` for the :fixture:`monkeypatch` fixture.
  - ``pytest.WarningsRecorder`` for the :fixture:`recwarn` fixture.

  Constructing them is not supported (except for `MonkeyPatch`); they are only meant for use in type annotations.
  Doing so will emit a deprecation warning, and may become a hard-error in pytest 7.0.

  Subclassing them is also not supported. This is not currently enforced at runtime, but is detected by type-checkers such as mypy.


- `7527 &lt;https://github.com/pytest-dev/pytest/issues/7527&gt;`_: When a comparison between :func:`namedtuple &lt;collections.namedtuple&gt;` instances of the same type fails, pytest now shows the differing field names (possibly nested) instead of their indexes.


- `7615 &lt;https://github.com/pytest-dev/pytest/issues/7615&gt;`_: :meth:`Node.warn &lt;_pytest.nodes.Node.warn&gt;` now permits any subclass of :class:`Warning`, not just :class:`PytestWarning &lt;pytest.PytestWarning&gt;`.


- `7701 &lt;https://github.com/pytest-dev/pytest/issues/7701&gt;`_: Improved reporting when using ``--collected-only``. It will now show the number of collected tests in the summary stats.


- `7710 &lt;https://github.com/pytest-dev/pytest/issues/7710&gt;`_: Use strict equality comparison for non-numeric types in :func:`pytest.approx` instead of
  raising :class:`TypeError`.

  This was the undocumented behavior before 3.7, but is now officially a supported feature.


- `7938 &lt;https://github.com/pytest-dev/pytest/issues/7938&gt;`_: New ``--sw-skip`` argument which is a shorthand for ``--stepwise-skip``.


- `8023 &lt;https://github.com/pytest-dev/pytest/issues/8023&gt;`_: Added ``&#39;node_modules&#39;`` to default value for :confval:`norecursedirs`.


- `8032 &lt;https://github.com/pytest-dev/pytest/issues/8032&gt;`_: :meth:`doClassCleanups &lt;unittest.TestCase.doClassCleanups&gt;` (introduced in :mod:`unittest` in Python and 3.8) is now called appropriately.



Bug Fixes
---------

- `4824 &lt;https://github.com/pytest-dev/pytest/issues/4824&gt;`_: Fixed quadratic behavior and improved performance of collection of items using autouse fixtures and xunit fixtures.


- `7758 &lt;https://github.com/pytest-dev/pytest/issues/7758&gt;`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.


- `7911 &lt;https://github.com/pytest-dev/pytest/issues/7911&gt;`_: Directories created by by :fixture:`tmp_path` and :fixture:`tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.


- `7913 &lt;https://github.com/pytest-dev/pytest/issues/7913&gt;`_: Fixed a crash or hang in :meth:`pytester.spawn &lt;_pytest.pytester.Pytester.spawn&gt;` when the :mod:`readline` module is involved.


- `7951 &lt;https://github.com/pytest-dev/pytest/issues/7951&gt;`_: Fixed handling of recursive symlinks when collecting tests.


- `7981 &lt;https://github.com/pytest-dev/pytest/issues/7981&gt;`_: Fixed symlinked directories not being followed during collection. Regressed in pytest 6.1.0.


- `8016 &lt;https://github.com/pytest-dev/pytest/issues/8016&gt;`_: Fixed only one doctest being collected when using ``pytest --doctest-modules path/to/an/__init__.py``.



Improved Documentation
----------------------

- `7429 &lt;https://github.com/pytest-dev/pytest/issues/7429&gt;`_: Add more information and use cases about skipping doctests.


- `7780 &lt;https://github.com/pytest-dev/pytest/issues/7780&gt;`_: Classes which should not be inherited from are now marked ``final class`` in the API reference.


- `7872 &lt;https://github.com/pytest-dev/pytest/issues/7872&gt;`_: ``_pytest.config.argparsing.Parser.addini()`` accepts explicit ``None`` and ``&quot;string&quot;``.


- `7878 &lt;https://github.com/pytest-dev/pytest/issues/7878&gt;`_: In pull request section, ask to commit after editing changelog and authors file.



Trivial/Internal Changes
------------------------

- `7802 &lt;https://github.com/pytest-dev/pytest/issues/7802&gt;`_: The ``attrs`` dependency requirement is now &gt;=19.2.0 instead of &gt;=17.4.0.


- `8014 &lt;https://github.com/pytest-dev/pytest/issues/8014&gt;`_: `.pyc` files created by pytest&#39;s assertion rewriting now conform to the newer PEP-552 format on Python&gt;=3.7.
  (These files are internal and only interpreted by pytest itself.)
   ```
   
  
  
   ### 6.1.2
   ```
   =========================

Bug Fixes
---------

- `7758 &lt;https://github.com/pytest-dev/pytest/issues/7758&gt;`_: Fixed an issue where some files in packages are getting lost from ``--lf`` even though they contain tests that failed. Regressed in pytest 5.4.0.


- `7911 &lt;https://github.com/pytest-dev/pytest/issues/7911&gt;`_: Directories created by `tmpdir` are now considered stale after 3 days without modification (previous value was 3 hours) to avoid deleting directories still in use in long running test suites.



Improved Documentation
----------------------

- `7815 &lt;https://github.com/pytest-dev/pytest/issues/7815&gt;`_: Improve deprecation warning message for ``pytest._fillfuncargs()``.
   ```
   
  
  
   ### 6.1.1
   ```
   =========================

Bug Fixes
---------

- `7807 &lt;https://github.com/pytest-dev/pytest/issues/7807&gt;`_: Fixed regression in pytest 6.1.0 causing incorrect rootdir to be determined in some non-trivial cases where parent directories have config files as well.


- `7814 &lt;https://github.com/pytest-dev/pytest/issues/7814&gt;`_: Fixed crash in header reporting when :confval:`testpaths` is used and contains absolute paths (regression in 6.1.0).
   ```
   
  
  
   ### 6.1.0
   ```
   =========================

Breaking Changes
----------------

- `5585 &lt;https://github.com/pytest-dev/pytest/issues/5585&gt;`_: As per our policy, the following features which have been deprecated in the 5.X series are now
  removed:

  * The ``funcargnames`` read-only property of ``FixtureRequest``, ``Metafunc``, and ``Function`` classes. Use ``fixturenames`` attribute.

  * ``pytest.fixture`` no longer supports positional arguments, pass all arguments by keyword instead.

  * Direct construction of ``Node`` subclasses now raise an error, use ``from_parent`` instead.

  * The default value for ``junit_family`` has changed to ``xunit2``. If you require the old format, add ``junit_family=xunit1`` to your configuration file.

  * The ``TerminalReporter`` no longer has a ``writer`` attribute. Plugin authors may use the public functions of the ``TerminalReporter`` instead of accessing the ``TerminalWriter`` object directly.

  * The ``--result-log`` option has been removed. Users are recommended to use the `pytest-reportlog &lt;https://github.com/pytest-dev/pytest-reportlog&gt;`__ plugin instead.


  For more information consult
  `Deprecations and Removals &lt;https://docs.pytest.org/en/stable/deprecations.html&gt;`__ in the docs.



Deprecations
------------

- `6981 &lt;https://github.com/pytest-dev/pytest/issues/6981&gt;`_: The ``pytest.collect`` module is deprecated: all its names can be imported from ``pytest`` directly.


- `7097 &lt;https://github.com/pytest-dev/pytest/issues/7097&gt;`_: The ``pytest._fillfuncargs`` function is deprecated. This function was kept
  for backward compatibility with an older plugin.

  It&#39;s functionality is not meant to be used directly, but if you must replace
  it, use `function._request._fillfixtures()` instead, though note this is not
  a public API and may break in the future.


- `7210 &lt;https://github.com/pytest-dev/pytest/issues/7210&gt;`_: The special ``-k &#39;-expr&#39;`` syntax to ``-k`` is deprecated. Use ``-k &#39;not expr&#39;``
  instead.

  The special ``-k &#39;expr:&#39;`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.


- `7255 &lt;https://github.com/pytest-dev/pytest/issues/7255&gt;`_: The :func:`pytest_warning_captured &lt;_pytest.hookspec.pytest_warning_captured&gt;` hook is deprecated in favor
  of :func:`pytest_warning_recorded &lt;_pytest.hookspec.pytest_warning_recorded&gt;`, and will be removed in a future version.


- `7648 &lt;https://github.com/pytest-dev/pytest/issues/7648&gt;`_: The ``gethookproxy()`` and ``isinitpath()`` methods of ``FSCollector`` and ``Package`` are deprecated;
  use ``self.session.gethookproxy()`` and ``self.session.isinitpath()`` instead.
  This should work on all pytest versions.



Features
--------

- `7667 &lt;https://github.com/pytest-dev/pytest/issues/7667&gt;`_: New ``--durations-min`` command-line flag controls the minimal duration for inclusion in the slowest list of tests shown by ``--durations``. Previously this was hard-coded to ``0.005s``.



Improvements
------------

- `6681 &lt;https://github.com/pytest-dev/pytest/issues/6681&gt;`_: Internal pytest warnings issued during the early stages of initialization are now properly handled and can filtered through :confval:`filterwarnings` or ``--pythonwarnings/-W``.

  This also fixes a number of long standing issues: `2891 &lt;https://github.com/pytest-dev/pytest/issues/2891&gt;`__, `#7620 &lt;https://github.com/pytest-dev/pytest/issues/7620&gt;`__, `#7426 &lt;https://github.com/pytest-dev/pytest/issues/7426&gt;`__.


- `7572 &lt;https://github.com/pytest-dev/pytest/issues/7572&gt;`_: When a plugin listed in ``required_plugins`` is missing or an unknown config key is used with ``--strict-config``, a simple error message is now shown instead of a stacktrace.


- `7685 &lt;https://github.com/pytest-dev/pytest/issues/7685&gt;`_: Added two new attributes :attr:`rootpath &lt;_pytest.config.Config.rootpath&gt;` and :attr:`inipath &lt;_pytest.config.Config.inipath&gt;` to :class:`Config &lt;_pytest.config.Config&gt;`.
  These attributes are :class:`pathlib.Path` versions of the existing :attr:`rootdir &lt;_pytest.config.Config.rootdir&gt;` and :attr:`inifile &lt;_pytest.config.Config.inifile&gt;` attributes,
  and should be preferred over them when possible.


- `7780 &lt;https://github.com/pytest-dev/pytest/issues/7780&gt;`_: Public classes which are not designed to be inherited from are now marked `final &lt;https://docs.python.org/3/library/typing.html#typing.final&gt;`_.
  Code which inherits from these classes will trigger a type-checking (e.g. mypy) error, but will still work in runtime.
  Currently the ``final`` designation does not appear in the API Reference but hopefully will in the future.



Bug Fixes
---------

- `1953 &lt;https://github.com/pytest-dev/pytest/issues/1953&gt;`_: Fixed error when overwriting a parametrized fixture, while also reusing the super fixture value.

  .. code-block:: python

       conftest.py
      import pytest


      pytest.fixture(params=[1, 2])
      def foo(request):
          return request.param


       test_foo.py
      import pytest


      pytest.fixture
      def foo(foo):
          return foo * 2


- `4984 &lt;https://github.com/pytest-dev/pytest/issues/4984&gt;`_: Fixed an internal error crash with ``IndexError: list index out of range`` when
  collecting a module which starts with a decorated function, the decorator
  raises, and assertion rewriting is enabled.


- `7591 &lt;https://github.com/pytest-dev/pytest/issues/7591&gt;`_: pylint shouldn&#39;t complain anymore about unimplemented abstract methods when inheriting from :ref:`File &lt;non-python tests&gt;`.


- `7628 &lt;https://github.com/pytest-dev/pytest/issues/7628&gt;`_: Fixed test collection when a full path without a drive letter was passed to pytest on Windows (for example ``\projects\tests\test.py`` instead of ``c:\projects\tests\pytest.py``).


- `7638 &lt;https://github.com/pytest-dev/pytest/issues/7638&gt;`_: Fix handling of command-line options that appear as paths but trigger an OS-level syntax error on Windows, such as the options used internally by ``pytest-xdist``.


- `7742 &lt;https://github.com/pytest-dev/pytest/issues/7742&gt;`_: Fixed INTERNALERROR when accessing locals / globals with faulty ``exec``.



Improved Documentation
----------------------

- `1477 &lt;https://github.com/pytest-dev/pytest/issues/1477&gt;`_: Removed faq.rst and its reference in contents.rst.



Trivial/Internal Changes
------------------------

- `7536 &lt;https://github.com/pytest-dev/pytest/issues/7536&gt;`_: The internal ``junitxml`` plugin has rewritten to use ``xml.etree.ElementTree``.
  The order of attributes in XML elements might differ. Some unneeded escaping is
  no longer performed.


- `7587 &lt;https://github.com/pytest-dev/pytest/issues/7587&gt;`_: The dependency on the ``more-itertools`` package has been removed.


- `7631 &lt;https://github.com/pytest-dev/pytest/issues/7631&gt;`_: The result type of :meth:`capfd.readouterr() &lt;_pytest.capture.CaptureFixture.readouterr&gt;` (and similar) is no longer a namedtuple,
  but should behave like one in all respects. This was done for technical reasons.


- `7671 &lt;https://github.com/pytest-dev/pytest/issues/7671&gt;`_: When collecting tests, pytest finds test classes and functions by examining the
  attributes of python objects (modules, classes and instances). To speed up this
  process, pytest now ignores builtin attributes (like ``__class__``,
  ``__delattr__`` and ``__new__``) without consulting the :confval:`python_classes` and
  :confval:`python_functions` configuration options and without passing them to plugins
  using the :func:`pytest_pycollect_makeitem &lt;_pytest.hookspec.pytest_pycollect_makeitem&gt;` hook.
   ```
   
  
  
   ### 6.0.2
   ```
   =========================

Bug Fixes
---------

- `7148 &lt;https://github.com/pytest-dev/pytest/issues/7148&gt;`_: Fixed ``--log-cli`` potentially causing unrelated ``print`` output to be swallowed.


- `7672 &lt;https://github.com/pytest-dev/pytest/issues/7672&gt;`_: Fixed log-capturing level restored incorrectly if ``caplog.set_level`` is called more than once.


- `7686 &lt;https://github.com/pytest-dev/pytest/issues/7686&gt;`_: Fixed `NotSetType.token` being used as the parameter ID when the parametrization list is empty.
  Regressed in pytest 6.0.0.


- `7707 &lt;https://github.com/pytest-dev/pytest/issues/7707&gt;`_: Fix internal error when handling some exceptions that contain multiple lines or the style uses multiple lines (``--tb=line`` for example).
   ```
   
  
  
   ### 6.0.1
   ```
   =========================

Bug Fixes
---------

- `7394 &lt;https://github.com/pytest-dev/pytest/issues/7394&gt;`_: Passing an empty ``help`` value to ``Parser.add_option`` is now accepted instead of crashing when running ``pytest --help``.
  Passing ``None`` raises a more informative ``TypeError``.


- `7558 &lt;https://github.com/pytest-dev/pytest/issues/7558&gt;`_: Fix pylint ``not-callable`` lint on ``pytest.mark.parametrize()`` and the other builtin marks:
  ``skip``, ``skipif``, ``xfail``, ``usefixtures``, ``filterwarnings``.


- `7559 &lt;https://github.com/pytest-dev/pytest/issues/7559&gt;`_: Fix regression in plugins using ``TestReport.longreprtext`` (such as ``pytest-html``) when ``TestReport.longrepr`` is not a string.


- `7569 &lt;https://github.com/pytest-dev/pytest/issues/7569&gt;`_: Fix logging capture handler&#39;s level not reset on teardown after a call to ``caplog.set_level()``.
   ```
   
  
  
   ### 6.0.0
   ```
   =========================

(**Please see the full set of changes for this release also in the 6.0.0rc1 notes below**)

Breaking Changes
----------------

- `5584 &lt;https://github.com/pytest-dev/pytest/issues/5584&gt;`_: **PytestDeprecationWarning are now errors by default.**

  Following our plan to remove deprecated features with as little disruption as
  possible, all warnings of type ``PytestDeprecationWarning`` now generate errors
  instead of warning messages.

  **The affected features will be effectively removed in pytest 6.1**, so please consult the
  `Deprecations and Removals &lt;https://docs.pytest.org/en/latest/deprecations.html&gt;`__
  section in the docs for directions on how to update existing code.

  In the pytest ``6.0.X`` series, it is possible to change the errors back into warnings as a
  stopgap measure by adding this to your ``pytest.ini`` file:

  .. code-block:: ini

      [pytest]
      filterwarnings =
          ignore::pytest.PytestDeprecationWarning

  But this will stop working when pytest ``6.1`` is released.

  **If you have concerns** about the removal of a specific feature, please add a
  comment to `5584 &lt;https://github.com/pytest-dev/pytest/issues/5584&gt;`__.


- `7472 &lt;https://github.com/pytest-dev/pytest/issues/7472&gt;`_: The ``exec_()`` and ``is_true()`` methods of ``_pytest._code.Frame`` have been removed.



Features
--------

- `7464 &lt;https://github.com/pytest-dev/pytest/issues/7464&gt;`_: Added support for :envvar:`NO_COLOR` and :envvar:`FORCE_COLOR` environment variables to control colored output.



Improvements
------------

- `7467 &lt;https://github.com/pytest-dev/pytest/issues/7467&gt;`_: ``--log-file`` CLI option and ``log_file`` ini marker now create subdirectories if needed.


- `7489 &lt;https://github.com/pytest-dev/pytest/issues/7489&gt;`_: The :func:`pytest.raises` function has a clearer error message when ``match`` equals the obtained string but is not a regex match. In this case it is suggested to escape the regex.



Bug Fixes
---------

- `7392 &lt;https://github.com/pytest-dev/pytest/issues/7392&gt;`_: Fix the reported location of tests skipped with ``pytest.mark.skip`` when ``--runxfail`` is used.


- `7491 &lt;https://github.com/pytest-dev/pytest/issues/7491&gt;`_: :fixture:`tmpdir` and :fixture:`tmp_path` no longer raise an error if the lock to check for
  stale temporary directories is not accessible.


- `7517 &lt;https://github.com/pytest-dev/pytest/issues/7517&gt;`_: Preserve line endings when captured via ``capfd``.


- `7534 &lt;https://github.com/pytest-dev/pytest/issues/7534&gt;`_: Restored the previous formatting of ``TracebackEntry.__str__`` which was changed by accident.



Improved Documentation
----------------------

- `7422 &lt;https://github.com/pytest-dev/pytest/issues/7422&gt;`_: Clarified when the ``usefixtures`` mark can apply fixtures to test.


- `7441 &lt;https://github.com/pytest-dev/pytest/issues/7441&gt;`_: Add a note about ``-q`` option used in getting started guide.



Trivial/Internal Changes
------------------------

- `7389 &lt;https://github.com/pytest-dev/pytest/issues/7389&gt;`_: Fixture scope ``package`` is no longer considered experimental.
   ```
   
  
  
   ### 6.0.0rc1
   ```
   ============================

Breaking Changes
----------------

- `1316 &lt;https://github.com/pytest-dev/pytest/issues/1316&gt;`_: ``TestReport.longrepr`` is now always an instance of ``ReprExceptionInfo``. Previously it was a ``str`` when a test failed with ``pytest.fail(..., pytrace=False)``.


- `5965 &lt;https://github.com/pytest-dev/pytest/issues/5965&gt;`_: symlinks are no longer resolved during collection and matching `conftest.py` files with test file paths.

  Resolving symlinks for the current directory and during collection was introduced as a bugfix in 3.9.0, but it actually is a new feature which had unfortunate consequences in Windows and surprising results in other platforms.

  The team decided to step back on resolving symlinks at all, planning to review this in the future with a more solid solution (see discussion in
  `6523 &lt;https://github.com/pytest-dev/pytest/pull/6523&gt;`__ for details).

  This might break test suites which made use of this feature; the fix is to create a symlink
  for the entire test tree, and not only to partial files/tress as it was possible previously.


- `6505 &lt;https://github.com/pytest-dev/pytest/issues/6505&gt;`_: ``Testdir.run().parseoutcomes()`` now always returns the parsed nouns in plural form.

  Originally ``parseoutcomes()`` would always returns the nouns in plural form, but a change
  meant to improve the terminal summary by using singular form single items (``1 warning`` or ``1 error``)
  caused an unintended regression by changing the keys returned by ``parseoutcomes()``.

  Now the API guarantees to always return the plural form, so calls like this:

  .. code-block:: python

      result = testdir.runpytest()
      result.assert_outcomes(error=1)

  Need to be changed to:


  .. code-block:: python

      result = testdir.runpytest()
      result.assert_outcomes(errors=1)


- `6903 &lt;https://github.com/pytest-dev/pytest/issues/6903&gt;`_: The ``os.dup()`` function is now assumed to exist. We are not aware of any
  supported Python 3 implementations which do not provide it.


- `7040 &lt;https://github.com/pytest-dev/pytest/issues/7040&gt;`_: ``-k`` no longer matches against the names of the directories outside the test session root.

  Also, ``pytest.Package.name`` is now just the name of the directory containing the package&#39;s
  ``__init__.py`` file, instead of the full path. This is consistent with how the other nodes
  are named, and also one of the reasons why ``-k`` would match against any directory containing
  the test suite.


- `7122 &lt;https://github.com/pytest-dev/pytest/issues/7122&gt;`_: Expressions given to the ``-m`` and ``-k`` options are no longer evaluated using Python&#39;s :func:`eval`.
  The format supports ``or``, ``and``, ``not``, parenthesis and general identifiers to match against.
  Python constants, keywords or other operators are no longer evaluated differently.


- `7135 &lt;https://github.com/pytest-dev/pytest/issues/7135&gt;`_: Pytest now uses its own ``TerminalWriter`` class instead of using the one from the ``py`` library.
  Plugins generally access this class through ``TerminalReporter.writer``, ``TerminalReporter.write()``
  (and similar methods), or ``_pytest.config.create_terminal_writer()``.

  The following breaking changes were made:

  - Output (``write()`` method and others) no longer flush implicitly; the flushing behavior
    of the underlying file is respected. To flush explicitly (for example, if you
    want output to be shown before an end-of-line is printed), use ``write(flush=True)`` or
    ``terminal_writer.flush()``.
  - Explicit Windows console support was removed, delegated to the colorama library.
  - Support for writing ``bytes`` was removed.
  - The ``reline`` method and ``chars_on_current_line`` property were removed.
  - The ``stringio`` and ``encoding`` arguments was removed.
  - Support for passing a callable instead of a file was removed.


- `7224 &lt;https://github.com/pytest-dev/pytest/issues/7224&gt;`_: The `item.catch_log_handler` and `item.catch_log_handlers` attributes, set by the
  logging plugin and never meant to be public, are no longer available.

  The deprecated ``--no-print-logs`` option and ``log_print`` ini option are removed. Use ``--show-capture`` instead.


- `7226 &lt;https://github.com/pytest-dev/pytest/issues/7226&gt;`_: Removed the unused ``args`` parameter from ``pytest.Function.__init__``.


- `7418 &lt;https://github.com/pytest-dev/pytest/issues/7418&gt;`_: Removed the `pytest_doctest_prepare_content` hook specification. This hook
  hasn&#39;t been triggered by pytest for at least 10 years.


- `7438 &lt;https://github.com/pytest-dev/pytest/issues/7438&gt;`_: Some changes were made to the internal ``_pytest._code.source``, listed here
  for the benefit of plugin authors who may be using it:

  - The ``deindent`` argument to ``Source()`` has been removed, now it is always true.
  - Support for zero or multiple arguments to ``Source()`` has been removed.
  - Support for comparing ``Source`` with an ``str`` has been removed.
  - The methods ``Source.isparseable()`` and ``Source.putaround()`` have been removed.
  - The method ``Source.compile()`` and function ``_pytest._code.compile()`` have
    been removed; use plain ``compile()`` instead.
  - The function ``_pytest._code.source.getsource()`` has been removed; use
    ``Source()`` directly instead.



Deprecations
------------

- `7210 &lt;https://github.com/pytest-dev/pytest/issues/7210&gt;`_: The special ``-k &#39;-expr&#39;`` syntax to ``-k`` is deprecated. Use ``-k &#39;not expr&#39;``
  instead.

  The special ``-k &#39;expr:&#39;`` syntax to ``-k`` is deprecated. Please open an issue
  if you use this and want a replacement.

- `4049 &lt;https://github.com/pytest-dev/pytest/issues/4049&gt;`_: ``pytest_warning_captured`` is deprecated in favor of the ``pytest_warning_recorded`` hook.


Features
--------

- `1556 &lt;https://github.com/pytest-dev/pytest/issues/1556&gt;`_: pytest now supports ``pyproject.toml`` files for configuration.

  The configuration options is similar to the one available in other formats, but must be defined
  in a ``[tool.pytest.ini_options]`` table to be picked up by pytest:

  .. code-block:: toml

       pyproject.toml
      [tool.pytest.ini_options]
      minversion = &quot;6.0&quot;
      addopts = &quot;-ra -q&quot;
      testpaths = [
          &quot;tests&quot;,
          &quot;integration&quot;,
      ]

  More information can be found `in the docs &lt;https://docs.pytest.org/en/stable/customize.html#configuration-file-formats&gt;`__.


- `3342 &lt;https://github.com/pytest-dev/pytest/issues/3342&gt;`_: pytest now includes inline type annotations and exposes them to user programs.
  Most of the user-facing API is covered, as well as internal code.

  If you are running a type checker such as mypy on your tests, you may start
  noticing type errors indicating incorrect usage. If you run into an error that
  you believe to be incorrect, please let us know in an issue.

  The types were developed against mypy version 0.780. Versions before 0.750
  are known not to work. We recommend using the latest version. Other type
  checkers may work as well, but they are not officially verified to work by
  pytest yet.


- `4049 &lt;https://github.com/pytest-dev/pytest/issues/4049&gt;`_: Introduced a new hook named `pytest_warning_recorded` to convey information about warnings captured by the internal `pytest` warnings plugin.

  This hook is meant to replace `pytest_warning_captured`, which is deprecated and will be removed in a future release.


- `6471 &lt;https://github.com/pytest-dev/pytest/issues/6471&gt;`_: New command-line flags:

  * `--no-header`: disables the initial header, including platform, version, and plugins.
  * `--no-summary`: disables the final test summary, including warnings.


- `6856 &lt;https://github.com/pytest-dev/pytest/issues/6856&gt;`_: A warning is now shown when an unknown key is read from a config INI file.

  The `--strict-config` flag has been added to treat these warnings as errors.


- `6906 &lt;https://github.com/pytest-dev/pytest/issues/6906&gt;`_: Added `--code-highlight` command line option to enable/disable code highlighting in terminal output.


- `7245 &lt;https://github.com/pytest-dev/pytest/issues/7245&gt;`_: New ``--import-mode=importlib`` option that uses `importlib &lt;https://docs.python.org/3/library/importlib.html&gt;`__ to import test modules.

  Traditionally pytest used ``__import__`` while changing ``sys.path`` to import test modules (which
  also changes ``sys.modules`` as a side-effect), which works but has a number of drawbacks, like requiring test modules
  that don&#39;t live in packages to have unique names (as they need to reside under a unique name in ``sys.modules``).

  ``--import-mode=importlib`` uses more fine grained import mechanisms from ``importlib`` which don&#39;t
  require pytest to change ``sys.path`` or ``sys.modules`` at all, eliminating much of the drawbacks
  of the previous mode.

  We intend to make ``--import-mode=importlib`` the default in future versions, so users are encouraged
  to try the new mode and provide feedback (both positive or negative) in issue `7245 &lt;https://github.com/pytest-dev/pytest/issues/7245&gt;`__.

  You can read more about this option in `the documentation &lt;https://docs.pytest.org/en/latest/pythonpath.html#import-modes&gt;`__.


- `7305 &lt;https://github.com/pytest-dev/pytest/issues/7305&gt;`_: New ``required_plugins`` configuration option allows the user to specify a list of plugins, including version information, that are required for pytest to run. An error is raised if any required plugins are not found when running pytest.


Improvements
------------

- `4375 &lt;https://github.com/pytest-dev/pytest/issues/4375&gt;`_: The ``pytest`` command now suppresses the ``BrokenPipeError`` error message that
  is printed to stderr when the output of ``pytest`` is piped and and the pipe is
  closed by the piped-to program (common examples are ``less`` and ``head``).


- `4391 &lt;https://github.com/pytest-dev/pytest/issues/4391&gt;`_: Improved precision of test durations measurement. ``CallInfo`` items now have a new ``&lt;CallInfo&gt;.duration`` attribute, created using ``time.perf_counter()``. This attribute is used to fill the ``&lt;TestReport&gt;.duration`` attribute, which is more accurate than the previous ``&lt;CallInfo&gt;.stop - &lt;CallInfo&gt;.start`` (as these are based on ``time.time()``).


- `4675 &lt;https://github.com/pytest-dev/pytest/issues/4675&gt;`_: Rich comparison for dataclasses and `attrs`-classes is now recursive.


- `6285 &lt;https://github.com/pytest-dev/pytest/issues/6285&gt;`_: Exposed the `pytest.FixtureLookupError` exception which is raised by `request.getfixturevalue()`
  (where `request` is a `FixtureRequest` fixture) when a fixture with the given name cannot be returned.


- `6433 &lt;https://github.com/pytest-dev/pytest/issues/6433&gt;`_: If an error is encountered while formatting the message in a logging call, for
  example ``logging.warning(&quot;oh no!: %s: %s&quot;, &quot;first&quot;)`` (a second argument is
  missing), pytest now propagates the error, likely causing the test to fail.

  Previously, such a mistake would cause an error to be printed to stderr, which
  is not displayed by default for passing tests. This change makes the mistake
  visible during testing.

  You may supress this behavior temporarily or permanently by setting
  ``logging.raiseExceptions = False``.


- `6817 &lt;https://github.com/pytest-dev/pytest/issues/6817&gt;`_: Explicit new-lines in help texts of command-line options are preserved, allowing plugins better control
  of the help displayed to users.


- `6940 &lt;https://github.com/pytest-dev/pytest/issues/6940&gt;`_: When using the ``--duration`` option, the terminal message output is now more precise about the number and duration of hidden items.


- `6991 &lt;https://github.com/pytest-dev/pytest/issues/6991&gt;`_: Collected files are displayed after any reports from hooks, e.g. the status from ``--lf``.


- `7091 &lt;https://github.com/pytest-dev/pytest/issues/7091&gt;`_: When ``fd`` capturing is used, through ``--capture=fd`` or the ``capfd`` and
  ``capfdbinary`` fixtures, and the file descriptor (0, 1, 2) cannot be
  duplicated, FD capturing is still performed. Previously, direct writes to the
  file descriptors would fail or be lost in this case.


- `7119 &lt;https://github.com/pytest-dev/pytest/issues/7119&gt;`_: Exit with an error if the ``--basetemp`` argument is empty, is the current working directory or is one of the parent directories.
  This is done to protect against accidental data loss, as any directory passed to this argument is cleared.


- `7128 &lt;https://github.com/pytest-dev/pytest/issues/7128&gt;`_: `pytest --version` now displays just the pytest version, while `pytest --version --version` displays more verbose information including plugins. This is more consistent with how other tools show `--version`.


- `7133 &lt;https://github.com/pytest-dev/pytest/issues/7133&gt;`_: :meth:`caplog.set_level() &lt;_pytest.logging.LogCaptureFixture.set_level&gt;` will now override any :confval:`log_level` set via the CLI or configuration file.


- `7159 &lt;https://github.com/pytest-dev/pytest/issues/7159&gt;`_: :meth:`caplog.set_level() &lt;_pytest.logging.LogCaptureFixture.set_level&gt;` and :meth:`caplog.at_level() &lt;_pytest.logging.LogCaptureFixture.at_level&gt;` no longer affect
  the level of logs that are shown in the *Captured log report* report section.


- `7348 &lt;https://github.com/pytest-dev/pytest/issues/7348&gt;`_: Improve recursive diff report for comparison asserts on dataclasses / attrs.


- `7385 &lt;https://github.com/pytest-dev/pytest/issues/7385&gt;`_: ``--junitxml`` now includes the exception cause in the ``message`` XML attribute for failures during setup and teardown.

  Previously:

  .. code-block:: xml

      &lt;error message=&quot;test setup failure&quot;&gt;

  Now:

  .. code-block:: xml

      &lt;error message=&quot;failed on setup with &amp;quot;ValueError: Some error during setup&amp;quot;&quot;&gt;



Bug Fixes
---------

- `1120 &lt;https://github.com/pytest-dev/pytest/issues/1120&gt;`_: Fix issue where directories from :fixture:`tmpdir` are not removed properly when multiple instances of pytest are running in parallel.


- `4583 &lt;https://github.com/pytest-dev/pytest/issues/4583&gt;`_: Prevent crashing and provide a user-friendly error when a marker expression (`-m`) invoking of :func:`eval` raises any exception.


- `4677 &lt;https://github.com/pytest-dev/pytest/issues/4677&gt;`_: The path shown in the summary report for SKIPPED tests is now always relative. Previously it was sometimes absolute.


- `5456 &lt;https://github.com/pytest-dev/pytest/issues/5456&gt;`_: Fix a possible race condition when trying to remove lock files used to control access to folders
  created by :fixture:`tmp_path` and :fixture:`tmpdir`.


- `6240 &lt;https://github.com/pytest-dev/pytest/issues/6240&gt;`_: Fixes an issue where logging during collection step caused duplication of log
  messages to stderr.


- `6428 &lt;https://github.com/pytest-dev/pytest/issues/6428&gt;`_: Paths appearing in error messages are now correct in case the current working directory has
  changed since the start of the session.


- `6755 &lt;https://github.com/pytest-dev/pytest/issues/6755&gt;`_: Support deleting paths longer than 260 characters on windows created inside :fixture:`tmpdir`.


- `6871 &lt;https://github.com/pytest-dev/pytest/issues/6871&gt;`_: Fix crash with captured output when using :fixture:`capsysbinary`.


- `6909 &lt;https://github.com/pytest-dev/pytest/issues/6909&gt;`_: Revert the change introduced by `#6330 &lt;https://github.com/pytest-dev/pytest/pull/6330&gt;`_, which required all arguments to ``pytest.mark.parametrize`` to be explicitly defined in the function signature.

  The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.


- `6910 &lt;https://github.com/pytest-dev/pytest/issues/6910&gt;`_: Fix crash when plugins return an unknown stats while using the ``--reportlog`` option.


- `6924 &lt;https://github.com/pytest-dev/pytest/issues/6924&gt;`_: Ensure a ``unittest.IsolatedAsyncioTestCase`` is actually awaited.


- `6925 &lt;https://github.com/pytest-dev/pytest/issues/6925&gt;`_: Fix `TerminalRepr` instances to be hashable again.


- `6947 &lt;https://github.com/pytest-dev/pytest/issues/6947&gt;`_: Fix regression where functions registered with :meth:`unittest.TestCase.addCleanup` were not being called on test failures.


- `6951 &lt;https://github.com/pytest-dev/pytest/issues/6951&gt;`_: Allow users to still set the deprecated ``TerminalReporter.writer`` attribute.


- `6956 &lt;https://github.com/pytest-dev/pytest/issues/6956&gt;`_: Prevent pytest from printing `ConftestImportFailure` traceback to stdout.


- `6991 &lt;https://github.com/pytest-dev/pytest/issues/6991&gt;`_: Fix regressions with `--lf` filtering too much since pytest 5.4.


- `6992 &lt;https://github.com/pytest-dev/pytest/issues/6992&gt;`_: Revert &quot;tmpdir: clean up indirection via config for factories&quot; `#6767 &lt;https://github.com/pytest-dev/pytest/issues/6767&gt;`_ as it breaks pytest-xdist.


- `7061 &lt;https://github.com/pytest-dev/pytest/issues/7061&gt;`_: When a yielding fixture fails to yield a value, report a test setup error instead of crashing.


- `7076 &lt;https://github.com/pytest-dev/pytest/issues/7076&gt;`_: The path of file skipped by ``pytest.mark.skip`` in the SKIPPED report is now relative to invocation directory. Previously it was relative to root directory.


- `7110 &lt;https://github.com/pytest-dev/pytest/issues/7110&gt;`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.


- `7126 &lt;https://github.com/pytest-dev/pytest/issues/7126&gt;`_: ``--setup-show`` now doesn&#39;t raise an error when a bytes value is used as a ``parametrize``
  parameter when Python is called with the ``-bb`` flag.


- `7143 &lt;https://github.com/pytest-dev/pytest/issues/7143&gt;`_: Fix :meth:`pytest.File.from_parent` so it forwards extra keyword arguments to the constructor.


- `7145 &lt;https://github.com/pytest-dev/pytest/issues/7145&gt;`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.


- `7150 &lt;https://github.com/pytest-dev/pytest/issues/7150&gt;`_: Prevent hiding the underlying exception when ``ConfTestImportFailure`` is raised.


- `7180 &lt;https://github.com/pytest-dev/pytest/issues/7180&gt;`_: Fix ``_is_setup_py`` for files encoded differently than locale.


- `7215 &lt;https://github.com/pytest-dev/pytest/issues/7215&gt;`_: Fix regression where running with ``--pdb`` would call :meth:`unittest.TestCase.tearDown` for skipped tests.


- `7253 &lt;https://github.com/pytest-dev/pytest/issues/7253&gt;`_: When using ``pytest.fixture`` on a function directly, as in ``pytest.fixture(func)``,
  if the ``autouse`` or ``params`` arguments are also passed, the function is no longer
  ignored, but is marked as a fixture.


- `7360 &lt;https://github.com/pytest-dev/pytest/issues/7360&gt;`_: Fix possibly incorrect evaluation of string expressions passed to ``pytest.mark.skipif`` and ``pytest.mark.xfail``,
  in rare circumstances where the exact same string is used but refers to different global values.


- `7383 &lt;https://github.com/pytest-dev/pytest/issues/7383&gt;`_: Fixed exception causes all over the codebase, i.e. use `raise new_exception from old_exception` when wrapping an exception.



Improved Documentation
----------------------

- `7202 &lt;https://github.com/pytest-dev/pytest/issues/7202&gt;`_: The development guide now links to the contributing section of the docs and `RELEASING.rst` on GitHub.


- `7233 &lt;https://github.com/pytest-dev/pytest/issues/7233&gt;`_: Add a note about ``--strict`` and ``--strict-markers`` and the preference for the latter one.


- `7345 &lt;https://github.com/pytest-dev/pytest/issues/7345&gt;`_: Explain indirect parametrization and markers for fixtures.



Trivial/Internal Changes
------------------------

- `7035 &lt;https://github.com/pytest-dev/pytest/issues/7035&gt;`_: The ``originalname`` attribute of ``_pytest.python.Function`` now defaults to ``name`` if not
  provided explicitly, and is always set.


- `7264 &lt;https://github.com/pytest-dev/pytest/issues/7264&gt;`_: The dependency on the ``wcwidth`` package has been removed.


- `7291 &lt;https://github.com/pytest-dev/pytest/issues/7291&gt;`_: Replaced ``py.iniconfig`` with `iniconfig &lt;https://pypi.org/project/iniconfig/&gt;`__.


- `7295 &lt;https://github.com/pytest-dev/pytest/issues/7295&gt;`_: ``src/_pytest/config/__init__.py`` now uses the ``warnings`` module to report warnings instead of ``sys.stderr.write``.


- `7356 &lt;https://github.com/pytest-dev/pytest/issues/7356&gt;`_: Remove last internal uses of deprecated *slave* term from old ``pytest-xdist``.


- `7357 &lt;https://github.com/pytest-dev/pytest/issues/7357&gt;`_: ``py``&gt;=1.8.2 is now required.
   ```
   
  
  
   ### 5.4.3
   ```
   =========================

Bug Fixes
---------

- `6428 &lt;https://github.com/pytest-dev/pytest/issues/6428&gt;`_: Paths appearing in error messages are now correct in case the current working directory has
  changed since the start of the session.


- `6755 &lt;https://github.com/pytest-dev/pytest/issues/6755&gt;`_: Support deleting paths longer than 260 characters on windows created inside tmpdir.


- `6956 &lt;https://github.com/pytest-dev/pytest/issues/6956&gt;`_: Prevent pytest from printing ConftestImportFailure traceback to stdout.


- `7150 &lt;https://github.com/pytest-dev/pytest/issues/7150&gt;`_: Prevent hiding the underlying exception when ``ConfTestImportFailure`` is raised.


- `7215 &lt;https://github.com/pytest-dev/pytest/issues/7215&gt;`_: Fix regression where running with ``--pdb`` would call the ``tearDown`` methods of ``unittest.TestCase``
  subclasses for skipped tests.
   ```
   
  
  
   ### 5.4.2
   ```
   =========================

Bug Fixes
---------

- `6871 &lt;https://github.com/pytest-dev/pytest/issues/6871&gt;`_: Fix crash with captured output when using the :fixture:`capsysbinary fixture &lt;capsysbinary&gt;`.


- `6924 &lt;https://github.com/pytest-dev/pytest/issues/6924&gt;`_: Ensure a ``unittest.IsolatedAsyncioTestCase`` is actually awaited.


- `6925 &lt;https://github.com/pytest-dev/pytest/issues/6925&gt;`_: Fix TerminalRepr instances to be hashable again.


- `6947 &lt;https://github.com/pytest-dev/pytest/issues/6947&gt;`_: Fix regression where functions registered with ``TestCase.addCleanup`` were not being called on test failures.


- `6951 &lt;https://github.com/pytest-dev/pytest/issues/6951&gt;`_: Allow users to still set the deprecated ``TerminalReporter.writer`` attribute.


- `6992 &lt;https://github.com/pytest-dev/pytest/issues/6992&gt;`_: Revert &quot;tmpdir: clean up indirection via config for factories&quot; #6767 as it breaks pytest-xdist.


- `7110 &lt;https://github.com/pytest-dev/pytest/issues/7110&gt;`_: Fixed regression: ``asyncbase.TestCase`` tests are executed correctly again.


- `7143 &lt;https://github.com/pytest-dev/pytest/issues/7143&gt;`_: Fix ``File.from_parent`` so it forwards extra keyword arguments to the constructor.


- `7145 &lt;https://github.com/pytest-dev/pytest/issues/7145&gt;`_: Classes with broken ``__getattribute__`` methods are displayed correctly during failures.


- `7180 &lt;https://github.com/pytest-dev/pytest/issues/7180&gt;`_: Fix ``_is_setup_py`` for files encoded differently than locale.
   ```
   
  
  
   ### 5.4.1
   ```
   =========================

Bug Fixes
---------

- `6909 &lt;https://github.com/pytest-dev/pytest/issues/6909&gt;`_: Revert the change introduced by `#6330 &lt;https://github.com/pytest-dev/pytest/pull/6330&gt;`_, which required all arguments to ``pytest.mark.parametrize`` to be explicitly defined in the function signature.

  The intention of the original change was to remove what was expected to be an unintended/surprising behavior, but it turns out many people relied on it, so the restriction has been reverted.


- `6910 &lt;https://github.com/pytest-dev/pytest/issues/6910&gt;`_: Fix crash when plugins return an unknown stats while using the ``--reportlog`` option.
   ```
   
  
  
   ### 5.4.0
   ```
   =========================

Breaking Changes
----------------

- `6316 &lt;https://github.com/pytest-dev/pytest/issues/6316&gt;`_: Matching of ``-k EXPRESSION`` to test names is now case-insensitive.


- `6443 &lt;https://github.com/pytest-dev/pytest/issues/6443&gt;`_: Plugins specified with ``-p`` are now loaded after internal plugins, which results in their hooks being called *before* the internal ones.

  This makes the ``-p`` behavior consistent with ``PYTEST_PLUGINS``.


- `6637 &lt;https://github.com/pytest-dev/pytest/issues/6637&gt;`_: Removed the long-deprecated ``pytest_itemstart`` hook.

  This hook has been marked as deprecated and not been even called by pytest for over 10 years now.


- `6673 &lt;https://github.com/pytest-dev/pytest/issues/6673&gt;`_: Reversed / fix meaning of &quot;+/-&quot; in error diffs.  &quot;-&quot; means that sth. expected is missing in the result and &quot;+&quot; means that there are unexpected extras in the result.


- `6737 &lt;https://github.com/pytest-dev/pytest/issues/6737&gt;`_: The ``cached_result`` attribute of ``FixtureDef`` is now set to ``None`` when
  the result is unavailable, instead of being deleted.

  If your plugin performs checks like ``hasattr(fixturedef, &#39;cached_result&#39;)``,
  for example in a ``pytest_fixture_post_finalizer`` hook implementation, replace
  it with ``fixturedef.cached_result is not None``. If you ``del`` the attribute,
  set it to ``None`` instead.



Deprecations
------------

- `3238 &lt;https://github.com/pytest-dev/pytest/issues/3238&gt;`_: Option ``--no-print-logs`` is deprecated and meant to be removed in a future release. If you use ``--no-print-logs``, please try out ``--show-capture`` and
  provide feedback.

  ``--show-capture`` command-line option was added in ``pytest 3.5.0`` and allows to specify how to
  display captured output when tests fail: ``no``, ``stdout``, ``stderr``, ``log`` or ``all`` (the default).


- `571 &lt;https://github.com/pytest-dev/pytest/issues/571&gt;`_: Deprecate the unused/broken `pytest_collect_directory` hook.
  It was misaligned since the removal of the ``Directory`` collector in 2010
  and incorrect/unusable as soon as collection was split from test execution.


- `5975 &lt;https://github.com/pytest-dev/pytest/issues/5975&gt;`_: Deprecate using direct constructors for ``Nodes``.

  Instead they are now constructed via ``Node.from_parent``.

  This transitional mechanism enables us to untangle the very intensely
  entangled ``Node`` relationships by enforcing more controlled creation/configuration patterns.

  As part of this change, session/config are already disallowed parameters and as we work on the details we might need disallow a few more as well.

  Subclasses are expected to use `super().from_parent` if they intend to expand the creation of `Nodes`.


- `6779 &lt;https://github.com/pytest-dev/pytest/issues/6779&gt;`_: The ``TerminalReporter.writer`` attribute has been deprecated and should no longer be used. This
  was inadvertently exposed as part of the public API of that plugin and ties it too much
  with ``py.io.TerminalWriter``.



Features
--------

- `4597 &lt;https://github.com/pytest-dev/pytest/issues/4597&gt;`_: New :ref:`--capture=tee-sys &lt;capture-method&gt;` option to allow both live printing and capturing of test output.


- `5712 &lt;https://github.com/pytest-dev/pytest/issues/5712&gt;`_: Now all arguments to ``pytest.mark.parametrize`` need to be explicitly declared in the function signature or via ``indirect``.
  Previously it was possible to omit an argument if a fixture with the same name existed, which was just an accident of implementation and was not meant to be a part of the API.


- `6454 &lt;https://github.com/pytest-dev/pytest/issues/6454&gt;`_: Changed default for `-r` to `fE`, which displays failures and errors in the :ref:`short test summary &lt;pytest.detailed_failed_tests_usage&gt;`.  `-rN` can be used to disable it (the old behavior).


- `6469 &lt;https://github.com/pytest-dev/pytest/issues/6469&gt;`_: New options have been added to the :confval:`junit_logging` option: ``log``, ``out-err``, and ``all``.


- `6834 &lt;https://github.com/pytest-dev/pytest/issues/6834&gt;`_: Excess warning summaries are now collapsed per file to ensure readable display of warning summaries.



Improvements
------------

- `1857 &lt;https://github.com/pytest-dev/pytest/issues/1857&gt;`_: ``pytest.mark.parametrize`` accepts integers for ``ids`` again, converting it to strings.


- `449 &lt;https://github.com/pytest-dev/pytest/issues/449&gt;`_: Use &quot;yellow&quot; main color with any XPASSED tests.


- `4639 &lt;https://github.com/pytest-dev/pytest/issues/4639&gt;`_: Revert &quot;A warning is now issued when assertions are made for ``None``&quot;.

  The warning proved to be less useful than initially expected and had quite a
  few false positive cases.


- `5686 &lt;https://github.com/pytest-dev/pytest/issues/5686&gt;`_: ``tmpdir_factory.mktemp`` now fails when given absolute and non-normalized paths.


- `5984 &lt;https://github.com/pytest-dev/pytest/issues/5984&gt;`_: The ``pytest_warning_captured`` hook now receives a ``location`` parameter with the code location that generated the warning.


- `6213 &lt;https://github.com/pytest-dev/pytest/issues/6213&gt;`_: pytester: the ``testdir`` fixture respects environment settings from the ``monkeypatch`` fixture for inner runs.


- `6247 &lt;https://github.com/pytest-dev/pytest/issues/6247&gt;`_: ``--fulltrace`` is honored with collection errors.


- `6384 &lt;https://github.com/pytest-dev/pytest/issues/6384&gt;`_: Make `--showlocals` work also with `--tb=short`.


- `6653 &lt;https://github.com/pytest-dev/pytest/issues/6653&gt;`_: Add support for matching lines consecutively with :attr:`LineMatcher &lt;_pytest.pytester.LineMatcher&gt;`&#39;s :func:`~_pytest.pytester.LineMatcher.fnmatch_lines` and :func:`~_pytest.pytester.LineMatcher.re_match_lines`.


- `6658 &lt;https://github.com/pytest-dev/pytest/issues/6658&gt;`_: Code is now highlighted in tracebacks when ``pygments`` is installed.

  Users are encouraged to install ``pygments`` into their environment and provide feedback, because
  the plan is to make ``pygments`` a regular dependency in the future.


- `6795 &lt;https://github.com/pytest-dev/pytest/issues/6795&gt;`_: Import usage error message with invalid `-o` option.


- `759 &lt;https://github.com/pytest-dev/pytest/issues/759&gt;`_: ``pytest.mark.parametrize`` supports iterators and generators for ``ids``.



Bug Fixes
---------

- `310 &lt;https://github.com/pytest-dev/pytest/issues/310&gt;`_: Add support for calling `pytest.xfail()` and `pytest.importorskip()` with doctests.


- `3823 &lt;https://github.com/pytest-dev/pytest/issues/3823&gt;`_: ``--trace`` now works with unittests.


- `4445 &lt;https://github.com/pytest-dev/pytest/issues/4445&gt;`_: Fixed some warning reports produced by pytest to point to the correct location of the warning in the user&#39;s code.


- `5301 &lt;https://github.com/pytest-dev/pytest/issues/5301&gt;`_: Fix ``--last-failed`` to collect new tests from files with known failures.


- `5928 &lt;https://github.com/pytest-dev/pytest/issues/5928&gt;`_: Report ``PytestUnknownMarkWarning`` at the level of the user&#39;s code, not ``pytest``&#39;s.


- `5991 &lt;https://github.com/pytest-dev/pytest/issues/5991&gt;`_: Fix interaction with ``--pdb`` and unittests: do not use unittest&#39;s ``TestCase.debug()``.


- `6334 &lt;https://github.com/pytest-dev/pytest/issues/6334&gt;`_: Fix summary entries appearing twice when ``f/F`` and ``s/S`` report chars were used at the same time in the ``-r`` command-line option (for example ``-rFf``).

  The upper case variants were never documented and the preferred form should be the lower case.


- `6409 &lt;https://github.com/pytest-dev/pytest/issues/6409&gt;`_: Fallback to green (instead of yellow) for non-last items without previous passes with colored terminal progress indicator.


- `6454 &lt;https://github.com/pytest-dev/pytest/issues/6454&gt;`_: `--disable-warnings` is honored with `-ra` and `-rA`.


- `6497 &lt;https://github.com/pytest-dev/pytest/issues/6497&gt;`_: Fix bug in the comparison of request key with cached key in fixture.

  A construct ``if key == cached_key:`` can fail either because ``==`` is explicitly disallowed, or for, e.g., NumPy arrays, where the result of ``a == b`` cannot generally be converted to `bool`.
  The implemented fix replaces `==` with ``is``.


- `6557 &lt;https://github.com/pytest-dev/pytest/issues/6557&gt;`_: Make capture output streams ``.write()`` method return the same return value from original streams.


- `6566 &lt;https://github.com/pytest-dev/pytest/issues/6566&gt;`_: Fix ``EncodedFile.writelines`` to call the underlying buffer&#39;s ``writelines`` method.


- `6575 &lt;https://github.com/pytest-dev/pytest/issues/6575&gt;`_: Fix internal crash when ``faulthandler`` starts initialized
  (for example with ``PYTHONFAULTHANDLER=1`` environment variable set) and ``faulthandler_timeout`` defined
  in the configuration file.


- `6597 &lt;https://github.com/pytest-dev/pytest/issues/6597&gt;`_: Fix node ids which contain a parametrized empty-string variable.


- `6646 &lt;https://github.com/pytest-dev/pytest/issues/6646&gt;`_: Assertion rewriting hooks are (re)stored for the current item, which fixes them being still used after e.g. pytester&#39;s :func:`testdir.runpytest &lt;_pytest.pytester.Testdir.runpytest&gt;` etc.


- `6660 &lt;https://github.com/pytest-dev/pytest/issues/6660&gt;`_: :py:func:`pytest.exit` is handled when emitted from the :func:`pytest_sessionfinish &lt;_pytest.hookspec.pytest_sessionfinish&gt;` hook.  This includes quitting from a debugger.


- `6752 &lt;https://github.com/pytest-dev/pytest/issues/6752&gt;`_: When :py:func:`pytest.raises` is used as a function (as opposed to a context manager),
  a `match` keyword argument is now passed through to the tested function. Previously
  it was swallowed and ignored (regression in pytest 5.1.0).


- `6801 &lt;https://github.com/pytest-dev/pytest/issues/6801&gt;`_: Do not display empty lines inbetween traceback for unexpected exceptions with doctests.


- `6802 &lt;https://github.com/pytest-dev/pytest/issues/6802&gt;`_: The :fixture:`testdir fixture &lt;testdir&gt;` works within doctests now.



Improved Documentation
----------------------

- `6696 &lt;https://github.com/pytest-dev/pytest/issues/6696&gt;`_: Add list of fixtures to start of fixture chapter.


- `6742 &lt;https://github.com/pytest-dev/pytest/issues/6742&gt;`_: Expand first sentence on fixtures into a paragraph.



Trivial/Internal Changes
------------------------

- `6404 &lt;https://github.com/pytest-dev/pytest/issues/6404&gt;`_: Remove usage of ``parser`` module, deprecated in Python 3.9.
   ```
   
  
  
   ### 5.3.5
   ```
   =========================

Bug Fixes
---------

- `6517 &lt;https://github.com/pytest-dev/pytest/issues/6517&gt;`_: Fix regression in pytest 5.3.4 causing an INTERNALERROR due to a wrong assertion.
   ```
   
  
  
   ### 5.3.4
   ```
   =========================

Bug Fixes
---------

- `6496 &lt;https://github.com/pytest-dev/pytest/issues/6496&gt;`_: Revert `#6436 &lt;https://github.com/pytest-dev/pytest/issues/6436&gt;`__: unfortunately this change has caused a number of regressions in many suites,
  so the team decided to revert this change and make a new release while we continue to look for a solution.
   ```
   
  
  
   ### 5.3.3
   ```
   =========================

Bug Fixes
---------

- `2780 &lt;https://github.com/pytest-dev/pytest/issues/2780&gt;`_: Captured output during teardown is shown with ``-rP``.


- `5971 &lt;https://github.com/pytest-dev/pytest/issues/5971&gt;`_: Fix a ``pytest-xdist`` crash when dealing with exceptions raised in subprocesses created by the
  ``multiprocessing`` module.


- `6436 &lt;https://github.com/pytest-dev/pytest/issues/6436&gt;`_: :class:`FixtureDef &lt;_pytest.fixtures.FixtureDef&gt;` objects now properly register their finalizers with autouse and
  parameterized fixtures that execute before them in the fixture stack so they are torn
  down at the right times, and in the right order.


- `6532 &lt;https://github.com/pytest-dev/pytest/issues/6532&gt;`_: Fix parsing of outcomes containing multiple errors with ``testdir`` results (regression in 5.3.0).



Trivial/Internal Changes
------------------------

- `6350 &lt;https://github.com/pytest-dev/pytest/issues/6350&gt;`_: Optimized automatic renaming of test parameter IDs.
   ```
   
  
  
   ### 5.3.2
   ```
   =========================

Improvements
------------

- `4639 &lt;https://github.com/pytest-dev/pytest/issues/4639&gt;`_: Revert &quot;A warning is now issued when assertions are made for ``None``&quot;.

  The warning proved to be less useful than initially expected and had quite a
  few false positive cases.



Bug Fixes
---------

- `5430 &lt;https://github.com/pytest-dev/pytest/issues/5430&gt;`_: junitxml: Logs for failed test are now passed to junit report in case the test fails during call phase.


- `6290 &lt;https://github.com/pytest-dev/pytest/issues/6290&gt;`_: The supporting files in the ``.pytest_cache`` directory are kept with ``--cache-clear``, which only clears cached values now.


- `6301 &lt;https://github.com/pytest-dev/pytest/issues/6301&gt;`_: Fix assertion rewriting for egg-based distributions and ``editable`` installs (``pip install --editable``).
   ```
   
  
  
   ### 5.3.1
   ```
   =========================

Improvements
------------

- `6231 &lt;https://github.com/pytest-dev/pytest/issues/6231&gt;`_: Improve check for misspelling of :ref:`pytest.mark.parametrize ref`.


- `6257 &lt;https://github.com/pytest-dev/pytest/issues/6257&gt;`_: Handle :py:func:`pytest.exit` being use…
bors bot added a commit to aragilar/spaceplot that referenced this issue Aug 6, 2021