Philipp von Weitershausen wrote: > Tres Seaver wrote: >>>> + @deprecate("The 'first' method has been deprecated and will disappear >>>> " >>>> + "in Zope 2.12. Use the 'start' property instead.") >>>> def first(self, name=None): >>>> if self.start: >>>> return True >>>> return not self.same_part(name, self._last, self.item) >>>> >>>> + @deprecate("The 'last' method has been deprecated and will disappear " >>>> + "in Zope 2.12. Use the 'end' property instead.") >>>> def last(self, name=None): >>>> if self.end: >>>> return True >>>> >> I don't think deprecating 'first' and 'last' is appropriate here: they >> *aren't* synonyms for 'start' and 'end; they are used to implement >> sort-break processing. Here is the comment from the checkin which >> initially documented them >> (http://mail.zope.org/pipermail/zpt/2001-December/002598.html): > > This sounds sensible. Thanks for the pointer. I'll undeprecate them :).
I'll add nonetheless that neither 'first' nor 'last' nor 'nextIndex' are required by the ZPT spec (http://www.zope.org/Wikis/DevSite/Projects/ZPT/RepeatVariable). Hence, Zope 3 just doesn't have them. I can still see a use case for 'first' and 'last' which is why I'll do my best to continue to support them. Philipp _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )