From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/rfc3339-validator/
Date: Wed, 11 May 2022 16:43:49 +0000 (UTC) [thread overview]
Message-ID: <1652287419.21c2147b9222958197678a258fa17a8ef3fa5779.mgorny@gentoo> (raw)
commit: 21c2147b9222958197678a258fa17a8ef3fa5779
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed May 11 16:31:19 2022 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed May 11 16:43:39 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=21c2147b
dev-python/rfc3339-validator: Revert the pytest-markdown workaround
The awful mistake of dev-python/pytest-markdown is now sterilized
via epytest, no need to work around it anymore.
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/rfc3339-validator/rfc3339-validator-0.1.4-r1.ebuild | 4 ----
1 file changed, 4 deletions(-)
diff --git a/dev-python/rfc3339-validator/rfc3339-validator-0.1.4-r1.ebuild b/dev-python/rfc3339-validator/rfc3339-validator-0.1.4-r1.ebuild
index b85efbca0543..72cb16eb1624 100644
--- a/dev-python/rfc3339-validator/rfc3339-validator-0.1.4-r1.ebuild
+++ b/dev-python/rfc3339-validator/rfc3339-validator-0.1.4-r1.ebuild
@@ -33,7 +33,3 @@ BDEPEND="
"
distutils_enable_tests pytest
-
-python_test() {
- epytest tests
-}
next reply other threads:[~2022-05-11 16:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 16:43 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-12 16:30 [gentoo-commits] repo/gentoo:master commit in: dev-python/rfc3339-validator/ Michał Górny
2024-05-12 16:30 Michał Górny
2023-07-08 10:47 Benda XU
2023-05-26 15:14 Sam James
2022-06-13 8:23 Michał Górny
2022-05-11 14:32 Michał Górny
2022-05-11 14:32 Michał Górny
2022-01-17 13:02 James Le Cuirot
2021-11-18 5:36 Sam James
2021-07-03 6:26 Michał Górny
2021-07-03 1:32 Sam James
2021-05-24 21:58 Joshua Kinard
2021-05-13 8:56 Michał Górny
2021-05-10 21:56 Michał Górny
2021-05-10 21:56 Michał Górny
2021-04-27 18:09 Sam James
2021-04-27 11:37 Michał Górny
2021-03-23 8:39 Michał Górny
2020-12-13 1:06 Sam James
2020-08-02 9:33 Michał Górny
2020-06-09 19:46 Michał Górny
2020-06-06 19:31 Mart Raudsepp
2020-06-05 16:10 Sergei Trofimovich
2020-06-04 6:35 Agostino Sarubbo
2020-06-04 6:23 Agostino Sarubbo
2020-06-03 18:43 Agostino Sarubbo
2020-06-03 15:12 Agostino Sarubbo
2020-06-01 20:51 Sergei Trofimovich
2020-06-01 17:02 Sergei Trofimovich
2020-04-30 7:16 Sergei Trofimovich
2020-04-28 19:23 Mart Raudsepp
2020-04-28 15:41 Mikle Kolyada
2020-04-28 7:00 Michał Górny
2020-03-29 21:21 Sergei Trofimovich
2020-03-28 23:40 Sergei Trofimovich
2020-03-17 2:09 Matt Turner
2019-12-05 22:15 Sergei Trofimovich
2019-12-04 19:44 Sergei Trofimovich
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=1652287419.21c2147b9222958197678a258fa17a8ef3fa5779.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