From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/flask-security/
Date: Wed, 24 Jun 2020 07:07:16 +0000 (UTC) [thread overview]
Message-ID: <1592982426.9b93f09b20a459bd3a23ebc36410dfe29da3928e.mgorny@gentoo> (raw)
commit: 9b93f09b20a459bd3a23ebc36410dfe29da3928e
Author: Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 24 06:49:06 2020 +0000
Commit: Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Jun 24 07:07:06 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9b93f09b
dev-python/flask-security: Remove pytest-runner dep
Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>
dev-python/flask-security/flask-security-3.0.0.ebuild | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/dev-python/flask-security/flask-security-3.0.0.ebuild b/dev-python/flask-security/flask-security-3.0.0.ebuild
index 349a0a18f98..5544516760b 100644
--- a/dev-python/flask-security/flask-security-3.0.0.ebuild
+++ b/dev-python/flask-security/flask-security-3.0.0.ebuild
@@ -31,8 +31,6 @@ RDEPEND=">=dev-python/flask-0.11[${PYTHON_USEDEP}]
"
DEPEND="${RDEPEND}
- dev-python/pytest-runner[${PYTHON_USEDEP}]
- dev-python/setuptools[${PYTHON_USEDEP}]
test? (
dev-python/nose[${PYTHON_USEDEP}]
dev-python/flask-sqlalchemy[${PYTHON_USEDEP}]
@@ -43,6 +41,11 @@ DEPEND="${RDEPEND}
S="${WORKDIR}/${MY_P}"
+src_prepare() {
+ sed -i -e '/pytest-runner/d' setup.py || die
+ distutils-r1_src_prepare
+}
+
python_test() {
nosetests -v || die "Testing failed with ${EPYTHON}"
}
next reply other threads:[~2020-06-24 7:07 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 7:07 Michał Górny [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-29 10:12 [gentoo-commits] repo/gentoo:master commit in: dev-python/flask-security/ Arthur Zamarin
2022-05-21 17:35 Jakov Smolić
2022-04-20 7:47 Michał Górny
2022-04-16 15:56 Michał Górny
2022-04-16 7:38 Sam James
2022-03-24 22:50 Jakov Smolić
2022-03-22 21:53 Michał Górny
2022-03-22 21:53 Michał Górny
2022-03-16 10:06 Michał Górny
2021-10-23 14:03 Arthur Zamarin
2021-10-16 5:56 Michał Górny
2021-10-15 22:42 Sam James
2021-09-23 8:16 Michał Górny
2021-09-11 22:09 Michał Górny
2021-08-26 8:24 Michał Górny
2021-08-26 4:41 Agostino Sarubbo
2021-07-24 8:23 Michał Górny
2021-05-06 10:06 Sam James
2021-04-13 21:49 Michał Górny
2021-04-13 21:49 Michał Górny
2021-04-03 6:59 Michał Górny
2021-03-02 4:39 Sam James
2021-01-12 12:03 Sam James
2021-01-11 23:56 Michał Górny
2021-01-11 23:56 Michał Górny
2021-01-11 23:56 Michał Górny
2020-09-18 14:48 Michał Górny
2020-09-04 4:58 Sam James
2020-08-22 8:09 Michał Górny
2020-08-18 8:55 Michał Górny
2020-07-28 12:48 Michał Górny
2020-03-17 7:23 Michał Górny
2020-02-05 21:28 Andreas Sturmlechner
2020-02-05 13:24 Michał Górny
2019-12-01 19:27 Andreas Sturmlechner
2018-07-10 21:47 Michał Górny
2018-06-24 14:09 Jason Zaman
2018-06-24 11:31 Pacho Ramos
2018-05-20 16:53 Aaron Swenson
2018-05-18 11:27 Aaron Swenson
2018-04-29 7:35 Michał Górny
2018-01-03 23:35 Michał Górny
2017-12-29 18:48 Mikle Kolyada
2017-12-19 15:46 Thomas Deutschmann
2016-11-06 11:25 Tiziano Müller
2016-02-14 18:56 Patrick Lauer
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=1592982426.9b93f09b20a459bd3a23ebc36410dfe29da3928e.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