codecov-io
commented
5 years ago Codecov Report
Merging #8 into master will not change coverage. The diff coverage is
n/a.
@@ Coverage Diff @@
## master #8 +/- ##
=======================================
Coverage 70.21% 70.21%
=======================================
Files 2 2
Lines 47 47
Branches 3 3
=======================================
Hits 33 33
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 985c226...6e46ee2. Read the comment docs.
dependabot-preview[bot]
Bumps pytest from 4.6.3 to 5.0.1.
Changelog
*Sourced from [pytest's changelog](https://github.com/pytest-dev/pytest/blob/master/CHANGELOG.rst).* > pytest 5.0.1 (2019-07-04) > ========================= > > Bug Fixes > --------- > > - [\#5479](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5479): Improve quoting in `raises` match failure message. > - [\#5523](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5523): Fixed using multiple short options together in the command-line (for example `-vs`) in Python 3.8+. > - [\#5547](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5547): `--step-wise` now handles `xfail(strict=True)` markers properly. > > Improved Documentation > ---------------------- > > - [\#5517](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5517): Improve "Declaring new hooks" section in chapter "Writing Plugins" > > 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 > ... (truncated)Commits
- [`bb29f31`](https://github.com/pytest-dev/pytest/commit/bb29f31d2278fc93efba7ef3e123616c13ce8022) Preparing release version 5.0.1 - [`b1928f8`](https://github.com/pytest-dev/pytest/commit/b1928f878d33b912851391c32adb4c0b91fb70c0) Handle xfail(strict=True) properly in --step-wise mode ([#5555](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5555)) - [`8651d88`](https://github.com/pytest-dev/pytest/commit/8651d880a06c078d8c04ec8c99df1a05bc9826d7) Handle xfail(strict=True) properly in --step-wise mode - [`95824c5`](https://github.com/pytest-dev/pytest/commit/95824c588a333c54780e6ea82393488b6a6a81d4) Improve quoting in raises match failure message ([#5553](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5553)) - [`caa08eb`](https://github.com/pytest-dev/pytest/commit/caa08ebd4536bbabfb0e1edd3d438be911cfab51) Improve quoting in raises match failure message - [`b08ae44`](https://github.com/pytest-dev/pytest/commit/b08ae4449b6ab0e70296cc11fc3f1f0ad0e97255) Add docs about Tidelift and OpenCollective ([#5527](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5527)) - [`776a632`](https://github.com/pytest-dev/pytest/commit/776a632170d1bb3da0764f5277ec6c9ebb9d3781) Merge pull request [#5540](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5540) from bazcrown/yml2yaml - [`d74a975`](https://github.com/pytest-dev/pytest/commit/d74a975f8287e8ee1802aecbb449a47239b3e757) remove documentation about setuptools integration Refs [#5534](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5534) Fi… ([#5546](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5546)) - [`2b9522e`](https://github.com/pytest-dev/pytest/commit/2b9522e9da15107bf3a96083e0221ad6cce47bb6) remove documentation about setuptools integration Refs [#5534](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5534) - [`528ee3e`](https://github.com/pytest-dev/pytest/commit/528ee3e1c5b461c91948632aadd835ede83cc50b) Add upcoming trainings ([#5544](https://github-redirect.dependabot.com/pytest-dev/pytest/issues/5544)) - Additional commits viewable in [compare view](https://github.com/pytest-dev/pytest/compare/4.6.3...5.0.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.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). To ignore the version in this PR you can just close it - `@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.