Bump pytest from 3.6.3 to 3.7.0

[dependabot-preview[bot]]

Bumps pytest from 3.6.3 to 3.7.0.

Changelog

*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 3.7.0 (2018-07-30) > ========================= > > Deprecations and Removals > ------------------------- > > - `#2639 `_: ``pytest_namespace`` has been deprecated. > > See the documentation for ``pytest_namespace`` hook for suggestions on how to deal > with this in plugins which use this functionality. > > > - `#3661 `_: Calling a fixture function directly, as opposed to request them in a test function, now issues a ``RemovedInPytest4Warning``. It will be changed into an error in pytest ``4.0``. > > This is a great source of confusion to new users, which will often call the fixture functions and request them from test functions interchangeably, which breaks the fixture resolution model. > > > > Features > -------- > > - `#2283 `_: New ``package`` fixture scope: fixtures are finalized when the last test of a *package* finishes. This feature is considered **experimental**, so use it sparingly. > > > - `#3576 `_: ``Node.add_marker`` now supports an ``append=True/False`` parameter to determine whether the mark comes last (default) or first. > > > - `#3579 `_: Fixture ``caplog`` now has a ``messages`` property, providing convenient access to the format-interpolated log messages without the extra data provided by the formatter/handler. > > > - `#3610 `_: New ``--trace`` option to enter the debugger at the start of a test. > > > - `#3623 `_: Introduce ``pytester.copy_example`` as helper to do acceptance tests against examples from the project. > > > > Bug Fixes > --------- > > - `#2220 `_: Fix a bug where fixtures overridden by direct parameters (for example parametrization) were being instantiated even if they were not being used by a test. > > > - `#3695 `_: Fix ``ApproxNumpy`` initialisation argument mixup, ``abs`` and ``rel`` tolerances were flipped causing strange comparsion results. > Add tests to check ``abs`` and ``rel`` tolerances for ``np.array`` and test for expecting ``nan`` with ``np.array()`` > > > - `#980 `_: Fix truncated locals output in verbose mode. > > > ... (truncated)

Commits

- [`997ef59`](https://github.com/pytest-dev/pytest/commit/997ef593068a36c283cbb83d938272b9770caa36) Fix typos in CHANGELOG - [`60b1913`](https://github.com/pytest-dev/pytest/commit/60b1913ba21094da5eb91d8c68642c38f20f6a26) Preparing release version 3.7.0 - [`2c09930`](https://github.com/pytest-dev/pytest/commit/2c09930b6d701d91a0284c6d44086488ffbcb419) Use proper quotes for python 3.7 on travis.yml - [`d461e93`](https://github.com/pytest-dev/pytest/commit/d461e931dd7fa7eae7b835cb84047e033872aade) Use python 3.6 for regendoc - [`eada0b1`](https://github.com/pytest-dev/pytest/commit/eada0b1fd7a892be9c8e32cac7b3af26b919056d) Merge remote-tracking branch 'upstream/master' into release-3.7.0 - [`150535b`](https://github.com/pytest-dev/pytest/commit/150535b6c11b16ad38299ea93246b5ad55ce013c) Merge pull request [#3696](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3696) from abrammer/approx_numpy_tolerance_bugfix - [`f1ec02c`](https://github.com/pytest-dev/pytest/commit/f1ec02cdcd6aa00d0eaf72d9bcfa862be9629118) Merge pull request [#3733](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3733) from nicoddemus/py37 - [`9f5d73d`](https://github.com/pytest-dev/pytest/commit/9f5d73d44afc165a0c0803913615f3ddd119d2b3) Merge pull request [#3735](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3735) from nicoddemus/deprecate-pytest-namespace - [`8609f8d`](https://github.com/pytest-dev/pytest/commit/8609f8d25a1f9a59df835bf51bdf86953c127f00) Move warning definition to deprecated module - [`953a618`](https://github.com/pytest-dev/pytest/commit/953a618102782daceb229af3b8788b71560b1f0d) Update CHANGELOG entry about pytest_namespace deprecation - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/3.6.3...3.7.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 merge` will merge this PR after your CI passes on it - `@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 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.

[CLAassistant]

Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dependabot-preview[bot]]

Superseded by #97.