A future import is not much of a contortion, and metaclasses is not
exactly an everyday occurrence, after 9 years of python I have yet to
write a metaclass...

Of course I don't like that it specifically mentiones 2.6, while 2.6 has
lot's of forwards compatibility just to make it possible to write code
that runs under both. It will always be true for 2.5, and then we could
fix the issue by changing 2.6 to 2.5. 

If you want to keep the statement for 2.6, it could possibly be
reformulated less strongly, or as a minimum change come up with another
example than something that actually has a forward compatibility in 2.6.