Python 2 reached upstream end-of-life in January 2020. In Fedora Rawhide, it's now provided from the compat package `python27`.
Packages that only use Python 2 at build time, like firefox, had a general exception to keep using it in Fedora 31. Now, the dependency should be removed.
Let us know if you need any help investigating or removing the dependency. (There are dozens of packages like this, so we didn't investigate this one thoroughly. We assume you know the package best.)
If it's possible that the dependency won't be removed in Fedora 33. Please request a FESCo exception. You can refer to the exception for mercurial as an example: https://pagure.io/fesco/issue/2243
It's good to mention:
- What is the reason for the Python 2 build dependency?
- What are the upstream/community plans/timelines regarding Python 2?
- What is the guidance for porting the build to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?)
If you need anything from us, or something is unclear, please mention it here.
Firefox does not build yet with Python2:
Upstream Python3 migration notes :
"In mozilla-central there are over 3500 Python files (excluding third party files), comprising roughly 230k lines of code. Most of it is Python 2"
If python2.7 is removed from Fedora we'd need to bundle it with Firefox sources as well as we do that for firefox on RHEL6. Perhaps we don't need system wide python in this case. We're not going to port Firefox build scripts to python3 as we have lot of other work to do.
Thanks for the wiki link and sharing the plans!
In Fedora, it would make sense to continue maintaining the python2 package separately, rather than bundle it in Firefox.
But we do want to track the situation, gather info and coordinate (and we use these bugzillas and FESCo exceptions for that).
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.
I see that this is fixed at least in the Rawhide build. Thank you!