On Sun, 24 Oct 2010 23:47:56 +0200
Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org> wrote:
> > > Usage of new EAPIs in the tree is not allowed before council
> > > approval.
> > python.eclass doesn't use any EAPIs, it only provides support for
> > ebuilds, which use given EAPIs (without EAPI="4").
> I forgot to say that this patch doesn't introduce usage of any
> feature absent in EAPI="3" and present in current draft of EAPI="4",
> but changes API of python.eclass in EAPI="4".
For all we know, EAPI 4 may be completely changed next week and then
allowed in the tree the week after. Then people looking at your eclass
will incorrectly assume that it supports the approved EAPI 4.
EAPI 4's current state used to be "closed, and approved subject to
Portage implementation", but due to the huge delays in that there have
been a number of things since then that the Council has voted on that
no-one has provided PMS patches or even approximate wording for. Unless
you've been keeping very close track of that, you don't even know what
EAPI 4 is likely to contain, let alone what it eventually will