public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anna Vyalkova" <cyber+gentoo@sysrq.in>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-python/rich-click/
Date: Fri, 28 Feb 2025 14:51:52 +0000 (UTC)	[thread overview]
Message-ID: <1740754296.2d47553dca5694fa00665bc367a2edaee2c674dd.cybertailor@gentoo> (raw)

commit:     2d47553dca5694fa00665bc367a2edaee2c674dd
Author:     Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
AuthorDate: Fri Feb 28 14:26:58 2025 +0000
Commit:     Anna Vyalkova <cyber+gentoo <AT> sysrq <DOT> in>
CommitDate: Fri Feb 28 14:51:36 2025 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=2d47553d

dev-python/rich-click: add 1.8.6, drop 1.8.4

Signed-off-by: Anna (cybertailor) Vyalkova <cyber+gentoo <AT> sysrq.in>

 dev-python/rich-click/Manifest                                          | 2 +-
 .../rich-click/{rich-click-1.8.4.ebuild => rich-click-1.8.6.ebuild}     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-python/rich-click/Manifest b/dev-python/rich-click/Manifest
index 3719fb214..229734928 100644
--- a/dev-python/rich-click/Manifest
+++ b/dev-python/rich-click/Manifest
@@ -1,2 +1,2 @@
-DIST rich-click-1.8.4.gh.tar.gz 375081 BLAKE2B f69491a9b5b0321783d0ce0225ae49d91bc38962a866ea85d438940860fc11f22662f242a85621b156d3143245c544c63947d260cc817ae3da96cbc15e9683c5 SHA512 34d650cf47becef15cb0ad32b6fe87b534e4d56de42106baacbcc3721c39297d383050118e57bb85a18332d28b52ba93f989141c8acc5c142953248c8e9e6a95
 DIST rich-click-1.8.5.gh.tar.gz 8135268 BLAKE2B 84e9fe895d70a4357ea49d383822b6f50d9c89b3788e0ef60200c2a67807ac1e77df2dba8d1fafc9a78f4174d12241c7f3faf53177bfa64d031da673c67ce4e8 SHA512 ccb309f05593c55edc097a199eb07f4c260217751e3bc5a27a6f11cfa5d6f98125086729639f0a5d6b476c17c18ef1b9cc29a26ac24dacb84754feed4291af3d
+DIST rich-click-1.8.6.gh.tar.gz 8140359 BLAKE2B ab5ddbad68cae208797a7893fdd8092035d8b4a428926fd55ffb01ebdd1ea83a510c1bf0622f01fd9f84da791425d1ac5647febc16bc55781c28d3fac96c70d3 SHA512 922c0c133104cb1aba9aca439aa81835202bf055c0b652339f3eb0c66bf71e7cb201881e03eb585f3eb1c0dedf1aa943df18917ce86f0d8d607ea7f9208ab0e2

diff --git a/dev-python/rich-click/rich-click-1.8.4.ebuild b/dev-python/rich-click/rich-click-1.8.6.ebuild
similarity index 94%
rename from dev-python/rich-click/rich-click-1.8.4.ebuild
rename to dev-python/rich-click/rich-click-1.8.6.ebuild
index 923a7332d..63e6f7e72 100644
--- a/dev-python/rich-click/rich-click-1.8.4.ebuild
+++ b/dev-python/rich-click/rich-click-1.8.6.ebuild
@@ -4,7 +4,7 @@
 EAPI=8
 
 DISTUTILS_USE_PEP517=setuptools
-PYTHON_COMPAT=( python3_{11..13} )
+PYTHON_COMPAT=( python3_{11..13} pypy3 )
 
 inherit click-app distutils-r1
 


             reply	other threads:[~2025-02-28 14:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28 14:51 Anna Vyalkova [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-09  6:24 [gentoo-commits] repo/proj/guru:dev commit in: dev-python/rich-click/ Anna Vyalkova
2024-12-03  4:30 Anna Vyalkova
2024-12-02 14:17 Anna Vyalkova
2024-11-26 14:15 Anna Vyalkova
2024-11-16  5:36 Anna Vyalkova
2024-10-30  0:05 Anna Vyalkova
2024-10-29  1:05 Anna Vyalkova

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=1740754296.2d47553dca5694fa00665bc367a2edaee2c674dd.cybertailor@gentoo \
    --to=cyber+gentoo@sysrq.in \
    --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