Foreign branch infrastructure plans

[Robert Collins]

On Fri, 2009-03-13 at 15:16 +1100, Martin Pool wrote:
> 
> It's only a bit related but I'd like to move more towards having clean
> hierarchies for the main components.  I'm thinking we should have one
> base which only defines the interface and is purely abstract, and then
> a subclass that provides 'reasonable defaults' for methods (like
> "return False" for supports_foo()), or building more complex methods
> on more primitive ones.  At the moment they're a bit mixed up.

I don't think an ABC per se is useful for us. What we have issues with
are:
 - when self-referential convenience methods are defined too low down
 - when sensible defaults are not sensible :)

So I'd like it if we moved all the convenience methods higher up the
stack, and have things that provide defaults always raise
NotImplementedError  at the same level that the convenience methods are
defined.

This may be just what you meant, of course.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090316/da12d3ae/attachment.pgp