Bump pytest from 3.9.3 to 4.0.0

[dependabot-preview[bot]]

Bumps pytest from 3.9.3 to 4.0.0.

Changelog

*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 4.0.0 (2018-11-13) > ========================= > > Removals > -------- > > - `#3737 `_: **RemovedInPytest4Warnings are now errors by default.** > > Following our plan to remove deprecated features with as little disruption as > possible, all warnings of type ``RemovedInPytest4Warnings`` now generate errors > instead of warning messages. > > **The affected features will be effectively removed in pytest 4.1**, so please consult the > `Deprecations and Removals `__ > section in the docs for directions on how to update existing code. > > In the pytest ``4.0.X`` series, it is possible to change the errors back into warnings as a stop > gap measure by adding this to your ``pytest.ini`` file: > > .. code-block:: ini > > [pytest] > filterwarnings = > ignore::pytest.RemovedInPytest4Warning > > But this will stop working when pytest ``4.1`` is released. > > **If you have concerns** about the removal of a specific feature, please add a > comment to `#4348 `__. > > > - `#4358 `_: Remove the ``::()`` notation to denote a test class instance in node ids. > > Previously, node ids that contain test instances would use ``::()`` to denote the instance like this:: > > test_foo.py::Test::()::test_bar > > The extra ``::()`` was puzzling to most users and has been removed, so that the test id becomes now:: > > test_foo.py::Test::test_bar > > This change could not accompany a deprecation period as is usual when user-facing functionality changes because > it was not really possible to detect when the functionality was being used explicitly. > > The extra ``::()`` might have been removed in some places internally already, > which then led to confusion in places where it was expected, e.g. with > ``--deselect`` (`#4127 `_). > > Test class instances are also not listed with ``--collect-only`` anymore. > > ... (truncated)

Commits

- [`c2d6b35`](https://github.com/pytest-dev/pytest/commit/c2d6b3524cc0039e152da52fe21eb375e63704cf) Preparing release version 4.0.0 - [`e025974`](https://github.com/pytest-dev/pytest/commit/e025974cbd4102e613a3833e35b8feefe4800d0d) Merge remote-tracking branch 'upstream/master' into release-4.0.0 - [`fea09cd`](https://github.com/pytest-dev/pytest/commit/fea09cda6c1db283835d2c72ad5c91831a02f844) Merge pull request [#4383](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4383) from nicoddemus/merge-master-into-features - [`b7863a5`](https://github.com/pytest-dev/pytest/commit/b7863a5f481b6a969832cd182681725fa9aedffd) Merge pull request [#4381](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4381) from blueyed/callinfo-repr - [`a72eff5`](https://github.com/pytest-dev/pytest/commit/a72eff5a08b637099aa040665381a638e1422ac4) Merge pull request [#4382](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4382) from blueyed/pytester-pop-TOX_ENV_DIR - [`46c8363`](https://github.com/pytest-dev/pytest/commit/46c8363e12e16933ebf1762ebd806fb506de8b13) Merge pull request [#4380](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4380) from blueyed/improve-ci - [`557cb6c`](https://github.com/pytest-dev/pytest/commit/557cb6cffe0dde3d11affa5da2286353417b6893) Merge remote-tracking branch 'upstream/master' into merge-master-into-features - [`8198e7c`](https://github.com/pytest-dev/pytest/commit/8198e7cd33d5ddb55231d3fab58511003dcdbaef) Merge pull request [#4349](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4349) from nicoddemus/pytest4-warnings-as-errors - [`a6a9646`](https://github.com/pytest-dev/pytest/commit/a6a96469ca25cc3e6066638679286ebe6cde82c1) pytester: pop TOX_ENV_DIR from os.environ - [`27dab4e`](https://github.com/pytest-dev/pytest/commit/27dab4e05f56a64b67e203400e52feb6d2663214) Fix CallInfo.__repr__ for unfinished call - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/3.9.3...4.0.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 cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major 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.