Date: Tue, 19 Mar 2019 13:08:46 +0100
From: Kevin Daudt <me@ikke.info>
To: Natanael Copa <ncopa@alpinelinux.org>
Cc: u-3qpt@aetey.se, Drew DeVault <sir@cmpwn.com>,
	alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Normalizing Python packages in aports
Message-ID: <20190319120846.GB18235@alpha>
References: <20190306212501.GD2800@cirno.localdomain>
 <20190314112413.29dd9816@ncopa-desktop.copa.dup.pw>
 <20190314191241.GF1544@homura.localdomain>
 <20190319103153.3964ded5@ncopa-desktop.copa.dup.pw>
 <20190319113230.GM23721@example.net>
 <20190319125738.73f31222@ncopa-desktop.copa.dup.pw>
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190319125738.73f31222@ncopa-desktop.copa.dup.pw>
User-Agent: Mutt/1.11.3 (2019-02-01)

On Tue, Mar 19, 2019 at 12:57:38PM +0100, Natanael Copa wrote:
> On Tue, 19 Mar 2019 12:32:30 +0100
> u-3qpt@aetey.se wrote:
> 
> > On Tue, Mar 19, 2019 at 10:31:53AM +0100, Natanael Copa wrote:
> > > Earler, before python3 was supported, all the py-* packages was
> > > python2. We should probably also look over all py-* packages and make
> > > sure that all python2 packages are renamed to py2-*.  
> > 
> > 2c from a lurker.
> > 
> > A large part of this thread looks dedicated to surviving a mess created
> > by the reuse of the same name "python" (also "py-" as a prefix or similar)
> > for different and incompatible softwares.
> > 
> > The problems would hardly exist if python2 and python3 worlds
> > were separated from the beginning.
> > 
> > That's why I would like to emphasize the need to always use strictly
> > specified references for the purposes of packaging.
> > 
> > In other words:
> > 
> > Do not use "default" names which change their meaning with time and
> > then their usage must be traced and adjusted everywhere (!)
> > 
> > From this point of view, it is important to (also) name all python3
> > packages as py3-*.
> 
> always name all python3 packages py3-* would also make it possible to
> install py4-* and py3-* in parallel if for some reason that would be
> needed in future.
> 
> python3.6 and python3.7 will not be possible to install in parallel.

I think we should make a difference between software and libraries. For
software, it should not matter what python version it is, they are
written against a specific version and just need the apropriate
dependencies.

Libraries ofcourse it does make sense to differentiate, because the
python interpreter is looking for those packages in it's library
directories.

In the end, it does make sense to phase out python2, because at some
point (at the moment January 2020), python 2.7 will be no longer
maintained.

Before that time, I don't think we should remove python 2 only packages,
but try to migrate as much as possible to python3. After that time, we
would need to make the choice to keep packages in the repo for a python
version that is no longer maintained.


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---