Odd handling of type.__init__ bases

[quick at sparq.org]

I encountered an oddity in attempting to use a metaclass to perform mix-in 
inheritance for classes.  I've attached a small demonstration file.  Have I 
misunderstood the bases argument for type.__init__ or should this be submitted 
as a bug?

Python 2.5 (r25:51908, Feb 22 2007, 19:05:27) 
[GCC 4.1.2] on linux2

-KQ





-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pyclass.py
Type: application/octet-stream
Size: 574 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-list/attachments/20080228/9cbeb13b/attachment.obj>