public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-check/
Date: Fri, 10 Feb 2023 06:52:10 +0000 (UTC)	[thread overview]
Message-ID: <1676011916.fdf9f7f3ea5e2d8ac3488e6ba15316dda91438f3.mgorny@gentoo> (raw)

commit:     fdf9f7f3ea5e2d8ac3488e6ba15316dda91438f3
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 10 06:21:47 2023 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Fri Feb 10 06:51:56 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fdf9f7f3

dev-python/pytest-check: Bump to 2.1.3

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-python/pytest-check/Manifest                  |  1 +
 dev-python/pytest-check/pytest-check-2.1.3.ebuild | 30 +++++++++++++++++++++++
 2 files changed, 31 insertions(+)

diff --git a/dev-python/pytest-check/Manifest b/dev-python/pytest-check/Manifest
index d3bcbe1392b6..f2b5c13a307a 100644
--- a/dev-python/pytest-check/Manifest
+++ b/dev-python/pytest-check/Manifest
@@ -3,3 +3,4 @@ DIST pytest-check-2.0.0.tar.gz 24825 BLAKE2B b1398dd98d90b9ba26cdda7776a63db8afc
 DIST pytest-check-2.1.0.tar.gz 25849 BLAKE2B 4b5fe598cdd395f153abd6cab90c729d0a70eb31ff95fe8eaccc7c1378e20adde65b9c1e35dd961bba2aede040652f97ac81d7fdaed4dd21d1ed44c340ea948f SHA512 503aee4eafab43dbe882f7d4ca63a63d4c3df78d691fc057de4bee72e2d2e61bb694c7c412b915e4019c052e34f9d80e02e03bf2be2c58c4c48b59e354a03763
 DIST pytest-check-2.1.1.tar.gz 26004 BLAKE2B 382931f4bc1f86106a0296b1a33d604976b6ad6933bb71e27e406af21bc87f6915cca7d383d0ec84cae0dc9e747d335c31005e0b22ba20514d5dafe1bc957d58 SHA512 8a12f6d5ae60204b55d8282c88558678b7676d0e0436a7d1d28e65783a367db6efb68ff8105cb4293c5d52db5f5a8510d726b387a86351421c6ff9f023cde88a
 DIST pytest-check-2.1.2.tar.gz 26152 BLAKE2B 75b58b97cb78f297614f6dce62662ee974e899846d896fa4e1d6ee5aa1e916e8c1d363a8de19fe842263702a94cb6e58519639bca82ac98d17ab596b724e98bd SHA512 1b5532e9473067db819e7d0ded5b8e681197c052b83909920eee0fc45c48047b849f513e6ad77d94e0fa06c9eb00845ec3f3ad7f38f3e90d80d82d7460d0d35a
+DIST pytest-check-2.1.3.gh.tar.gz 21570 BLAKE2B 8873d649e63ffca1fc8ab04383467f4cfb6c34f3970db95f1d439a3526d2a8b3482524ec2eda6a09fb2d166a781ff94895b976685ee8846d8e80ff5de6fd47e8 SHA512 bfd3975d93e27ccda71944e66b57e7628c5efbbbb6d9ac137fd58c96de760a1a4059fbdaf67d9c8844d2e5f0d7c671f2768fe1ced26f9a5406b872627238f664

