All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leon Anavi" <leon.anavi@konsulko.com>
To: openembedded-devel@lists.openembedded.org
Cc: Leon Anavi <leon.anavi@konsulko.com>
Subject: [meta-python][PATCH 7/7] python3-coverage: Upgrade 5.1 -> 5.2
Date: Wed, 22 Jul 2020 13:49:05 +0300	[thread overview]
Message-ID: <20200722104905.15499-7-leon.anavi@konsulko.com> (raw)
In-Reply-To: <20200722104905.15499-1-leon.anavi@konsulko.com>

Upgrade to release 5.2:

- The HTML report has been redesigned by Vince Salvino. There is
  now a dark mode, the code text is larger, and system sans serif
  fonts are used, in addition to other small changes.
- The coverage report and coverage html commands now accept a
  --precision option to control the number of decimal points
  displayed. Thanks, Teake Nutma.
- The coverage report and coverage html commands now accept a
  --no-skip-covered option to negate --skip-covered.
  Thanks, Anthony Sottile.
- The --skip-empty option is now available for the XML report.
- The coverage report command now accepts a --sort option to
  specify how to sort the results. Thanks, Jerin Peter George.
- If coverage fails due to the coverage total not reaching the
  --fail-under value, it will now print a message making the
  condition clear. Thanks, Naveen Yadav.
- TOML configuration files with non-ASCII characters would cause
  errors on Windows. This is now fixed.
- The output of --debug=trace now includes information about how
  the --source option is being interpreted, and the module names
  being considered.

Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
---
 .../{python3-coverage_5.1.bb => python3-coverage_5.2.bb}      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-python/recipes-devtools/python/{python3-coverage_5.1.bb => python3-coverage_5.2.bb} (61%)

diff --git a/meta-python/recipes-devtools/python/python3-coverage_5.1.bb b/meta-python/recipes-devtools/python/python3-coverage_5.2.bb
similarity index 61%
rename from meta-python/recipes-devtools/python/python3-coverage_5.1.bb
rename to meta-python/recipes-devtools/python/python3-coverage_5.2.bb
index 7265d2c97..72558e10c 100644
--- a/meta-python/recipes-devtools/python/python3-coverage_5.1.bb
+++ b/meta-python/recipes-devtools/python/python3-coverage_5.2.bb
@@ -3,8 +3,8 @@ HOMEPAGE = "https://coverage.readthedocs.io"
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=2ee41112a44fe7014dce33e26468ba93"
 
-SRC_URI[md5sum] = "506e30fb011158abe5ce92f39866b271"
-SRC_URI[sha256sum] = "f90bfc4ad18450c80b024036eaf91e4a246ae287701aaa88eaebebf150868052"
+SRC_URI[md5sum] = "bfe80a336636160a3916467f55842bc5"
+SRC_URI[sha256sum] = "1874bdc943654ba46d28f179c1846f5710eda3aeb265ff029e0ac2b52daae404"
 
 inherit pypi setuptools3
 
-- 
2.17.1


  parent reply	other threads:[~2020-07-22 10:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22 10:48 [meta-python][PATCH 1/7] python3-pymysql: Upgrade 0.9.3 -> 0.10.0 Leon Anavi
2020-07-22 10:49 ` [meta-python][PATCH 2/7] python3-simplejson: Upgrade 3.17.0 -> 3.17.2 Leon Anavi
2020-07-23 16:47   ` [oe] " Trevor Gamblin
2020-07-22 10:49 ` [meta-python][PATCH 3/7] python3-isort: Upgrade 5.1.0 -> 5.1.4 Leon Anavi
2020-07-23 16:47   ` [oe] " Trevor Gamblin
2020-07-22 10:49 ` [meta-python][PATCH 4/7] python3-stevedore: Upgrade 2.0.1 -> 3.2.0 Leon Anavi
2020-07-23 16:47   ` [oe] " Trevor Gamblin
2020-07-22 10:49 ` [meta-python][PATCH 5/7] python3-mock: Upgrade 4.0.1 -> 4.0.2 Leon Anavi
2020-07-23 16:47   ` [oe] " Trevor Gamblin
2020-07-22 10:49 ` [meta-python][PATCH 6/7] python3-pychromecast: Upgrade 7.1.1 -> 7.1.2 Leon Anavi
2020-07-23 16:48   ` [oe] " Trevor Gamblin
2020-07-22 10:49 ` Leon Anavi [this message]
2020-07-23 16:48   ` [oe] [meta-python][PATCH 7/7] python3-coverage: Upgrade 5.1 -> 5.2 Trevor Gamblin
2020-07-23 16:47 ` [oe] [meta-python][PATCH 1/7] python3-pymysql: Upgrade 0.9.3 -> 0.10.0 Trevor Gamblin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200722104905.15499-7-leon.anavi@konsulko.com \
    --to=leon.anavi@konsulko.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.