On Thu, Oct 1, 2009 at 1:02 PM, Martin Aspeli <
[hidden email]> wrote:
> Wichert Akkerman wrote:
>> I saw Hanno made several commits yesterday which broke python 2.4
>> support for recent branches of several packages. I am wondering if that
>> is acceptable. We have a long history of people using newer releases or
>> backports in older Plone versions, and these kind of changes make that
>> needlessly harder. Can we please try to keep python 2.4 support for
>> another release or two?
>
> What is the cost of keeping Python 2.4 support?
It depends on the package. There are some packages where we make a
number of Zope 2.12-only changes, like changing interfaces over to
zope.interfaces and removing support for the old Zope2 Interfaces. Or
depending on the ZTK refactoring and using new packages. In these
cases I don't see keeping Python 2.4 support as a goal. There are
packages where we make so many changes at once, that using them in
Plone 3.x won't work anyways.
There are other cases where we depend on external packages like
elementtree or simplejson. Both of these are now part of Python
itself. So it makes sense to avoid the external dependency and
additional code and instead use the version in Python itself. Packages
with those kind of dependencies should be allowed to require Python
2.6 IMO.
> Which packages are we talking about?
Two changes I made yesterday, could for the time being be made to work
easily in Python 2.4. PasswordResetTool for example just had an import
statement for hashlib vs. md5. Instead of the bare try/except I
removed, one could just use a try/except ImportError.
In general there are new major versions of packages like Archetypes,
ATContentTypes, plone.app.layout which are unreasonable to use in
older versions of Plone. But we could try to allow the less
intermingled / dependent packages to stay somewhat more backwards
compatible. The plone.* packages would be a good example for these.
> As far as I know, Zope 2.12 doesn't support Python 2.4 anymore (they
> tried, unofficially, but I think it was abandoned?).
The official story is: It's unsupported, but it might work. Use at
your own risk.
Hanno
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf_______________________________________________
Plone-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-developers
