Re: Dropping Python 2 (questions about python modules that are in python3 and python2 versions)

[Adolf Belka <adolf.belka@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 3592 bytes --]

Hi all,

Three of the python-xxx files listed for python2 already seem to have a python3 versions available in IPFire.


For python-six there is python3-six. Both are addons. Can python3-six replace python-six?

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 name. Searching in the git repository I found spice refers to needing python-six to be built but it is not mentioned in the spice source install instructions under either mandatory or optional dependencies for building.


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 version is 0.17.1

Could python3-docutils be made into a core program and updated and python-docutils removed?



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 are 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 installation is running a .egg file via the bash command.

Can python-setuptools just be removed without creating an equivalent python3 version or is it being used/required somewhere that I have been unable to identify?


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 receive 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 change 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 there 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 does not seem to be too difficult.
>
> Would anyone be up to help and remove Python from any of those packages above? I would like to aim for Core Update 158 and remove as much stuff as possible - if we can everything - and then remove Python 2 in the update after that. If anyone has any custom scripts or applications, people will have some time to migrate away.
>
> Best,
> -Michael