It is true for 2.6 unless you use various from __future__ imports, which
I consider a form of contortion.

Even with 2.6 I don't see how you can specify a metaclass without doing
something weird like

  foo = MyMetaclass('foo', bases_tuple, namespace_dict)

which is hardly an improvement over either the 2.x or 3.0 syntax.

Given that it will always be true for 2.5, I don't want to back down.