Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Jeroen Ploemen Newsgroups: linux.debian.maint.python Subject: review for python-asyncpraw/7.8.1-1 Date: Thu, 19 Feb 2026 14:20:01 +0100 Message-ID: X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Feb 19 13:12:08 2026 Old-Return-Path: X-Amavis-Spam-Status: No, score=-114.51 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, PGPSIGNATURE=-5, RCVD_IN_DNSWL_MED=-2.3, UNPARSEABLE_RELAY=0.001, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no X-Mailer: Claws Mail 4.3.1 (GTK 3.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/rrSH=ub7+EgTgD/5F+Yll.s"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Debian-User: jcfp X-Mailing-List: archive/latest/23663 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20260219131149.6fd0b33f@debian.org Approved: robomod@news.nic.it Lines: 49 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Thu, 19 Feb 2026 13:11:49 -0000 X-Original-Message-ID: <20260219131149.6fd0b33f@debian.org> Xref: csiph.com linux.debian.maint.python:17403 --Sig_/rrSH=ub7+EgTgD/5F+Yll.s Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable hi Aryan, I took a look at the python-asyncpraw package, up for sponsorship in the Python team: * there's a vast diff (doc, tests, tools, ...) between the orig tarball uscan pulls in and the one generated from the pristine-tar branch. * copyright: upstream in their README.rst says this is a fork of praw, and there's a praw_license.txt file in the root of the sources; none of that info shows up in d/copyright though. * d/salsa-ci.yml present but the CI isn't enabled on the salsa repo. * why are tests disabled wholesale? Even assuming there were a good reason, that should at least be documented - for example by adding a comment alongside the setting in d/rules. I stopped reviewing at this point, as the above might lead to significant changes. Once the above comments have been addressed, simply re-add the package to the IRC channel topic and/or ping me by e-mail. --Sig_/rrSH=ub7+EgTgD/5F+Yll.s Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEd8lhnEnWos3N8v+qQoMEoXSNzHoFAmmXDBUACgkQQoMEoXSN zHqtgQ//QroPylpKDu2u/Xkma9vSFfuCYyPdeJYTwgnk/fwIFaEfpf7ua+yHnx3m PdmsfmyzzbArSlQPPrJLXC6BHKbmDjmfS9oJ9QhkwgDwFagl++tidFdnRR93nd70 kgKREQlG6IbMixPoA3Okn5YewS7PpcDC7yRoj8eVOZCV2ZGoKqwz1gkxbvb9O6X+ K25BfHaWKr1aYlEeUNIdpbN3QNW01PIpPkvdXQzbHsE8ZUx2H+eGRyazfQFvVrHm qy8VdG+MAEdTpM1+BRgjKJOPdhEI9rHd0euj97a04FFz0ny+cysOtyuW2o+dVZCp sIV2Hqwsm6Fz+YisjThRJPLfgzCc8tMH5Ycmrs1fjd2YkNvwZFHxL64ator8c4P0 2BCsXXgEYczEEzRxPYsmT0irozqHSDKAKEUAdzI6aggSa9n9T41LT0TpJEaU0iKM mwe59ZNJu0lYE0JRApNtSD6ImukY7JmamISw4k51UJz9N9WSv3UyF/GIOC4WqLKA n8FBtwfwFqF5bwct2Vu3bJmg9ueGnJqikuxn5riDxf8w2TGyVKixZIPr+S7XCiK+ hYKgv1LyF0zqsIqOZAH72hxH4x/zdHyYMGkJCvq5kX28gYbiZp8dJ5xF2Pe6fWfy hpx9FaTTfKyTMLwGFTE/DnzIdAG3LCR1AcGRDy5NaybJ57TpFoU= =Jb/7 -----END PGP SIGNATURE----- --Sig_/rrSH=ub7+EgTgD/5F+Yll.s--