colpage.py

[Skaperen]

Implicitly.  No one ever explicitly returns None for __init__ or indeed many functions at all.  I would say only explicitly return None on a function where that has meaning.  If your function changes a mutable it was passed or simply is setting attributes on a class it is customary to leave it off.  Functions with no explicit return statement will return None regardless.

This goes for almost every return in the code you posted, but as stated specifically jumps out for the init.

i do remember the thought i had when coding that.  i wanted it to be short and knew that geometry() returned None so it could put the call on the return statement.  but i have changed to not depend on that.  i did do an explicit return None in the __init__ method per post #8.  is there a reason you believe in that suggests or mandates that an implicit None is better, as in just return?