Wow, I just took a look at the roadmap and deciding what to do about api.named was one of two remaining tasks before releasing 0.9.5! Crazy!
I really don’t want to do any more deprecation after this release, so I’ll also be doing an API review to make sure that there’s no warts or anything still out there. I’ll let you know if I find anything.
After 1.0, the strategy ought to be: anything that is in the documentation should not have any breaking changes made to it. We’ll probably not be able to be perfect about this, so we’ll be as conservative as possible about migration. Anything that’s not in the documentation, or is explicitly declared internal, is internal and might change at any time. Bewarez!
PEP-387 is a good basis, but I think we can be more consistent about maintaining compatibility only with documented interfaces, simply because we have such comprehensive documentation already.
Anyway, all that is to say, we’re gonna try real hard to keep things non-broken for everyone. Namaste!
