belbio / bel_resources

BEL resources and tools for namespaces, annotations, orthologs, taxonomy, etc and tool
https://bel-resources.rtfd.io
Apache License 2.0
2 stars 0 forks source link

Bump pytest from 3.5.1 to 3.6.0 #74

Closed dependabot-preview[bot] closed 6 years ago

dependabot-preview[bot] commented 6 years ago

Bumps pytest from 3.5.1 to 3.6.0.

Changelog *Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > Pytest 3.6.0 (2018-05-23) > ========================= > > Features > -------- > > - Revamp the internals of the ``pytest.mark`` implementation with correct per > node handling which fixes a number of long standing bugs caused by the old > design. This introduces new ``Node.iter_markers(name)`` and > ``Node.get_closest_mark(name)`` APIs. Users are **strongly encouraged** to > read the `reasons for the revamp in the docs > `_, > or jump over to details about `updating existing code to use the new APIs > `_. (`#3317 > `_) > > - Now when ``[**pytest**](https://github.com/pytest).fixture`` is applied more than once to the same function a > ``ValueError`` is raised. This buggy behavior would cause surprising problems > and if was working for a test suite it was mostly by accident. (`#2334 > `_) > > - Support for Python 3.7's builtin ``breakpoint()`` method, see `Using the > builtin breakpoint function > `_ for > details. (`#3180 `_) > > - ``monkeypatch`` now supports a ``context()`` function which acts as a context > manager which undoes all patching done within the ``with`` block. (`#3290 > `_) > > - The ``--pdb`` option now causes KeyboardInterrupt to enter the debugger, > instead of stopping the test session. On python 2.7, hitting CTRL+C again > exits the debugger. On python 3.2 and higher, use CTRL+D. (`#3299 > `_) > > - pytest not longer changes the log level of the root logger when the > ``log-level`` parameter has greater numeric value than that of the level of > the root logger, which makes it play better with custom logging configuration > in user code. (`#3307 `_) > > > Bug Fixes > --------- > > - A rare race-condition which might result in corrupted ``.pyc`` files on > Windows has been hopefully solved. (`#3008 > `_) > > - Also use iter_marker for discovering the marks applying for marker > expressions from the cli to avoid the bad data from the legacy mark storage. > ... (truncated)
Commits - [`45e7703`](https://github.com/pytest-dev/pytest/commit/45e77031336b11a64756d745b1aba46301b32f27) Move mark revamp note to the top of the CHANGELOG - [`d70e910`](https://github.com/pytest-dev/pytest/commit/d70e910b65d1a33bfc179248e024b766c7fc30fa) Preparing release version 3.6.0 - [`c55db1f`](https://github.com/pytest-dev/pytest/commit/c55db1faac4401bc055f75245b82f87c102da51a) Merge remote-tracking branch 'upstream/master' into release-3.6.0 - [`16583a6`](https://github.com/pytest-dev/pytest/commit/16583a6d43ed542bdfd4b67d83b52dff467386d8) Add missing libs to tasks/requirements.txt - [`7985eff`](https://github.com/pytest-dev/pytest/commit/7985eff5b4b824576c0a1a98ddf31cbce14498ef) Merge pull request [#3497](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3497) from hroncok/approx_compat_import - [`5072226`](https://github.com/pytest-dev/pytest/commit/5072226f69ce7bb2fedd091d3e84cb40fac390ec) Import Mapping and Sequence from compat in python_api::approx - [`6c8d46d`](https://github.com/pytest-dev/pytest/commit/6c8d46d8ea2341ef20362d8f46665f7e563b9821) Merge pull request [#3487](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3487) from tgoodlet/detect_pytest_hook_prefix - [`7d0c983`](https://github.com/pytest-dev/pytest/commit/7d0c9837ce4c3411ad8b5d82ee2ce6b1eebeaf28) Merge pull request [#3459](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3459) from RonnyPfannschmidt/mark-iter-name-filter - [`8e17e32`](https://github.com/pytest-dev/pytest/commit/8e17e322535b36d01cf6ba1199f8a812858062c1) Merge pull request [#3492](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3492) from timhughes/patch-1 - [`f0b8553`](https://github.com/pytest-dev/pytest/commit/f0b855369c5d5163e64f88e8ea3172cfa38de5c8) fix typo - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/3.5.1...3.6.0)


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 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 (this|these) label[s]` will set the current labels as the default for future PRs for this repo and language - `@dependabot use (this|these) reviewer[s]` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use (this|these) assignee[s]` will set the current assignees as the default for future PRs for this repo and language 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 commented 6 years ago

CLA assistant check
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.