Bump pytest from 3.8.2 to 3.9.1

[dependabot-preview[bot]]

Bumps pytest from 3.8.2 to 3.9.1.

Changelog

*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 3.9.1 (2018-10-16) > ========================= > > Features > -------- > > - `#4159 `_: For test-suites containing test classes, the information about the subclassed > module is now output only if a higher verbosity level is specified (at least > "-vv"). > > > pytest 3.9.0 (2018-10-15 - not published due to a release automation bug) > ========================================================================= > > Deprecations > ------------ > > - `#3616 `_: The following accesses have been documented as deprecated for years, but are now actually emitting deprecation warnings. > > * Access of ``Module``, ``Function``, ``Class``, ``Instance``, ``File`` and ``Item`` through ``Node`` instances. Now > users will this warning:: > > usage of Function.Module is deprecated, please use pytest.Module instead > > Users should just ``import pytest`` and access those objects using the ``pytest`` module. > > * ``request.cached_setup``, this was the precursor of the setup/teardown mechanism available to fixtures. You can > consult `funcarg comparison section in the docs `_. > > * Using objects named ``"Class"`` as a way to customize the type of nodes that are collected in ``Collector`` > subclasses has been deprecated. Users instead should use ``pytest_collect_make_item`` to customize node types during > collection. > > This issue should affect only advanced plugins who create new collection types, so if you see this warning > message please contact the authors so they can change the code. > > * The warning that produces the message below has changed to ``RemovedInPytest4Warning``:: > > getfuncargvalue is deprecated, use getfixturevalue > > > - `#3988 `_: Add a Deprecation warning for pytest.ensuretemp as it was deprecated since a while. > > > > Features > -------- > > - `#2293 `_: Improve usage errors messages by hiding internal details which can be distracting and noisy. > > ... (truncated)

Commits

- [`c5bbf8a`](https://github.com/pytest-dev/pytest/commit/c5bbf8ac73a78fd15016296e808d13f2a2a983f1) make note about the unpublished 3.9.0 release - [`253c578`](https://github.com/pytest-dev/pytest/commit/253c5786af681604f4e0c2b315f17fa5bcc950c2) Preparing release version 3.9.1 - [`c4550bc`](https://github.com/pytest-dev/pytest/commit/c4550bc922b6d44cb68b6577320888f9028096b4) Merge branch 'release-3.9.0' of github.com:nicoddemus/pytest into release-3.9.1 - [`2c00f8a`](https://github.com/pytest-dev/pytest/commit/2c00f8aad1ae71b31d7dfa6f57953b2ebdd48930) Merge pull request [#4170](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4170) from RonnyPfannschmidt/fix-metadata-url-quotes - [`456715a`](https://github.com/pytest-dev/pytest/commit/456715a5c1b4e573cb87b9864c1ca83616944395) fix url quotes in setup.cfg metadata - [`54b8ad4`](https://github.com/pytest-dev/pytest/commit/54b8ad4554509b191d3c5e7d53ecafe235652b87) Merge pull request [#4159](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4159) from thisch/subclassedfile - [`2868c31`](https://github.com/pytest-dev/pytest/commit/2868c314953e3a2cf2c753ebb87710d65c906cfa) Preparing release version 3.9.0 - [`39a13d7`](https://github.com/pytest-dev/pytest/commit/39a13d70647ae8c7a984209a3424b5b4052efa4f) Fix tmp_path example in docs - [`e4e4fd1`](https://github.com/pytest-dev/pytest/commit/e4e4fd1e521c3a6235adedb179915c9c74bd08d4) Merge pull request [#4158](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4158) from nicoddemus/merge-master-into-features - [`e8c220b`](https://github.com/pytest-dev/pytest/commit/e8c220b9bd31924aa94f0410d3a6f0c50e9ab18d) Increase required verbosity level for debug output - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/3.8.2...3.9.1)

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.

If all status checks pass Dependabot will automatically merge this pull request.

---

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.