Having a handler is still necessary, but the other information (e.g. long
name, short name, type, action) don't make sense, since type and name are
already included at the Command level.

Sent from my phone.
On Oct 11, 2013 4:35 PM, "Daniel McDonald" <notifications@github.com> wrote:

> In pyqi/core/interfaces/optparse/__init__.py:
>
> >  from pyqi.core.factory import general_factory
> >  from pyqi.core.exception import IncompetentDeveloperError
> >  from pyqi.core.command import Parameter
> >
> > -class OptparseResult(InterfaceResult):
> > -    def _validate_result(self):
> > +class OptparseResult(InterfaceOption):
>
> How does the optparse interface know what to do with the return without a
> handler? On Fri, Oct 11, 2013 at 2:26 PM, Jai Ram Rideout <
> notifications@github.com>wrote:
> … <#141a93b8bfd0a59b_>
>  In pyqi/core/interfaces/optparse/__init__.py: > from pyqi.core.factory
> import general_factory > from pyqi.core.exception import
> IncompetentDeveloperError > from pyqi.core.command import Parameter > >
> -class OptparseResult(InterfaceResult): > - def _validate_result(self): >
> +class OptparseResult(InterfaceOption): I think we're misunderstanding each
> other- I agree that having this information is important at the Command
> level (i.e. CommandOut objects), but not sure it fits well at the optparse
> level for results that are not associated with an optparse option (like the
> biom example). Maybe things will become clearer once you implement the
> inheritance hierarchy. It may also be easier to chat about this stuff on
> Skype sometime next week. — Reply to this email directly or view it on
> GitHub<https://github.com/bipy/pyqi/pull/193/files#r6925820> .
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/bipy/pyqi/pull/193/files#r6926072>
> .
>