Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump pytest from 6.1.2 to 6.2.0 (#550)
Bumps [pytest](https://github.com/pytest-dev/pytest) from 6.1.2 to 6.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/pytest-dev/pytest/releases">pytest's releases</a>.</em></p> <blockquote> <h2>6.2.0</h2> <h1>pytest 6.2.0 (2020-12-12)</h1> <h2>Breaking Changes</h2> <ul> <li><a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/7808">#7808</a>: pytest now supports python3.6+ only.</li> </ul> <h2>Deprecations</h2> <ul> <li> <p><a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/7469">#7469</a>: Directly constructing/calling the following classes/functions is now deprecated:</p> <ul> <li><code>_pytest.cacheprovider.Cache</code></li> <li><code>_pytest.cacheprovider.Cache.for_config()</code></li> <li><code>_pytest.cacheprovider.Cache.clear_cache()</code></li> <li><code>_pytest.cacheprovider.Cache.cache_dir_from_config()</code></li> <li><code>_pytest.capture.CaptureFixture</code></li> <li><code>_pytest.fixtures.FixtureRequest</code></li> <li><code>_pytest.fixtures.SubRequest</code></li> <li><code>_pytest.logging.LogCaptureFixture</code></li> <li><code>_pytest.pytester.Pytester</code></li> <li><code>_pytest.pytester.Testdir</code></li> <li><code>_pytest.recwarn.WarningsRecorder</code></li> <li><code>_pytest.recwarn.WarningsChecker</code></li> <li><code>_pytest.tmpdir.TempPathFactory</code></li> <li><code>_pytest.tmpdir.TempdirFactory</code></li> </ul> <p>These have always been considered private, but now issue a deprecation warning, which may become a hard error in pytest 7.0.0.</p> </li> <li> <p><a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/7530">#7530</a>: The <code>--strict</code> command-line option has been deprecated, use <code>--strict-markers</code> instead.</p> <p>We have plans to maybe in the future to reintroduce <code>--strict</code> and make it an encompassing flag for all strictness related options (<code>--strict-markers</code> and <code>--strict-config</code> at the moment, more might be introduced in the future).</p> </li> <li> <p><a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/7988">#7988</a>: The <code>@pytest.yield_fixture</code> decorator/function is now deprecated. Use pytest.fixture instead.</p> <p><code>yield_fixture</code> has been an alias for <code>fixture</code> for a very long time, so can be search/replaced safely.</p> </li> </ul> <h2>Features</h2> <ul> <li> <p><a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5299">#5299</a>: pytest now warns about unraisable exceptions and unhandled thread exceptions that occur in tests on Python>=3.8. See unraisable for more information.</p> </li> <li> <p><a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/7425">#7425</a>: New pytester fixture, which is identical to testdir but its methods return pathlib.Path when appropriate instead of <code>py.path.local</code>.</p> <p>This is part of the movement to use pathlib.Path objects internally, in order to remove the dependency to <code>py</code> in the future.</p> <p>Internally, the old Testdir <_pytest.pytester.Testdir> is now a thin wrapper around Pytester <_pytest.pytester.Pytester>, preserving the old interface.</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/pytest-dev/pytest/commit/e7073afe6e2373175130511135020af8b4e3a670"><code>e7073af</code></a> Prepare release version 6.2.0</li> <li><a href="https://github.com/pytest-dev/pytest/commit/683f29f84df61e9dab92970a57190d20ca58385e"><code>683f29f</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/8129">#8129</a> from bluetech/docs-pygments-workaround</li> <li><a href="https://github.com/pytest-dev/pytest/commit/0feeddf8edb87052402fafe690d019e3eb75dfa4"><code>0feeddf</code></a> doc: temporary workaround for pytest-pygments lexing error</li> <li><a href="https://github.com/pytest-dev/pytest/commit/b4782757772373a2ea00802606407e9399b98031"><code>b478275</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/8128">#8128</a> from bluetech/skip-reason-empty</li> <li><a href="https://github.com/pytest-dev/pytest/commit/3302ff994959964c3ec2ab35ec1fe98c038684c0"><code>3302ff9</code></a> terminal: when the skip/xfail is empty, don't show it as "()"</li> <li><a href="https://github.com/pytest-dev/pytest/commit/59bd0f6912fd9ec2b4c3e3bbc989636bb5f54dbf"><code>59bd0f6</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/8126">#8126</a> from bluetech/tox-regen-pretend-scm2</li> <li><a href="https://github.com/pytest-dev/pytest/commit/6298ff1f4e21307627b59aa86437145ddcf2bafe"><code>6298ff1</code></a> tox: use pip legacy resolver for regen job</li> <li><a href="https://github.com/pytest-dev/pytest/commit/d51ecbd44d7e2f4f8c21f246fe9ed034bc8bae5b"><code>d51ecbd</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/8125">#8125</a> from bluetech/tox-rm-pip-req</li> <li><a href="https://github.com/pytest-dev/pytest/commit/f237b077fc83fe834589e619be1e898f28026eb2"><code>f237b07</code></a> tox: remove requires: pip>=20.3.1</li> <li><a href="https://github.com/pytest-dev/pytest/commit/95e0e19b8d5b55b0462d420af7454f3bdcbe7fbc"><code>95e0e19</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/pytest-dev/pytest/issues/8124">#8124</a> from bluetech/s0undt3ch-feature/skip-context-hook</li> <li>Additional commits viewable in <a href="https://github.com/pytest-dev/pytest/compare/6.1.2...6.2.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=pytest&package-manager=pip&previous-version=6.1.2&new-version=6.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end)
- Loading branch information