sean.upton at uniontrib
Oct 24, 2001, 9:09 AM
Post #3 of 8
You will get conservative-implementation folks who have a lot of production
infrastructure still on Zope 2.3.x and Python 1.5.2 (like me, right now);
that said, I think the best approach is to release an 2.3.x/1.5.2 compatible
interim release with your proxy speedups, see if the expat leak bug (is that
fixed yet, and better yet, what is the nature of the problem?) can be fixed.
Label that release as the 'last' ParsedXML release supporting Python 1.5.2
and Zope 2.3.x. I think that is fair, then move on, supporting only new
releases of Zope/Python.
From: Martijn Faassen [mailto:faassen [at] vet]
Sent: Wednesday, October 24, 2001 8:35 AM
To: zope-xml [at] zope
Subject: [Zope-xml] straw poll: ParsedXML requirements
I'd like to hold an informal poll on requirements for any new release of
ParsedXML. There was some discussion on whether it should continue to
support Zope 2.3 and Python 1.5.2, or if it would be okay if it supported
Zope 2.4 and Python 2.1 only. The latter option would make life easier
on the developers, but if there are a lot of users who want to upgrade
ParsedXML but not their Zope yet, we should continue to support
Python 1.5.2 for a while longer.
So, what do people think? I'm especially interested in hearing from current
users of ParsedXML, though input from others would be interesting as well.
Please send your replies to the list also so we can discuss things further.
Zope-xml mailing list
Zope-xml [at] zope