I haven't been able to figure out if upstream supports Python 3 or if it's planned
(In reply to Olof Kindgren from comment #0)
> I haven't been able to figure out if upstream supports Python 3 or if it's
So you're merely expressing a desire that the build system would one day support python3, or do you want downstream Gentoo to actively support what upstream as of now apparently does not?
This is primarily for the python3 tracking bug. Spidermonkey itself is a hard dependency of polkit so I suspect this might hold off python 2 removal for many installations.
As for the action to take, it sounds like a lot of work to fix this downstream, so the first course of action would be to see if upstream already supports py3 or has plans to do that. I started looking, but unfortunately I couldn't find any info and ran out of time for now to look deeper
SpiderMonkey is extracted from source code of Firefox.
Firefox upstream is already working on porting Firefox to Python 3. See bug #698978.
(In reply to Arfrever Frehtes Taifersar Arahesis from comment #3)
> SpiderMonkey is extracted from source code of Firefox.
> Firefox upstream is already working on porting Firefox to Python 3. See bug
In the tree of the upstream mirror at:
there I cannot see that much of the python .py scripts.
If that tree is self contained we could extract
from beneath the firefox source that Spidermonkey js/src
If we have difficulties to cut out the
SpiderMonkey correctly, we could lookup the needed
copy action on a new sub project at mozilla there:
They want to create a full blown NodeJs on top of SpiderMonkey.
For those interested: after fixing libmypaint (just merged, a dependency of GIMP) the last outstanding python2 dependency on my system was mozjs via polkit.
Someone was brave enough to port polkit to an alternative JS engine called duktape-2.x (in tree!), and the patch applies and works just fine on top of our existing polkit-0.116 ebuild.
I removed spidermonkey, enabled duktape and voila: spidermonkey & python2 are depcleaned. \o/
And yes, so far everything still seems to work, desktop/auth-wise. Beware that this is of course not (yet) an official patch, but it's a start.
Find the updated ebuild here: https://github.com/hhoffstaette/portage/commit/d3d70def05f79c8b4dec8b3d40404e7dfca482c5
Hi Holger Hoffstätte
I have used your idea and created the duktape flag to enable this feature:
dev-lang/spidermonkey-68.6.0 is python3-only and now is arch-masked (yesterday was hard-masked), but cannot upgrade to it because <=sys-auth/polkit-0.116-r1 depends on spidermonkey:60. Should I create separate ticket for upgrading polkit?
It's not python 3 only. Build system still requires Python2.7... only tests were ported to Python3.
you can track python3 porting here:
there's been a lot of activity recently with fixes landing in firefox-77 branch, so there's still hope ;-)
(In reply to Holger Hoffstätte from comment #5)
> For those interested: after fixing libmypaint (just merged, a dependency of
> GIMP) the last outstanding python2 dependency on my system was mozjs via
> Someone was brave enough to port polkit to an alternative JS engine called
> duktape-2.x (in tree!), and the patch applies and works just fine on top of
> our existing polkit-0.116 ebuild.
> I removed spidermonkey, enabled duktape and voila: spidermonkey & python2
> are depcleaned. \o/
> And yes, so far everything still seems to work, desktop/auth-wise. Beware
> that this is of course not (yet) an official patch, but it's a start.
> Find the updated ebuild here:
I'm trying your patch and it works perfectly. I suggest you to file a new bug proposing this for polkit
(In reply to cazzantonio from comment #10)
> I'm trying your patch and it works perfectly. I suggest you to file a new
> bug proposing this for polkit
+1, this works and would be a great improvement!
по хорошему, надо отправить bug сюда https://gitlab.freedesktop.org/polkit/polkit/-/issues
ну или merge request
I've created bug #734326 to be able to use duktape instead of spidermonkey in polkit.