(May-01-2017, 05:00 PM)volcano63 Wrote: From object.__init__ documentation
Quote:Because __new__() and __init__() work together in constructing objects (__new__() to create it, and __init__() to customize it), no non-None value may be returned by __init__(); doing so will cause a TypeError to be raised at runtime.
Yes, that has been established. This discussion was as to whether or not you should explicitly include
return None
or even return
in said function. And of course, as established by convention (whether it be in pep8 or not) you should not.