[IronPython] __init__ ignored in favor of base class constructor? - blocker

Dino Viehland dinov at microsoft.com
Mon Dec 1 20:22:43 CET 2008


Thanks for opening this - I'm going to look at this and the other subclassing issues and see how scary the fix(es) are.

-----Original Message-----
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Dan Eloff
Sent: Monday, December 01, 2008 11:15 AM
To: Discussion of IronPython
Subject: Re: [IronPython] __init__ ignored in favor of base class constructor? - blocker

On Mon, Dec 1, 2008 at 10:41 AM, Michael Foord
<fuzzyman at voidspace.org.uk> wrote:
>
> Looks like the subclassing bug *again*. :-)
>
> (i.e. it looks like  Theme.__new__(...) is actually being diverted back to
> MyTheme.__new__(...))
>
> Michael
>

I suspect this is the same bug you resolver guys have been reporting
recently, but I reported this at
http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=20021
just to be thorough.

-Dan
_______________________________________________
Users mailing list
Users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com



More information about the Ironpython-users mailing list