Date: Fri, 3 Jun 2016 12:12:28 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: =?ISO-8859-1?B?QmFydCpvbWllag==?= Piotrowski <b@bpiotrowski.pl>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Python 3 in Alpine 3.5
Message-ID: <20160603121228.5d26f586@ncopa-desktop.alpinelinux.org>
In-Reply-To: <a58597d021c9b6da1284fa0ce62235f5@server-speed.net>
References: <a58597d021c9b6da1284fa0ce62235f5@server-speed.net>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, 02 Jun 2016 12:29:17 +0200
Bart*omiej Piotrowski <b@bpiotrowski.pl> wrote:

> Hi all,
>=20
> we already discussed Python 3 support at least 3 times. As we recently
> released new stable series, edge is again open for all happy breakage
> so let's make use of it.
>=20
> Before I start though, I ran a simple grep on aports and it turns out
> there are 575 packages providing various Python libraries. I think this
> is much beyond our resources to keep all of them up to date, including
> possible security fixes.  Following recent Ruby example, I would love to
> limit this set to only very popular libraries (Flask, Requests, etc) and
> these that require to be patched to successfully build (numpy). I can=20
> also
> see an exception for all compiled libraries. The question is how to=20
> measure
> popularity; if that becomes a concern, I would rather drop all pure=20
> Python
> modules instead.

The difference between python and ruby module packages is that python
are much easier to package an maintain. Upgrading python packages is
fast too, so I actually don't mind keeping then.

Ruby packages on the other hand was almost impossible to maintain,
which is why they got removed.
=20
> I have no idea what to do with tools. We probably should leave them with
> dependencies, preferably using Python 3.

I suppose the biggest job is to figure out what to keep and what to
remove. I suspect there will be complains as soon as we start remove
python packages. There were very few complains when we removed ruby, I
suspect that nobody used them (because they were likely broken).

>=20
> With all of the above done, it would ease Python 3 transition a lot. I=20
> am
> thinking of renaming all py-* packages to py2-* and then add py3-*
> subpackages where applicable. Then we can open a champagne bottle and=20
> celebrate.
>=20
> I want to gather your opinions before I start pushing anything to=20
> master.

Sounds good. so to repeat:

1. clean up. (figure out what we can remove and remove it)
2. rename py-* to py2-*
3. add py3-*




---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---