X-Original-To: alpine-devel@lists.alpinelinux.org Received: from mx1.tetrasec.net (mx1.tetrasec.net [74.117.190.25]) by lists.alpinelinux.org (Postfix) with ESMTP id 8088AF81708 for ; Tue, 19 Mar 2019 12:04:15 +0000 (UTC) Received: from mx1.tetrasec.net (mail.local [127.0.0.1]) by mx1.tetrasec.net (Postfix) with ESMTP id 4CC139E22B2; Tue, 19 Mar 2019 12:04:15 +0000 (UTC) Received: from ncopa-desktop.copa.dup.pw (67.63.200.37.customer.cdi.no [37.200.63.67]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: alpine@tanael.org) by mx1.tetrasec.net (Postfix) with ESMTPSA id D2E7A9E03F8; Tue, 19 Mar 2019 12:04:13 +0000 (UTC) Date: Tue, 19 Mar 2019 13:04:08 +0100 From: Natanael Copa To: Drew DeVault Cc: alpine-devel@lists.alpinelinux.org, Fabian Affolter Subject: Re: [alpine-devel] Normalizing Python packages in aports Message-ID: <20190319130408.3f3861dc@ncopa-desktop.copa.dup.pw> In-Reply-To: <20190306212501.GD2800@cirno.localdomain> References: <20190306212501.GD2800@cirno.localdomain> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-alpine-linux-musl) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Wed, 6 Mar 2019 14:25:02 -0700 Drew DeVault wrote: > I'd like to start working on normalizing the Python packages in aports. > The quality of Python packages is pretty hit-or-miss: many packages have > only Python 2 support, split packages are addressed inconsistently, and > checks() are missing on most. > > I've put together a proposal on the wiki for Python packaging standards. > If we like this proposal, the next step would be applying these > standards to the existing packages in aports. I'll compile a list of > affected packages and some simple scripts to help track progress/todo > and we can get started in a separate branch. > > Here's my proposal for packaging standards: > > https://wiki.alpinelinux.org/wiki/Python_package_policies > > Another issue we'll have to face soon enough is Python 2 end-of-life. Do > we want to address this at the same time? I think the best balance of > conservatism and speedy removal of python 2 would be: > > - Stop adding new python 2 packages to aports > - As we normalize existing packages, drop python 2 if it's easy, or make > a note if not > - Make case-by-case judgement calls on the more difficult packages, > based on the upstream's progress/amicability towards a python 3 port. > Upstreams which are unwilling to port to python 3 should probably just > be dropped. > > If we bikeshed too hard on the Python 2 deprecation let's drop it and > focus just on normalization for now - it'll be easier to deal with > Python 2 from a sane baseline anyway. > > Thoughts? I would like to hear what Fabian Affolter thinks of your proposal. Fabian maintains alot of python packages and has done so for a while. -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---