Bump coverage from 5.2 to 5.3 in /python

[dependabot-preview]

Bumps coverage from 5.2 to 5.3.

Release notes

Sourced from coverage's releases.

coverage-5.3

• The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268.
• If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011. This is now fixed.

coverage-5.2.1

• The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009). This is now fixed.
• The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960).

Changelog

Sourced from coverage's changelog.

Version 5.3 --- 2020-09-13

• The source setting has always been interpreted as either a file path or a module, depending on which existed. If both interpretations were valid, it was assumed to be a file path. The new source_pkgs setting can be used to name a package to disambiguate this case. Thanks, Thomas Grainger. Fixes issue 268.
• If a plugin was disabled due to an exception, we used to still try to record its information, causing an exception, as reported in issue 1011. This is now fixed.

Version 5.2.1 --- 2020-07-23

• The dark mode HTML report still used light colors for the context listing, making them unreadable (issue 1009). This is now fixed.
• The time stamp on the HTML report now includes the time zone. Thanks, Xie Yanbo (pull request 960).

Commits

• d13594e Making a release
• 039ef09 If a plugin is disabled, don't try to record its file tracers. #1011
• 24eb6fd Move disable_plugin to Python
• 987ceb9 Fix a missed exception handling for bad plugins
• c907b2e ambigious -> ambiguous
• 263f3e1 Docs and cleanup for source_pkgs
• ecd6ab1 Create Way to force package even if filepath exists (#1026)
• 39e6d1d Thomas Grainger's first commit
• 154f528 replace confusing comment with assertion (#1028)
• c315908 Explain a mystery
• Additional commits viewable in compare view

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 close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor 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 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 the .dependabot/config.yml file in this repo:

• Update frequency
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[seldondev]

Hi @dependabot-preview[bot]. Thanks for your PR.

I'm waiting for a SeldonIO member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

[adriangonz]

/ok-to-test

[seldondev]

Mon Sep 14 07:55:48 UTC 2020
The logs for [pr-build] [1] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2419/1.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2419 --build=1

[seldondev]

Mon Sep 14 07:55:57 UTC 2020
The logs for [lint] [2] will show after the pipeline context has finished.
https://github.com/SeldonIO/seldon-core/blob/gh-pages/jenkins-x/logs/SeldonIO/seldon-core/PR-2419/2.log

impatient try
jx get build logs SeldonIO/seldon-core/PR-2419 --build=2

[adriangonz]

/approve

[seldondev]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adriangonz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [adriangonz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment