[Biopython-dev] Re: Abstract application wrapper

Brad Chapman chapmanb at arches.uga.edu
Sat Aug 4 10:51:13 EDT 2001


Hi Davide, Jeff;

[AbstractApplication ideas]

> I think it is really very nice!

Thanks, I'm glad that I used my time during that conference talk
productively :-)
 
> However I slightly prefer the lighter version in which you have a class
> 
> AbstractApplicationCommandLine (yes to be shortened) instead of
> AbstractApplication
> 
> where the only difference is that you do not have a run method and have
> also a __str__ method behaving as construct_commandline. (or maybe better
> something returning a list of strings?)

I've been thinking about your points while at work (I've got lots of
time to think while grinding up cactus), and I totally agree with
you. I like the idea of the class representing a command-line, and so
__str__ returns the string representation of that class (I do prefer
the actual commandline being returned over a list of string). So I
also think it would be better to just have an AbstractCommandLine
class that only represents the class, and then have the functions to
run the programs separate from the class.

[....snip... Lots of good justifications]
 
> Let me know what you think about it.

You've convinced me :-). I'd be very happy if you'd like to work on
this and get something together. Having a common way to deal with
command-lines would be very nice, and might convince us to get support
together for more programs :-)

Brad




More information about the Biopython-dev mailing list