[Zope-dev] Re: [z3-five] relocating Zope 2 core interfaces - a proposal

2005-05-06 Thread Martijn Faassen
yuppie wrote: [snip] Current State = Five (now part of Zope 2.8) ships with one big interfaces.py file that contains z3 interfaces for Zope 2 core classes. (There are also some five specific interfaces in that file, but they are not subject of this proposal.) interfaces.zcml states

[Zope-dev] Re: [z3-five] relocating Zope 2 core interfaces - a proposal

2005-05-06 Thread yuppie
Hi! Martijn Faassen wrote: yuppie wrote: [snip] Current State = Five (now part of Zope 2.8) ships with one big interfaces.py file that contains z3 interfaces for Zope 2 core classes. (There are also some five specific interfaces in that file, but they are not subject of this

[Zope-dev] Re: [z3-five] relocating Zope 2 core interfaces - a proposal

2005-05-06 Thread Philipp von Weitershausen
yuppie wrote: Current State = Five (now part of Zope 2.8) ships with one big interfaces.py file that contains z3 interfaces for Zope 2 core classes. (There are also some five specific interfaces in that file, but they are not subject of this proposal.) interfaces.zcml states that

[Zope-dev] Re: [z3-five] relocating Zope 2 core interfaces - a proposal

2005-05-06 Thread yuppie
Hi Philipp! Philipp von Weitershausen wrote: yuppie wrote: Seriously, you should merge your r11978 to the Five-1.0 branch.0 Martijn was faster than I thought :( I'll follow up to this in an other mail. I don't think we need to break backward compatability. We would just need to deprecate the

[Zope-dev] Re: [z3-five] relocating Zope 2 core interfaces - a proposal

2005-05-06 Thread Philipp von Weitershausen
yuppie wrote: I don't think we need to break backward compatability. We would just need to deprecate the Five.interfaces location. Basically, the goals are: * The solution needs to work with Zope 2.7 * Preferrably, the interface import spelling should be equal on both systems (which means a