From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/flit/
Date: Wed, 26 Jun 2024 09:05:34 +0000 (UTC) [thread overview]
Message-ID: <1719392626.40f5eee93d1523778270777a56f75f9cf8cdf41c.sam@gentoo> (raw)
commit: 40f5eee93d1523778270777a56f75f9cf8cdf41c
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Wed Jun 26 01:46:53 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Jun 26 09:03:46 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=40f5eee9
dev-python/flit: remove useless 4 year old dependencies
requests_download hasn't been used since a deprecated feature available
as a pip "extra" was removed:
https://github.com/pypa/flit/commit/b9a8ecd6037b3b98452c6fa90697612075c03ef4
Arguably before then it should have been an optfeature but at this point
it is pointless to discuss -- the feature got dropped in flit 3.0.0.
tomli has never been a dependency at all. The first version of flit that
moved from "toml" (an abandoned project) to tomli, only used tomli_w in
flit, and relied on flit_core to handle all use of "tomli" (and
flit-core correctly depends on the stdlib tomllib where reasonable).
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-python/flit/{flit-3.9.0.ebuild => flit-3.9.0-r1.ebuild} | 2 --
1 file changed, 2 deletions(-)
diff --git a/dev-python/flit/flit-3.9.0.ebuild b/dev-python/flit/flit-3.9.0-r1.ebuild
similarity index 94%
rename from dev-python/flit/flit-3.9.0.ebuild
rename to dev-python/flit/flit-3.9.0-r1.ebuild
index 249a8b03166e..572497166710 100644
--- a/dev-python/flit/flit-3.9.0.ebuild
+++ b/dev-python/flit/flit-3.9.0-r1.ebuild
@@ -18,8 +18,6 @@ RDEPEND="
dev-python/docutils[${PYTHON_USEDEP}]
>=dev-python/flit-core-${PV}[${PYTHON_USEDEP}]
dev-python/requests[${PYTHON_USEDEP}]
- dev-python/requests_download[${PYTHON_USEDEP}]
- dev-python/tomli[${PYTHON_USEDEP}]
dev-python/tomli-w[${PYTHON_USEDEP}]
"
BDEPEND="${RDEPEND}
next reply other threads:[~2024-06-26 9:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 9:05 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-12 7:40 [gentoo-commits] repo/gentoo:master commit in: dev-python/flit/ Michał Górny
2025-03-26 6:35 Michał Górny
2025-03-08 10:50 Michał Górny
2025-02-28 19:41 Michał Górny
2025-02-20 5:06 Michał Górny
2024-11-23 8:17 Michał Górny
2024-11-03 3:52 Michał Górny
2024-07-07 14:36 Michał Górny
2024-06-26 9:05 Sam James
2024-05-03 5:31 Arthur Zamarin
2023-05-26 3:57 Michał Górny
2023-03-16 3:50 Michał Górny
2023-01-22 19:20 Arthur Zamarin
2022-11-14 4:39 Michał Górny
2022-11-05 20:35 Arthur Zamarin
2022-11-05 17:33 Arthur Zamarin
2022-02-23 21:30 Michał Górny
2022-02-23 21:30 Michał Górny
2022-02-22 18:55 Michał Górny
2022-01-17 5:33 Joshua Kinard
2022-01-16 17:53 Michał Górny
2022-01-13 20:16 Michał Górny
2022-01-13 20:16 Michał Górny
2022-01-06 10:39 David Seifert
2021-12-28 9:03 Michał Górny
2021-12-28 9:03 Michał Górny
2021-11-23 22:05 Michał Górny
2021-11-19 9:03 Michał Górny
2021-10-11 7:56 Michał Górny
2021-09-10 14:03 Arthur Zamarin
2021-08-01 12:25 Michał Górny
2021-08-01 12:25 Michał Górny
2021-08-01 9:39 Michał Górny
2021-08-01 9:39 Michał Górny
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=1719392626.40f5eee93d1523778270777a56f75f9cf8cdf41c.sam@gentoo \
--to=sam@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