From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C489F139694 for ; Mon, 10 Jul 2017 11:04:21 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0D2B6274203; Mon, 10 Jul 2017 11:04:16 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id BC6DF2741EB for ; Mon, 10 Jul 2017 11:04:15 +0000 (UTC) Received: from [192.168.0.18] (81.61.201.10.dyn.user.ono.com [81.61.201.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id F1910341ADF for ; Mon, 10 Jul 2017 11:04:13 +0000 (UTC) Message-ID: <1499684650.24824.6.camel@gentoo.org> Subject: [gentoo-dev] About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values From: Pacho Ramos To: gentoo-dev Date: Mon, 10 Jul 2017 13:04:10 +0200 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Archives-Salt: 419cb6ac-86d4-4d54-899a-039d1430f776 X-Archives-Hash: 7e5e71d97310869c09f334722fea7d1d Hello Looking to the list of packages still not supporting python 3.5: https://qa-reports.gentoo.org/output/gpyutils/34-to-35.txt and considering that we should even start testing python 3.6, I think it would be nice if we could make portage to warn when PYTHON_COMPAT value is not updated. It's really frustrating to still see new ebuilds being added with obsolete values for PYTHON_COMPAT and relying on a few people looking to update this. This is also causing huge delays to migrate to newer python versions and I think it's responsibility of the maintainer to ensure his/her package is supported on newer versions or, at least, have a bug and ping upstream for the cases they need further fixing. Of course, this wouldn't be a fatal check preventing you from committing a package with outdated PYTHON_COMPAT, it would be a warning to remind you to update it as soon as possible. Any issues on trying to go further into implementing this warning? Thanks a lot