On 15 Dec 2009, at 18:11, Jared Gisin wrote: > What's wrong with writing subclasses? I've never had a case where > that wasn't sufficient. Instead of filling up your files with all > of these empty class definitions that define the methods that > objects should implemmnt, why not just make the base object from > which all similar object inherit implement the required methods, and > if it's up to a subclass to provide functionality, just raise an > ImplementationError in the base class method and let it be a run- > time error. Keep it clean and simple and let Python do its work.
Wouldn't that be _more_ empty class definitions? _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
