OK, so what are the _blocking_ reasons for no EAPI 4 support in python.eclass yet?
I understand you have some complicated patches in flight etc etc, but are they _required_ for the eclass not to break with EAPI 4? My point is that I'd like to use pkg_pretend in packages that use python.eclass and I can't (for a long time). Unless there are really important reasons like breakages I think we should really make python.eclass support EAPI=4.
signature.asc
Description: OpenPGP digital signature
