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 6883C139694 for ; Mon, 10 Jul 2017 17:25:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 358BE21412D; Mon, 10 Jul 2017 17:25:09 +0000 (UTC) Received: from smtp.gentoo.org (dev.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 E4240214126 for ; Mon, 10 Jul 2017 17:25:08 +0000 (UTC) Received: from localhost (unknown [IPv6:2a01:e34:eeaa:6bd0:4ecc:6aff:fe03:1cfc]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: aballier) by smtp.gentoo.org (Postfix) with ESMTPSA id A5C65341A44 for ; Mon, 10 Jul 2017 17:25:07 +0000 (UTC) Date: Mon, 10 Jul 2017 19:25:02 +0200 From: Alexis Ballier To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] About adding a *warning* to remind maintainers to check for new PYTHON_COMPAT values Message-ID: <20170710192502.4ae8a83e@gentoo.org> In-Reply-To: <20170710165530.GA22754@whubbs1.gaikai.biz> References: <1499684650.24824.6.camel@gentoo.org> <20170710165530.GA22754@whubbs1.gaikai.biz> Organization: Gentoo X-Mailer: Claws Mail 3.15.0-dirty (GTK+ 2.24.31; x86_64-pc-linux-gnu) 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-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 5c2ab683-2f3a-4a80-8ac5-03248a45ea76 X-Archives-Hash: 4f852c9db46519f9cf09de8de23d436a On Mon, 10 Jul 2017 11:55:30 -0500 William Hubbs wrote: > On Mon, Jul 10, 2017 at 01:04:10PM +0200, Pacho Ramos wrote: > > 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? > > What about the situation where a package is not compatible with newer > versions of python so does not need a PYTHON_COMPAT change? > > I don't think you can assume PYTHON_COMPAT is outdated for a package > just because it doesn't have the latest versions of python > listed. The only time you can know for sure that it is outdated is if > it lists a version of python that no longer exists in the tree. Maybe we should add some - modifier to PYTHON_COMPAT, just like keywords, indicating it has been tested to *not* work. PYTHON_COMPAT=( python{2_7,3_4,3_5} -python_3_6 )