From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonatan Schlag To: development@lists.ipfire.org Subject: Re: Dropping Python 2 (questions about python modules that are in python3 and python2 versions) Date: Wed, 12 May 2021 20:34:39 +0200 Message-ID: <2E5E06D8-27FF-41EA-905B-A313E07DBFFD@ipfire.org> In-Reply-To: <70cc7675-ebe1-2750-db48-f4a29983a526@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0197670757712205808==" List-Id: --===============0197670757712205808== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, > Am 11.05.2021 um 14:18 schrieb Adolf Belka : >=20 > =EF=BB=BFHi all, >=20 > Three of the python-xxx files listed for python2 already seem to have a pyt= hon3 versions available in IPFire. >=20 >=20 > For python-six there is python3-six. Both are addons. Can python3-six repla= ce python-six? >=20 > Both python-six and python3-six appear to be the same source file but just = a different version number 1.10.0 vs 1.14.0 and they have a different PROG na= me. Searching in the git repository I found spice refers to needing python-si= x to be built but it is not mentioned in the spice source install instruction= s under either mandatory or optional dependencies for building. >=20 So the easiest way to try would be to disable python-six and doing a clean bu= ild. If nothing needs it it can be dropped. Otherwise you could give the pyth= on3 version a try. >=20 > For python-docutils there is python3-docutils. They again appear to be the = same filename but different versions. python-docutils is version 0.12 and is = a core program. python3-docutils is version 0.14 and is an addon. Current ver= sion is 0.17.1 >=20 > Could python3-docutils be made into a core program and updated and python-d= ocutils removed? >=20 Seem to be added because of python daemon, so I would update this package fir= st and then see what happen. Greetings Jonatan >=20 >=20 > There is python-setuptools and python3-setupttols-scm. These do look to be = different files. Both are addons and grepping in the git repository neither a= re dependencies for any other package as far as I can find. Python-setuptools= also appears to be a very old version of setuptools at 0.6c11 and the instal= lation is running a .egg file via the bash command. >=20 > Can python-setuptools just be removed without creating an equivalent python= 3 version or is it being used/required somewhere that I have been unable to i= dentify? >=20 >=20 > 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 --===============0197670757712205808==--