Hi,
I'd like to move to python3 for alpine v3.2.
Options how to do that:
- we use python3 and add lots of py3-* apkbuilds. This will add
maintenance work since you need upgrade 2 different packages each
upgrade. This is likely the easiest way to get started with.
- we use python3 and for every currently py-* apkbuild we add a py3-*
subpackage (or opposite). The point is that both python2 and python3
modules are built from same APKBUILD. this reduces maintenance of
modules but it will much work to update all current apkbuilds.
- we rename current python3 package to python and rebuild all py-*
packages with python 3. This means that we basically drop support for
python 2. If there are exceptions that we cannot port to python3,
then we could add py2-* packages for those. This will likely make the
migration for users a bit more painful than the other options.
Other ideas?
Any volunteers to work on this?
-nc
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
I think we should just have Python 3 in testing/ for now. So I am thinking Alpine 3.3 maybe try to do edge testing for 3.2 and see how many modules port. If we had an Nic package manager style we wouldn't have dependency conflicts for python2 vs python3 :P . Is there any semi-standard or Distro we should emulate on how to have python2 and python3 on the system (e.g. Arch)?
Sent from my iPhone
> On Jan 12, 2015, at 07:27, Natanael Copa <ncopa@alpinelinux.org> wrote:> > Hi,> > I'd like to move to python3 for alpine v3.2.> > Options how to do that:> > - we use python3 and add lots of py3-* apkbuilds. This will add> maintenance work since you need upgrade 2 different packages each> upgrade. This is likely the easiest way to get started with.> > - we use python3 and for every currently py-* apkbuild we add a py3-*> subpackage (or opposite). The point is that both python2 and python3> modules are built from same APKBUILD. this reduces maintenance of> modules but it will much work to update all current apkbuilds.> > - we rename current python3 package to python and rebuild all py-*> packages with python 3. This means that we basically drop support for> python 2. If there are exceptions that we cannot port to python3,> then we could add py2-* packages for those. This will likely make the> migration for users a bit more painful than the other options.> > Other ideas?> > Any volunteers to work on this?> > > -nc> > > ---> Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org> Help: alpine-devel+help@lists.alpinelinux.org> --->
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
On 01/12/2015 04:27 PM, Natanael Copa wrote:
> - we rename current python3 package to python and rebuild all py-*> packages with python 3. This means that we basically drop support for> python 2. If there are exceptions that we cannot port to python3,> then we could add py2-* packages for those. This will likely make the> migration for users a bit more painful than the other options.
I am on this. However, we need to determine details of the whole
migration. I think it is also a good idea to look over the repo for
APKGBUILDs of already abandoned projects and so on. Probably there is a
long way to go.
Łukasz