Re: Class __init__ behaviour

2006-04-20 Thread Lou Pecora
In article <[EMAIL PROTECTED]>, "Thomas Bartkus" <[EMAIL PROTECTED]> wrote: > If I insert an __init__ method in my own class definition, it is incumbent > upon me to call the __init__ of any declared ancester to my new class object > because my __init__ will override that of any ancester I declar

Re: Class __init__ behaviour

2006-04-20 Thread Diez B. Roggisch
Thomas Bartkus schrieb: > If I insert an __init__ method in my own class definition, it is incumbent > upon me to call the __init__ of any declared ancester to my new class object > because my __init__ will override that of any ancester I declare in the > header. If I fail to call the ancesters __

Class __init__ behaviour

2006-04-20 Thread Thomas Bartkus
If I insert an __init__ method in my own class definition, it is incumbent upon me to call the __init__ of any declared ancester to my new class object because my __init__ will override that of any ancester I declare in the header. If I fail to call the ancesters __init__, then it won't happen. Th