codecov-io
commented
5 years ago Codecov Report
Merging #7 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #7 +/- ##
=======================================
Coverage 68.88% 68.88%
=======================================
Files 2 2
Lines 45 45
Branches 3 3
=======================================
Hits 31 31
Misses 13 13
Partials 1 1Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact),ø = not affected,? = missing dataPowered by Codecov. Last update 84f14f5...97a9104. Read the comment docs.
dependabot-preview[bot]
Bumps pytest from 4.6.3 to 5.0.0.
Changelog
*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 5.0.0 (2019-06-28) > ========================= > > Important > --------- > > This release is a Python3.5+ only release. > > For more details, see our [Python 2.7 and 3.4 support plan](https://docs.pytest.org/en/latest/py27-py34-deprecation.html). > > Removals > -------- > > - [\#1149](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/1149): Pytest no longer accepts prefixes of command-line arguments, for example typing `pytest --doctest-mod` inplace of `--doctest-modules`. This was previously allowed where the `ArgumentParser` thought it was unambiguous, but this could be incorrect due to delayed parsing of options for plugins. See for example issues [\#1149](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/1149), [\#3413](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3413), and [\#4009](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4009). > - [\#5402](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5402): **PytestDeprecationWarning are now errors by default.** > > Following our plan to remove deprecated features with as little disruption as possible, all warnings of type `PytestDeprecationWarning` now generate errors instead of warning messages. > > **The affected features will be effectively removed in pytest 5.1**, so please consult the [Deprecations and Removals](https://docs.pytest.org/en/latest/deprecations.html) section in the docs for directions on how to update existing code. > > In the pytest `5.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: > > ``` {.sourceCode .ini} > [pytest] > filterwarnings = > ignore::pytest.PytestDeprecationWarning > ``` > > But this will stop working when pytest `5.1` is released. > > **If you have concerns** about the removal of a specific feature, please add a comment to [\#5402](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5402). > > - [\#5412](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5412): `ExceptionInfo` objects (returned by `pytest.raises`) now have the same `str` representation as `repr`, which avoids some confusion when users use `print(e)` to inspect the object. > > Deprecations > ------------ > > - [\#4488](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/4488): The removal of the `--result-log` option and module has been postponed to (tentatively) pytest 6.0 as the team has not yet got around to implement a good alternative for it. > - [\#466](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/466): The `funcargnames` attribute has been an alias for `fixturenames` since pytest 2.3, and is now deprecated in code too. > > Features > -------- > > - [\#3457](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/3457): New [pytest\_assertion\_pass](https://docs.pytest.org/en/latest/reference.html#_pytest.hookspec.pytest_assertion_pass) hook, called with context information when an assertion *passes*. > > This hook is still **experimental** so use it with caution. > > - [\#5440](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5440): The [faulthandler](https://docs.python.org/3/library/faulthandler.html) standard library module is now enabled by default to help users diagnose crashes in C modules. > > This functionality was provided by integrating the external [pytest-faulthandler](https://github.com/pytest-dev/pytest-faulthandler) plugin into the core, so users should remove that plugin from their requirements if used. > ... (truncated)Commits
- [`58bfc77`](https://github.com/pytest-dev/pytest/commit/58bfc7736fc4f88eca669157822e00715c67a9bf) Use shutil.which to avoid distutils+imp warning - [`97f0a20`](https://github.com/pytest-dev/pytest/commit/97f0a20ca9fe4e1acac7d3510441214a223f36ac) Add notice about py35+ and move ExitCode changelog entry - [`55d2fe0`](https://github.com/pytest-dev/pytest/commit/55d2fe076f6b5a4a3b90d2df829685580dc48937) Use importlib instead of imp in demo - [`5e39eb9`](https://github.com/pytest-dev/pytest/commit/5e39eb91bb6d7bdc11364ab741f1057d36fc17d5) Correct Zac-HD's name in changelogs - [`fd2f320`](https://github.com/pytest-dev/pytest/commit/fd2f32048554da04d60bae662a82ecd0fc8417e2) Preparing release version 5.0.0 - [`73d918d`](https://github.com/pytest-dev/pytest/commit/73d918db55e2f653e1025f0151debe01a88a2986) Remove astor and reproduce the original assertion expression ([#5512](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5512)) - [`7ee2444`](https://github.com/pytest-dev/pytest/commit/7ee244476a4ecc2b39f9bf21afea8ebf57077941) Remove astor and reproduce the original assertion expression - [`3c9b46f`](https://github.com/pytest-dev/pytest/commit/3c9b46f78198ace16e434a29b4150a520c3d222c) Remove stray comment from tox.ini ([#5507](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5507)) - [`f7bfbb5`](https://github.com/pytest-dev/pytest/commit/f7bfbb557e3429fb0f2579322f1a3203a4b48e61) Merge pull request [#5506](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5506) from asottile/fix_no_terminal - [`45af361`](https://github.com/pytest-dev/pytest/commit/45af361a677c7a03369e59959688a1d03c99c61a) Remove stray comment from tox.ini - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/4.6.3...5.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 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 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) - 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.