search

matiskay / html-similarity

Compare html similarity using structural and style metrics
BSD 3-Clause "New" or "Revised" License
210 stars 23 forks source link

Bump pytest from 4.6.2 to 5.1.1 #60

Closed dependabot-preview[bot] closed 5 years ago

dependabot-preview[bot] commented 5 years ago

Bumps pytest from 4.6.2 to 5.1.1.

Release notes *Sourced from [pytest's releases](https://github.com/pytest-dev/pytest/releases).* > ## 5.1.1 > pytest 5.1.1 (2019-08-20) > ========================= > > Bug Fixes > --------- > > - [\#5751](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5751): Fixed > `TypeError` when importing pytest on Python 3.5.0 and 3.5.1. > > ## 5.1.0 > pytest 5.1.0 (2019-08-15) > ========================= > > Removals > -------- > > - [\#5180](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5180): As per > our policy, the following features have been deprecated in the 4.X > series and are now removed: > > - `Request.getfuncargvalue`: use `Request.getfixturevalue` > instead. > - `pytest.raises` and `pytest.warns` no longer support strings as > the second argument. > - `message` parameter of `pytest.raises`. > - `pytest.raises`, `pytest.warns` and `ParameterSet.param` now use > native keyword-only syntax. This might change the exception > message from previous versions, but they still raise `TypeError` > on unknown keyword arguments as before. > - `pytest.config` global variable. > - `tmpdir_factory.ensuretemp` method. > - `pytest_logwarning` hook. > - `RemovedInPytest4Warning` warning type. > - `request` is now a reserved name for fixtures. > > For more information consult [Deprecations and > Removals](https://docs.pytest.org/en/latest/deprecations.html) in > the docs. > > - [\#5565](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5565): Removed > unused support code for > [unittest2](https://pypi.org/project/unittest2/). > > The `unittest2` backport module is no longer necessary since Python > 3.3+, and the small amount of code in pytest to support it also > doesn\'t seem to be used: after removed, all tests still pass > unchanged. > > Although our policy is to introduce a deprecation period before > ... (truncated)
Changelog *Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 5.1.1 (2019-08-20) > ========================= > > Bug Fixes > --------- > > - [\#5751](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5751): Fixed `TypeError` when importing pytest on Python 3.5.0 and 3.5.1. > > pytest 5.1.0 (2019-08-15) > ========================= > > Removals > -------- > > - [\#5180](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5180): As per our policy, the following features have been deprecated in the 4.X series and are now removed: > > - `Request.getfuncargvalue`: use `Request.getfixturevalue` instead. > - `pytest.raises` and `pytest.warns` no longer support strings as the second argument. > - `message` parameter of `pytest.raises`. > - `pytest.raises`, `pytest.warns` and `ParameterSet.param` now use native keyword-only syntax. This might change the exception message from previous versions, but they still raise `TypeError` on unknown keyword arguments as before. > - `pytest.config` global variable. > - `tmpdir_factory.ensuretemp` method. > - `pytest_logwarning` hook. > - `RemovedInPytest4Warning` warning type. > - `request` is now a reserved name for fixtures. > > For more information consult [Deprecations and Removals](https://docs.pytest.org/en/latest/deprecations.html) in the docs. > > - [\#5565](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5565): Removed unused support code for [unittest2](https://pypi.org/project/unittest2/). > > The `unittest2` backport module is no longer necessary since Python 3.3+, and the small amount of code in pytest to support it also doesn't seem to be used: after removed, all tests still pass unchanged. > > Although our policy is to introduce a deprecation period before removing any features or support for third party libraries, because this code is apparently not used at all (even if `unittest2` is used by a test suite executed by pytest), it was decided to remove it in this release. > > If you experience a regression because of this, please [file an issue](https://github.com/pytest-dev/pytest/issues/new). > > - [\#5615](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5615): `pytest.fail`, `pytest.xfail` and `pytest.skip` no longer support bytes for the message argument. > > This was supported for Python 2 where it was tempting to use `"message"` instead of `u"message"`. > > Python 3 code is unlikely to pass `bytes` to these functions. If you do, please decode it to an `str` beforehand. > > Features > -------- > > - [\#5564](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5564): New `Config.invocation_args` attribute containing the unchanged arguments passed to `pytest.main()`. > - [\#5576](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5576): New [NUMBER](https://docs.pytest.org/en/latest/doctest.html#using-doctest-options) option for doctests to ignore irrelevant differences in floating-point numbers. Inspired by Sébastien Boisgérault's [numtest](https://github.com/boisgera/numtest) extension for doctest. > > Improvements > ------------ > ... (truncated)
Commits - [`b135f5a`](https://github.com/pytest-dev/pytest/commit/b135f5af8d9b3a2a3904a55ec51b55db737c97d1) Preparing release version 5.1.1 - [`daff906`](https://github.com/pytest-dev/pytest/commit/daff9066c0c4ed1108a391fe3efcf6df5ab905ca) Merge pull request [#5752](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5752) from bluetech/typing-py350-fix - [`43eab91`](https://github.com/pytest-dev/pytest/commit/43eab917a1d174808f1975364f64214f98b094a8) Fix coverage - [`0e569fa`](https://github.com/pytest-dev/pytest/commit/0e569faca2802be124cd1a6b6690a35a464fb0a8) Merge pull request [#5769](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5769) from The-Compiler/remove-training - [`a7c2357`](https://github.com/pytest-dev/pytest/commit/a7c235732a10ac94f5c0881de49419d234fe2caf) Pypy doesn't have sys.getrefcount(), so go back to gc - [`cec2183`](https://github.com/pytest-dev/pytest/commit/cec2183aebe8106f740b2891422d5818dd01a399) Add workaround for test_raises_cyclic_reference in Python 3.5.{0,1} - [`c049fd8`](https://github.com/pytest-dev/pytest/commit/c049fd85abae2c03a83e4cddad824fb6a12c3b40) Remove cancelled training - [`a7ede64`](https://github.com/pytest-dev/pytest/commit/a7ede64f4262d1acbc4d50442d980f54631a14c7) Move `@overload` to compat - [`3076522`](https://github.com/pytest-dev/pytest/commit/307652202c7fa83369f5abfd822a408d4cc32d14) Merge pull request [#5762](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5762) from pytest-dev/hugovk-patch-1 - [`a287aea`](https://github.com/pytest-dev/pytest/commit/a287aea00e5939f96797dbc2731b3cf0279ebb03) Docs: update tense - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/4.6.2...5.1.1)


Dependabot compatibility score

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 commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.
dependabot-preview[bot] commented 5 years ago

Superseded by #61.