+1000 for moving directly to 2.3.2
I maintain several existing Zope add-on products that have to change
anyway to be compatible
with 2.7. Why on earth would I want to go through that pain *twice* ?
Change is inevitable. Killing two birds with one stone means less pain
overall, IMHO.
--Craeg
The system is making the assumption that if you update indexes
individually, you know what you're doing. Passing an index name into
catalogObject was always meant to do as much or as little work as you
specified with respect to the names of the indexes; it was only by
mistake that metadata got upd
Chris McDonough wrote:
Some people at ZC have made pretty compelling arguments to make Python
2.3.2 the "recommended" version of Python to use with Zope 2.7 final.
I'm wondering if other people have a strong feeling about this either
way.
By the way: When is 2.7 supposed to be released?
Thanks,
F
--On Samstag, 4. Oktober 2003 10:20 Uhr +0300 Myroslav Opyr
<[EMAIL PROTECTED]> wrote:
Not sure if it was Python itself or some 3rd party product like
TextIndexNG but the issues arised.
There is no such problem with TextIndexNG.
-aj
___
Zope-Dev mai
Tres Seaver wrote:
On Fri, 2003-10-03 at 10:58, Andrew Sawyers wrote:
I don't know about 'blessing', but I'm using it on a project currently
(Python 2.3 and Zope 2.6.2) without glitches.
Andrew
Toby Dickenson wrote:
Does anyone else have an interest in blessing Zope 2.6.x with Python 2.2
