Tres Seaver wrote:
> Hash: SHA1
> Martin Aspeli wrote:
>> Tres Seaver wrote:
>>> Thinking further on this:  there is actually not much "shiny" about the
>>> ZTK:  it is going to be equivalent to a cut-down, dependency-stripped,
>>> bbb-cruft-sanded version of the packages already shipping with Zope
>>> 2.10.x / 2.11.x.  Until Plone quits using Zope2 altogether (likely
>>> never, AFAIK) Plone has no direct interest in the ZTK, which is just a
>>> layer of the Zope2 stack from Plone's perspective.
>> In practice, though, people are using packages from newer Zope releases 
>> in third party products, and, possibly, in Plone core.
>> One example is z3c.form, which requires you to upgrade zope.i18n and 
>> zope.component That works fine, FWIW. :)
> But it won't be "supported".  Mix-and-match is not what the toolkit (or
> the related KGS / index stuff) is designed for.

Sure. Which is why I said it would be disappointing (as opposed to 
negligent) if Python 2.4 support were dropped. ;)


Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See

Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to