From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: Dropping Python 2 Date: Wed, 05 May 2021 23:30:27 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8592073801665556386==" List-Id: --===============8592073801665556386== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, > On 5 May 2021, at 17:49, Adolf Belka wrote: >=20 > Hi Michael, >=20 > I am up for helping. I suspect the ones written in python2 that need to be = converted to python3 might not be so good for me. I have never programmed in = python at all. >=20 > I will have a go with some of the packages and see how things go. Yeah, so with most of the packages, we would need to disable Python 2 and ena= ble Python 3. That is it. No programming. > I can start with something like fetchmail and see if I run into any problem= s or not. Yes! Brilliant :) -Michael > Regards, >=20 > Adolf. >=20 >=20 > On 05/05/2021 16:27, Michael Tremer wrote: >> Hello, >>=20 >> I would like to talk about what has been discussed at the last developer c= onference call this week: Dropping Python 2 >>=20 >> This version of Python has reached its end of life and will no longer rece= ive any security fixes. Hence we need to get rid of it as soon as possible. >>=20 >> However, there is lots of software that still depends on it which has to b= e migrated away first. >>=20 >> There are at least the following packages: >>=20 >> boost >> fetchmail >> fireinfo >> iotop >> ipaddr >> libxml2 >> libxslt >> newt >> nmap >> python >> python-clientform >> python-daemon >> python-distutils >> python-distutils-extra >> python-docutils >> python-feedparser >> python-inotify >> python-ipaddress >> python-m2crypto >> python-mechanize >> python-optional-src >> python-pyparsing >> python-rssdler >> python-setuptools >> python-six >> python-typing >>=20 >> We also have the following scripts: >>=20 >> config/ca-certificates/certdata2pem.py >> config/unbound/unbound-dhcp-leases-bridge >>=20 >> Fireinfo is written by us and has a lot of C which will make it a little b= it more difficult to migrate. We would also have to be very careful to not ch= ange any behaviour of the current implementation. >>=20 >> The rest is probably either software that is entirely written in Python 2 = or software that brings bindings for Python. The latter case is easy because = we can either force it to build with Python 3 or we just disable the bindings. >>=20 >> Ultimately we might need to keep Python around in the build system if ther= e are other packages that rely on it. However, it would be great if we were a= ble to remove it from the distribution very soon. Looking at his list, it doe= s not seem to be too difficult. >>=20 >> Would anyone be up to help and remove Python from any of those packages ab= ove? I would like to aim for Core Update 158 and remove as much stuff as poss= ible - if we can everything - and then remove Python 2 in the update after th= at. If anyone has any custom scripts or applications, people will have some t= ime to migrate away. >>=20 >> Best, >> -Michael >=20 > --=20 > Sent from my laptop >=20 --===============8592073801665556386==--