Possibly, but not necessarily. There are two reasons for
``no_requirements``, the first being to explicitly indicate a method does
not have any requirements and second, to tag the method so that it can
properly be identified as a workflow method to be used during execution.
I'll review the tagging system though and see if there is a straightforward
alternative


On Mon, Feb 10, 2014 at 8:25 AM, Jai Ram Rideout
<notifications@github.com>wrote:

> In bipy/core/workflow.py:
>
> > +
> > +Construct arbitrarily complex workflows in which the specific methods run are
> > +determined at runtime. These methods are applied to items that are assumed to
> > +be independent.
> > +
> > +As an example:
> > +
> > +class MyWorkflow(Workflow):
> > +    def _allocate_final_state(self):
> > +        self.final_state = None
> > +
> > +    def _sanity_check(self):
> > +        pass
> > +
> > +    @priority(100)
> > +    @no_requirements
>
> Can @no_requirements be removed, so that if a workflow method is not
> decorated with @requires, it is assumed that there are no requirements
> for the method? This would be consistent with the handling of @priority(if it isn't present, a default priority of 0 is used).
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/biocore/bipy/pull/84/files#r9587147>
> .
>