[Zope-Checkins] CVS: Zope3/lib/python/Interface - __init__.py:1.9

[Guido van Rossum]

> > > Modified Files:
> > > 	__init__.py 
> > > Log Message:
> > > Stamp out the last uses of Interface.Base.
> > 
> > I got this message on 'zope-checkins', which would notionally mean that
> > it involves a module which is shared between Zope2 and Zope3.  If so,
> > this checkin will break virtually every Zope2 application which uses
> > interfaces at all.
> 
> /cvs-repository/Zope27/lib/python/Interface is a link to 
> /cvs-repository/Packages3/Interface , so they share that particular 
> __init__.py, and Zope27/* checkins are directed to the zope-checkins list.  
> 
> (It also happens to be the case that /cvs-repository/ZODB4/Interface is a 
> link to /cvs-repository/Packages3/Interface, but i don't think ZODB4 has 
> any notification handlers.)
> 
> > I just looked, and it doesn't appear to be a problem, in which case we
> > need to fix the routing for the mailing lists so that
> > /cvs-repository/Zope3/lib/python/Interfaces traffic goes only to
> > zope3-checkins.
> 
> Perhaps it's a problem for the Zope 2.7 branch - but if they're sharing 
> the Interfaces directory, perhaps Zope 2.7 isn't sensitive to the problem 
> you're describing.

I made the checkin in the Zope3 repository, under the assumption that
Zope3's codebase is completely separate from Zope2's.  Apparently
that's not the case.  I fixed a few places in the Zope3 codebase that
were still using Interface.Base (I found them by removing the
definition of Base from __init__.py).  I presume there are also still
places in the Zope 2.7 codebase that still use Interface.Base.  The
Zope 2.7 people can choose to fix those places, or they can add
Interface.Base back to the __init__.py file (though in the latter
case, I doubt the wisdom of sharing the Interface package between Zope
2.7 and Zope3).

--Guido van Rossum (home page: http://www.python.org/~guido/)