Chris McDonough wrote: > I think the breakage, although literally "incalculable" (as is
every change to Zope 2, given that it has no canonical API), would be manageable given enough lead time. In fact, if we did change the module name, we could just leave a "bruce" package in place that, when imported, raised a "ObsoleteError" with a descriptive message.
But I think that this is a big problem. Backward compatibility for Z2 *is* important. It's too bad that lots of test files have to import Zope. Sigh.
Why is that a *big* problem?
- It's not nice to break tests, but that doesn't necessarily mean the products are broken.
- AFAICT many products need some polishing and a new release for Zope 2.8 anyway.
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce