This is not for "pushing" you to support eapi4 just now, but I think we should have a bug for being able to track other bugs requiring eapi4 support in python.eclass and, then, being able to fix them as soon as eapi4 support is added to python eclass. Thanks a lot Reproducible: Always
I'm working on support for EAPI="4" and hopefully it will be ready soon.
Fixed in python overlay (in multiple revisions).
Thanks a lot Arfrever :-D
This has been fixed in gx86, too.
Sorry but the eclass in gx86 still dies when EAPI=4 in ebuilds inheriting this eclass. Please have a look at line 14 where it still only checks for EAPIs 0 to 3 Reopening this bug...
Any news? Packages depending on this still do not build.
There's an EAPI-4 python.eclass residing in openoffice-geki overlay.
Any progress on this? Since its show stopper for migration to eapi4
IIRC the eclass doesn't die anymore.