Date: Thu, 07 Mar 2019 09:25:18 +0200
User-Agent: K-9 Mail for Android
In-Reply-To: <20190306212501.GD2800@cirno.localdomain>
References: <20190306212501.GD2800@cirno.localdomain>
Precedence: list
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----3HCBPPKMTFM0A292BBATDPP0M801QC"
Content-Transfer-Encoding: 7bit
Subject: Re: [alpine-devel] Normalizing Python packages in aports
To: alpine-devel@lists.alpinelinux.org
From: =?UTF-8?B?0JzQuNGF0LDQudC70L4g0J7RgNC40YjQuNGH?= <mishaor@ukr.net>
Message-ID: <F65BF3D9-C6EA-49D9-9873-B3A44F994C76@ukr.net>
Authentication-Result: IP=46.133.156.21; mail.from=mishaor@ukr.net; dkim=pass; header.d=ukr.net

------3HCBPPKMTFM0A292BBATDPP0M801QC
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

Both hands up=2E

6 =D0=B1=D0=B5=D1=80=D0=B5=D0=B7=D0=BD=D1=8F 2019 =D1=80=2E 23:25:02 GMT+0=
2:00, Drew DeVault <sir@cmpwn=2Ecom> =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=
=D0=B2:
>I'd like to start working on normalizing the Python packages in aports=2E
>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=2E
>
>I've put together a proposal on the wiki for Python packaging
>standards=2E
>If we like this proposal, the next step would be applying these
>standards to the existing packages in aports=2E 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=2E
>
>Here's my proposal for packaging standards:
>
>https://wiki=2Ealpinelinux=2Eorg/wiki/Python_package_policies
>
>Another issue we'll have to face soon enough is Python 2 end-of-life=2E
>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=2E
> Upstreams which are unwilling to port to python 3 should probably just
>  be dropped=2E
>
>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=2E
>
>Thoughts?
>
>--
>Drew DeVault
>
>
>---
>Unsubscribe:  alpine-devel+unsubscribe@lists=2Ealpinelinux=2Eorg
>Help:         alpine-devel+help@lists=2Ealpinelinux=2Eorg
>---

--=20
=D0=92=D1=96=D0=B4=D0=BF=D1=80=D0=B0=D0=B2=D0=BB=D0=B5=D0=BD=D0=BE =D0=B7 =
=D0=BC=D0=BE=D0=B3=D0=BE Android =D0=BF=D1=80=D0=B8=D1=81=D1=82=D1=80=D0=BE=
=D1=8E =D0=B7 K-9 Mail=2E =D0=92=D0=B8=D0=B1=D0=B0=D1=87=D1=82=D0=B5 =D0=B7=
=D0=B0 =D1=81=D1=82=D0=B8=D1=81=D0=BB=D1=96=D1=81=D1=82=D1=8C=2E
------3HCBPPKMTFM0A292BBATDPP0M801QC
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body>Both hands up=2E<br><br><div class=3D"gmail_quote"=
>6 =D0=B1=D0=B5=D1=80=D0=B5=D0=B7=D0=BD=D1=8F 2019 =D1=80=2E 23:25:02 GMT+0=
2:00, Drew DeVault &lt;sir@cmpwn=2Ecom&gt; =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=
=D0=B0=D0=B2:<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt=
 0=2E8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class=3D"k9mail">I'd like to start working on normalizing the Python =
packages in aports=2E<br />The quality of Python packages is pretty hit-or-=
miss: many packages have<br />only Python 2 support, split packages are add=
ressed inconsistently, and<br />checks() are missing on most=2E<br /><br />=
I've put together a proposal on the wiki for Python packaging standards=2E<=
br />If we like this proposal, the next step would be applying these<br />s=
tandards to the existing packages in aports=2E I'll compile a list of<br />=
affected packages and some simple scripts to help track progress/todo<br />=
and we can get started in a separate branch=2E<br /><br />Here's my proposa=
l for packaging standards:<br /><br /><a href=3D"https://wiki=2Ealpinelinux=
=2Eorg/wiki/Python_package_policies">https://wiki=2Ealpinelinux=2Eorg/wiki/=
Python_package_policies</a><br /><br />Another issue we'll have to face soo=
n enough is Python 2 end-of-life=2E Do<br />we want to address this at the =
same time? I think the best balance of<br />conservatism and speedy removal=
 of python 2 would be:<br /><br />- Stop adding new python 2 packages to ap=
orts<br />- As we normalize existing packages, drop python 2 if it's easy, =
or make<br />  a note if not<br />- Make case-by-case judgement calls on th=
e more difficult packages,<br />  based on the upstream's progress/amicabil=
ity towards a python 3 port=2E<br />  Upstreams which are unwilling to port=
 to python 3 should probably just<br />  be dropped=2E<br /><br />If we bik=
eshed too hard on the Python 2 deprecation let's drop it and<br />focus jus=
t on normalization for now - it'll be easier to deal with<br />Python 2 fro=
m a sane baseline anyway=2E<br /><br />Thoughts?<br /><br />--<br />Drew De=
Vault<br /><br /><br />---<br />Unsubscribe:  alpine-devel+unsubscribe@list=
s=2Ealpinelinux=2Eorg<br />Help:         alpine-devel+help@lists=2Ealpineli=
nux=2Eorg<br />---<br /><br /></pre></blockquote></div><br>
-- <br>
=D0=92=D1=96=D0=B4=D0=BF=D1=80=D0=B0=D0=B2=D0=BB=D0=B5=D0=BD=D0=BE =D0=B7 =
=D0=BC=D0=BE=D0=B3=D0=BE Android =D0=BF=D1=80=D0=B8=D1=81=D1=82=D1=80=D0=BE=
=D1=8E =D0=B7 K-9 Mail=2E =D0=92=D0=B8=D0=B1=D0=B0=D1=87=D1=82=D0=B5 =D0=B7=
=D0=B0 =D1=81=D1=82=D0=B8=D1=81=D0=BB=D1=96=D1=81=D1=82=D1=8C=2E</body></ht=
ml>
------3HCBPPKMTFM0A292BBATDPP0M801QC--


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---