From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Dropping Python 2 (problems with libxml2 and libxslt) Date: Tue, 11 May 2021 15:31:53 +0200 Message-ID: <22ccbb7b-aba4-eeca-146f-98680fdd7231@ipfire.org> In-Reply-To: <7A982478-7F32-48D4-99B2-27A5CA9828EE@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6486519369905052418==" List-Id: --===============6486519369905052418== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 11/05/2021 15:25, Michael Tremer wrote: > Hello, >=20 > Did you try =E2=80=94-disable-python? I found that command but I was trying to get the python3 versions because the= python2 versions existed currently. >=20 > I am not aware that we need the Python modules. If the python modules are not needed then that makes these two modules much e= asier to deal with. Thanks for the clarification. Adolf. >=20 > -Michael >=20 >> On 11 May 2021, at 14:24, Adolf Belka wrote: >> >> Hi All, >> >> Problems trying to update libxml2 and libxslt from python2 to python3. >> >> Using --with-python=3Dpython3 in the configure section gives the result of= unknown command and it builds with python2. >> >> Using PYTHON=3Dpython3 before the ./configure command is ignored by the co= nfigure process and it builds with python2. >> >> There is a python3 version of libxml2 available in PyPI but it was release= d in 2018 and nothing since then. >> >> It looks like both libxml2 and libxslt only do their python bits in python= 2. Not running python at all would still give the libxml2 and libxslt librari= es but would miss out the uncommented python lines in the rootfile:- >> >> usr/lib/python2.7/site-packages/drv_libxml2.py >> usr/lib/python2.7/site-packages/libxml2.py >> #usr/lib/python2.7/site-packages/libxml2mod.la >> usr/lib/python2.7/site-packages/libxml2mod.so >> >> >> usr/lib/python2.7/site-packages/libxml2.pyc >> #usr/lib/python2.7/site-packages/libxslt.py >> #usr/lib/python2.7/site-packages/libxsltmod.a >> #usr/lib/python2.7/site-packages/libxsltmod.la >> usr/lib/python2.7/site-packages/libxsltmod.so >> >> >> I can't tell if missing those would be a problem. >> >> I also can't tell if there is any alternative way around libxml2/libxslt w= ith python3 or not and if this means that python 2 needs to stay for these tw= o libraries. >> >> >> Regards, >> >> Adolf. >> >> On 05/05/2021 16:27, Michael Tremer wrote: >>> Hello, >>> >>> I would like to talk about what has been discussed at the last developer = conference call this week: Dropping Python 2 >>> >>> This version of Python has reached its end of life and will no longer rec= eive any security fixes. Hence we need to get rid of it as soon as possible. >>> >>> However, there is lots of software that still depends on it which has to = be migrated away first. >>> >>> There are at least the following packages: >>> >>> 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 >>> >>> We also have the following scripts: >>> >>> config/ca-certificates/certdata2pem.py >>> config/unbound/unbound-dhcp-leases-bridge >>> >>> Fireinfo is written by us and has a lot of C which will make it a little = bit more difficult to migrate. We would also have to be very careful to not c= hange any behaviour of the current implementation. >>> >>> 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 binding= s. >>> >>> Ultimately we might need to keep Python around in the build system if the= re are other packages that rely on it. However, it would be great if we were = able to remove it from the distribution very soon. Looking at his list, it do= es not seem to be too difficult. >>> >>> Would anyone be up to help and remove Python from any of those packages a= bove? I would like to aim for Core Update 158 and remove as much stuff as pos= sible - if we can everything - and then remove Python 2 in the update after t= hat. If anyone has any custom scripts or applications, people will have some = time to migrate away. >>> >>> Best, >>> -Michael >=20 --===============6486519369905052418==--