Deprecations when interfaces changed (was Re: [Zope3-dev] Re: Usage of IAnnotations disrespects interface declaration)

2006-12-17 Thread Dieter Maurer
Christian Theune wrote at 2006-12-17 11:34 +0100: > ... >Jupp. Is there any technical chance the we can use the deprecation mechanism >or something like this to inform developers that they are not fully >complying to a changed contract? > >Still, for me it feels like the original interface should h

Re: [Zope3-dev] Re: Usage of IAnnotations disrespects interface declaration

2006-12-17 Thread Christian Theune
On Sun, December 17, 2006 10:27 am, Dieter Maurer wrote: > Christian Theune wrote at 2006-12-11 08:30 +0100: >> ... >>> Both are not acceptable, especially option #1. We can't just change >>> existing contracts as we see fit. >> >>Right. However, I think it's possible to regard this is a bug in the

Re: [Zope3-dev] Re: Usage of IAnnotations disrespects interface declaration

2006-12-17 Thread Dieter Maurer
Christian Theune wrote at 2006-12-11 08:30 +0100: > ... >> Both are not acceptable, especially option #1. We can't just change >> existing contracts as we see fit. > >Right. However, I think it's possible to regard this is a bug in the >original contract. But, some adapters for "IAnnotations" may

Re: [Zope3-dev] Re: Usage of IAnnotations disrespects interface declaration

2006-12-10 Thread Christian Theune
Good Morning, Philipp von Weitershausen wrote: > In the issue you write: > >> I can see two ways: >> >> 1. Extend the IAnnotations interface to grow the necessary >> methods and support the existing use cases >> >> 2. Remove the ability from the existing attribute annotation >> and re-write t