On Thu, Jun 06, 2002, Guido van Rossum wrote: > >>> class Element: >>> >>> def __str__(self): >>> pass >> >> Dunno about other people's opinions, but I have a strong distaste for >> creating methods whose body contains pass. I always use "raise >> NotImplementedError". > > But that has different semantics! Yes, exactly. My point was that one rarely wants the semantics of "pass" for method definitions, and that goes double or triple for the special methods such as __str__. Consider what happens to an application that calls str() on this object and gets back a None instead of a string. Blech -- errors should never pass silently. -- Aahz (aahz@pythoncraft.com) <*> http://www.pythoncraft.com/ "I had lots of reasonable theories about children myself, until I had some." --Michael Rios
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4