diff --git a/dev-python/pytest-check/pytest-check-2.1.3.ebuild b/dev-python/pytest-check/pytest-check-2.1.3.ebuild
new file mode 100644
index 000000000000..98715a584197
--- /dev/null
+++ b/dev-python/pytest-check/pytest-check-2.1.3.ebuild
@@ -0,0 +1,30 @@
+# Copyright 2021-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+DISTUTILS_USE_PEP517=flit
+PYTHON_COMPAT=( python3_{9..11} )
+
+inherit distutils-r1
+
+DESCRIPTION="pytest plugin that allows multiple failures per test"
+HOMEPAGE="
+	https://github.com/okken/pytest-check/
+	https://pypi.org/project/pytest-check/
+"
+SRC_URI="
+	https://github.com/okken/pytest-check/archive/${PV}.tar.gz
+		-> ${P}.gh.tar.gz
+"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64 ~arm ~arm64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~riscv ~s390 ~sparc ~x86"
+
+RDEPEND="
+	>=dev-python/colorama-0.4.6[${PYTHON_USEDEP}]
+	dev-python/pytest[${PYTHON_USEDEP}]
+"
+
+distutils_enable_tests pytest


             reply	other threads:[~2023-02-10  6:52 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-10  6:52 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-28 12:59 [gentoo-commits] repo/gentoo:master commit in: dev-python/pytest-check/ Michał Górny
2024-09-28 12:32 Arthur Zamarin
2024-08-29  4:52 Michał Górny
2024-08-28  3:43 Michał Górny
2024-06-10  7:57 Petr Vaněk
2024-02-03  9:17 Michał Górny
2024-02-03  8:30 Arthur Zamarin
2024-01-24 19:05 Michał Górny
2024-01-19  5:28 Michał Górny
2024-01-18 18:46 Michał Górny
2024-01-18 18:03 Arthur Zamarin
2024-01-18  3:43 Michał Górny
2024-01-09  7:02 Michał Górny
2024-01-01  4:13 Michał Górny
2023-10-24  5:58 Michał Górny
2023-10-23 18:50 Sam James
2023-09-22 11:34 Michał Górny
2023-08-19 18:14 Michał Górny
2023-08-19 16:44 Arthur Zamarin
2023-08-12  3:27 Michał Górny
2023-07-15  3:04 Michał Górny
2023-07-10  1:38 Michał Górny
2023-06-07  4:40 Michał Górny
2023-06-07  4:40 Michał Górny
2023-03-17 15:58 Michał Górny
2023-03-17 15:52 Arthur Zamarin
2023-03-14  5:02 Michał Górny
2023-03-13 19:39 Arthur Zamarin
2023-02-14  4:57 Michał Górny
2023-02-13  6:07 Michał Górny
2023-02-13  3:22 Matt Turner
2023-02-12 20:24 Jakov Smolić
2023-01-14  4:57 Michał Górny
2023-01-13  7:09 Michał Górny
2023-01-11 20:34 Michał Górny
2023-01-09  8:09 Michał Górny
2022-12-25 17:41 Michał Górny
2022-12-03  9:09 Michał Górny
2022-12-02 14:03 Arthur Zamarin
2022-11-26  6:28 Michał Górny
2022-11-23  8:41 Michał Górny
2022-11-22 19:56 Arthur Zamarin
2022-11-22  6:27 Arthur Zamarin
2022-11-03 19:41 Arthur Zamarin
2022-11-03 19:32 Arthur Zamarin
2022-09-29 18:07 Arthur Zamarin
2022-09-25 18:35 Arthur Zamarin
2022-09-25 18:28 Arthur Zamarin
2022-08-25 19:25 Arthur Zamarin
2022-08-21 17:41 Arthur Zamarin
2022-05-10  5:47 Arthur Zamarin
2022-05-01 12:56 Michał Górny
2022-05-01 12:20 Jakov Smolić
2022-05-01  6:55 Michał Górny
2022-03-31 16:03 Michał Górny
2022-02-07 22:29 Sam James
2022-02-07 20:14 Arthur Zamarin
2022-02-07 20:14 Arthur Zamarin
2022-02-07  9:35 Sam James
2021-11-19 11:39 Arthur Zamarin
2021-11-19  7:59 Arthur Zamarin
2021-11-18 10:50 Sam James
2021-11-15 16:29 Agostino Sarubbo
2021-10-24  4:51 Sam James
2021-10-24  2:27 Sam James
2021-10-24  0:19 Sam James
2021-10-10 20:43 Sam James
2021-10-10  2:20 Sam James
2021-10-10  0:09 Sam James
2021-10-09 20:19 Sam James
2021-09-24 22:48 Sam James
2021-09-23 17:22 Arthur Zamarin

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=1676011916.fdf9f7f3ea5e2d8ac3488e6ba15316dda91438f3.mgorny@gentoo \
    --to=mgorny@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox