1756371 - Python3 building support

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, enhancement)

Description

[Myckel Habets]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 SeaMonkey/2.53.10.2

Expected results:

Python2.7 is EoL and Seamonkey is one of the few packages on my distro (Gentoo) that requires it for building. The distro devs would like to see python2 go.

What is the state of Python 3 building support in Seamonkey?

Comment 1

[Frank-Rainer Grahl (:frg)]

The build files are at about Mozilla 62 with additional fixes. Whenever I have time I update them to a later level. I don't have a timeframe. Not enough devs around who backport stuff unfortunately.

Comment 2

[Edmund Wong (:ewong)]

Will see if I can work on this. It's been a crap-long time since I've touched this so it'll be some time.

Comment 3

[Frank-Rainer Grahl (:frg)]

Myckel is on it. We likely need only backports which we don't track because this already works in our comm-central builds. Keeping bug open in case something 2.53 specfic is needed.

Comment 4

[Ken Moffat]

Trying 2.53.14 with python-3.10 there are (at least) imports of Iter and Mapping from collections in the python code. These were apparently deprecated in 3.9 and removed in 3.10. Online suggestions are that they are in collections.abc but as a non-pythonista I failed to get what looked like an obvious change in mach/main.py to work.

Comment 5

[Ken Moffat]

Sorry, can't type. s/Iter/Iterable/

Comment 6

[Myckel Habets]

Yes, the fixes for this issue are in the patch queue (https://gitlab.com/frg/seamonkey-253-patches.git, see mozilla-release/patches/TOP-NOBUG-PLASTER-PY310_support-25314.patch) and add fixes for this on the go, when I encounter them. These are relative simple to fix.

Python 3 doesn't work yet, although I think we're getting close. Current large road block is webext type of translation support getting in.

Comment 7

[Tristan Miller]

What's the relationship between this bug and Bug 1635849? Is this a duplicate?

Comment 8

[Myckel Habets]

That bug was only a very small subset of all the work that was needed to get the building working on Python 3. That bug handled only the Makefile calls to some python scripts. The real work was to have all the python scripts themselves patched to being able to be run by Python 3.

Comment 9

[Tristan Miller]

In that case, perhaps someone could retitle Bug 1635849 so that it doesn't give the impression that it has solved the Python 3 issue once and for all. I think this overly broad title is what led to my confusion concerning this bug, and with the release notes of the 2.53.17 beta, as documented in Bug 1840074.

Comment 10

[Frank-Rainer Grahl (:frg)]

I think this bug is no longer needed. 2.53.17b1 no longer needs python 2. There are still a few loose ends outside normal building but they either need missing backports or are specific to the 2.53 branch and need to be fixed on a case by case base.