[Biopython-dev] interface/SQL development policies

James Casbon j.a.casbon at qmul.ac.uk
Wed Aug 18 12:14:21 EDT 2004


> > * the two classes imply a common interface X, what is the best way of
> > handling this in python?  An abstract base class?
>
> Separate classes, the interface being checked via unit tests

As the classes have developed, it has become apparent there is identical code 
in both classes which is independent of the implementation of the backend.

In the light of this, an abstract class with some defined methods becomes more 
appealing, or should the common functionality be moved out of the class?

james

-- 
James Casbon

PhD Student
Centre for Infectious Disease
Institute of Cell and Molecular Science
Barts and The London

http://compbio.mds.qmw.ac.uk



More information about the Biopython-dev mailing list