From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Dropping Python 2 (python-optional-src) Date: Sat, 15 May 2021 10:41:38 +0200 Message-ID: <8c40a65a-cb5c-895a-576f-33c9ea093b0b@ipfire.org> In-Reply-To: <4416eb2b-13be-2885-df3e-fc9308b1169e@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0900465195297294802==" List-Id: --===============0900465195297294802== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All, On 15/05/2021 10:28, Adolf Belka wrote: > Hi All, > > I just had a look at python-optional-src for converting to python3 but foun= d most of it is not present. > > There is an lfs file but it does not mention the source file and there are = no build instructions. > > python-optional-src is not in make.sh so it is not getting built anyway. > > There is no rootfile for python-optional-src > Error in my first message. There is a rootfile in packages. grepping for "imp= ort optional-src" or "from optional-src import" in the build doesn't flag any= thing up. So I still believe it can be removed. > I think this lfs can just be deleted. I will raise a patch for this unless = I hear something different. > > > 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 c= onference call this week: Dropping Python 2 >> >> 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. >> >> However, there is lots of software that still depends on it which has to b= e 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 b= it more difficult to migrate. We would also have to be very careful to not ch= ange 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 bindings. >> >> 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. >> >> 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. >> >> Best, >> -Michael --===============0900465195297294802==--