On Jan 29, 2008 12:56 AM, Michael G Schwern <[EMAIL PROTECTED]> wrote: > 2) The most common mistake is forgetting about dependent actions when you do > a complete override, and that's not documented anywhere.
Sure it's documented -- it's documented in the code. I can't imagine doing a complete override of a function and not actually looking to see what happens in that function that I'm replacing. > Some dependencies are more complicated, like testcover depends on code, then > does some work, then "depends on" test when in reality it doesn't really > depend on the test action but overrides its behavior. testdb is similar. > Either way, complex cases like this can still be handled, depends_for() is a > convenience, not a replacement for depends_on(). Should depends_on change the list of dependencies? David
