no return values for __init__ ??
Aahz Maruch
aahz at netcom.com
Thu Jan 6 12:28:20 EST 2000
More information about the Python-list mailing list
Thu Jan 6 12:28:20 EST 2000
- Previous message (by thread): no return values for __init__ ??
- Next message (by thread): no return values for __init__ ??
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In article <3874CFE5.765A40EA at mdlink.de>, Helge Hess <helge.hess at mdlink.de> wrote: > >recently I was heavily wondering why __init__ does not allow return >values ! Is there any special reason not to do this ? Yup. The return value *has* to be the object instantiated by Python. Why do you want to do this? -- --- Aahz (@netcom.com) Androgynous poly kinky vanilla queer het <*> http://www.rahul.net/aahz/ Hugs and backrubs -- I break Rule 6 The problem with an ever-changing .sig is that you have to keep changing it.
- Previous message (by thread): no return values for __init__ ??
- Next message (by thread): no return values for __init__ ??
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list