dependabot-preview[bot]
commented
4 years ago OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
Bumps pytest from 3.3.2 to 5.3.0.
Release notes
*Sourced from [pytest's releases](https://github.com/pytest-dev/pytest/releases).* > ## 5.3.0 > pytest 5.3.0 (2019-11-19) > ========================= > > Deprecations > ------------ > > - [\#6179](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6179): The > default value of `junit_family` option will change to `xunit2` 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` option is given in the command line but > `junit_family` is not explicitly configured in `pytest.ini`. > > For more information, [see the > docs](https://docs.pytest.org/en/latest/deprecations.html#junit-family-default-value-change-to-xunit2). > > Features > -------- > > - [\#4488](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4488): The > pytest team has created the > [pytest-reportlog](https://github.com/pytest-dev/pytest-reportlog) > plugin, which provides a new `--report-log=FILE` option that writes > *report logs* into a file as the test session executes. > > Each line of the report log contains a self contained JSON object > corresponding to a testing event, such as a collection or a test > result report. The file is guaranteed to be flushed after writing > each line, so systems can read and process events in real-time. > > The plugin is meant to replace the `--resultlog` option, which is > deprecated and meant to be removed in a future release. If you use > `--resultlog`, please try out `pytest-reportlog` and > provide feedback. > > - [\#4730](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4730): When > `sys.pycache_prefix` (Python 3.8+) is set, it will be used by pytest > to cache test files changed by the assertion rewriting mechanism. > > This makes it easier to benefit of cached `.pyc` files even on file > systems without permissions. > > - [\#5515](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5515): Allow > selective auto-indentation of multiline log messages. > > Adds command line option `--log-auto-indent`, config option > `log_auto_indent` and support for per-entry configuration of > ... (truncated)Changelog
*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 5.3.0 (2019-11-19) > ========================= > > Deprecations > ------------ > > - [\#6179](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6179): The default value of `junit_family` option will change to `xunit2` 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` option is given in the command line but `junit_family` is not explicitly configured in `pytest.ini`. > > For more information, [see the docs](https://docs.pytest.org/en/latest/deprecations.html#junit-family-default-value-change-to-xunit2). > > Features > -------- > > - [\#4488](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4488): The pytest team has created the [pytest-reportlog](https://github.com/pytest-dev/pytest-reportlog) plugin, which provides a new `--report-log=FILE` option that writes *report logs* into a file as the test session executes. > > Each line of the report log contains a self contained JSON object corresponding to a testing event, such as a collection or a test result report. The file is guaranteed to be flushed after writing each line, so systems can read and process events in real-time. > > The plugin is meant to replace the `--resultlog` option, which is deprecated and meant to be removed in a future release. If you use `--resultlog`, please try out `pytest-reportlog` and provide feedback. > > - [\#4730](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4730): When `sys.pycache_prefix` (Python 3.8+) is set, it will be used by pytest to cache test files changed by the assertion rewriting mechanism. > > This makes it easier to benefit of cached `.pyc` files even on file systems without permissions. > > - [\#5515](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5515): Allow selective auto-indentation of multiline log messages. > > Adds command line option `--log-auto-indent`, config option `log_auto_indent` and support for per-entry configuration of indentation behavior on calls to `logging.log()`. > > Alters the default for auto-indention from `on` to `off`. This restores the older behavior that existed prior to v4.6.0. This reversion to earlier behavior was done because it is better to activate new features that may lead to broken tests explicitly rather than implicitly. > > - [\#5914](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5914): `pytester` learned two new functions, [no\_fnmatch\_line](https://docs.pytest.org/en/latest/reference.html#_pytest.pytester.LineMatcher.no_fnmatch_line) and [no\_re\_match\_line](https://docs.pytest.org/en/latest/reference.html#_pytest.pytester.LineMatcher.no_re_match_line). > > The functions are used to ensure the captured text *does not* match the given pattern. > > The previous idiom was to use `re.match`: > > ``` {.sourceCode .python} > assert re.match(pat, result.stdout.str()) is None > ``` > > Or the `in` operator: > > ``` {.sourceCode .python} > assert text in result.stdout.str() > ``` > > But the new functions produce best output on failure. > > - [\#6057](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6057): Added tolerances to complex values when printing `pytest.approx`. > ... (truncated)Commits
- [`be59827`](https://github.com/pytest-dev/pytest/commit/be59827216612fd416818702be7e2b8448f4089d) Small fixes in the CHANGELOG for 5.3.0 - [`4b16b93`](https://github.com/pytest-dev/pytest/commit/4b16b93cf57bb58d6dd55fb4b4ffa2a0a2a344db) Preparing release version 5.3.0 - [`21622d0`](https://github.com/pytest-dev/pytest/commit/21622d0df43609b84644134a4741343d147df1eb) Merge remote-tracking branch 'upstream/master' into release-5.3.0 - [`d1e2d12`](https://github.com/pytest-dev/pytest/commit/d1e2d12b3feae7366b57b878f88a8b772817820e) python: remove unused pytest_make_parametrize_id hookimpl ([#6228](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6228)) - [`f36ea24`](https://github.com/pytest-dev/pytest/commit/f36ea240fe3579f945bf5d6cc41b5e45a572249d) Remove check for os.symlink, always there in py3+ ([#6227](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6227)) - [`4804d4b`](https://github.com/pytest-dev/pytest/commit/4804d4bc9824f7a6fb0153a25e896627dec37b3b) python: remove unused pytest_make_parametrize_id hookimpl - [`b820b7e`](https://github.com/pytest-dev/pytest/commit/b820b7e384a0e86ed0954bd79b89f4ff928e2837) Merge pull request [#6224](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6224) from blueyed/visit_Assert-minor-cleanup - [`8d3e8b1`](https://github.com/pytest-dev/pytest/commit/8d3e8b1c54ae5499e25101f5162cbe17f1cf7330) Revert "ci: use tox -vv" ([#6226](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6226)) - [`63a23d8`](https://github.com/pytest-dev/pytest/commit/63a23d876cad98d42f03cf6c6f397513e96ffcdb) Remove check for os.symlink, always there in py3+ - [`eeeb196`](https://github.com/pytest-dev/pytest/commit/eeeb19626b26072ff49735e221dc558363716b78) Merge pull request [#6202](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/6202) from linw1995/fix_getmodpath - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/3.3.2...5.3.0)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) - 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)