> Please don't try to blur the line between module and class. This has > been proposed many times, and the net result IMO is always more > confusion and no more power. This is also why in 2.3, modules are no > longer subclassable. Loud and clear! > (I would explain more about *why* I think it's a really bad idea, but > I'm officially on vacation.) "There should be one-- and preferably only one --obvious way to do it" if I had to guess. Happy holidays. -troy
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