Tres Seaver wrote:
The "burden of proof" *is* the work you just signed up the "preserve 2.4" group for: monitoring the packages they care about for things which break under 2.4, and proposing 2.4-compatible fixes.
Sure. That's different to saying officially that ZTK does not support Python 2.4, though, which is where we were going before.
Note as well that the mere presence of certain kinds of BBB code is a burden on the core maintainers. Conditional imports, for instance, create untestable code paths, as do other kinds of "capability" checks. Removing that kind of cruft increases the quality of the codebase, at the expense of backward compatibility.
Agree. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book