> Betreff: [Zope-dev] Deprecate ITerms in zope.app.form? [Re:
> >> A deprecation warning isn't bad. But I think we should not
> >> the use of ITerms from zope.app.form. I don't see a gain
> in this API
> >> change.
> > Imo it's a bad idea to keep exactly the same interface in 2
> places. At
> > least i don't see an improvement or convenience in keeping it.
> > the only real reason to keep it is for legacy reasons, but import
> > adoption should not be that hard ;)
> No it is not. I just question why we force everybody to use
> the new location when we did not do so with ISite. It is
> exactly the same issue with two different outcomes.
> The canonical location for ISite is zope.location now. It
> used to reside in zope.app.component but was moved to
> zope.location w/o deprecating the use from zope.app.location
> to keep the API backward compatible. I really do not see a
> differrence to ITerms here.
This doesn't have to do with bachward compatibility. Deprecated
imports are backward compatible too. I think someone just missed
to deprecate that interface.
The reason why we should deprecate interfaces is: If a package
still points to the old interface location, this package whould
bring in the old dependency we tried to remove.
I guess, since you are asking for support the old location,
this doesn't hurt you because you are using both packages.
Others don't. Any other packages which doesn't adjust the
import to the new location will hurt others which do not use
I see that this makes it more a good thing for others then
for yourself. But I think that's fine. Isn't it?
In my point of view, deprecation messages are a great concept
to announce changes/improvments without to break compatibility.
Without such announcements our code can get very quick out
of date and we have no change to know about that.
we also should deprecate the ISite interface at the old location.
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -