Re: [Zope] Re: [Zope-dev] Using 2.3.2 for Zope 2.7

2003-10-04 Thread Myroslav Opyr
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/2.3 ?
 

We have deployed Zope 2.6.2 with Python 2.2.3 in production for clients
already;  the garbage collection improvements in Python 2.2.3 were so
compelling that we couldn't reasonably roll them back to Python 2.1.3
after testing.
 

I've several times met indirect evidences that migration of application 
between Python 2.1 - Python 2.2 got strange pickle-related issues.

Not sure if it was Python itself or some 3rd party product like 
TextIndexNG but the issues arised.

However running something with Python 2.2 or 2.3 from scratch had shown 
no problems.

Regards,

m.
--
Myroslav Opyr
zope.net.ua http://zope.net.ua/  Ukrainian Zope Hosting
e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope] Re: [Zope-dev] Using 2.3.2 for Zope 2.7

2003-10-04 Thread Andreas Jung


--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 maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


[Zope-dev] Re: [Zope] Using 2.3.2 for Zope 2.7

2003-10-04 Thread Florian Lindner
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,
Florian
___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] catalogObject changes (Zope-2_6-branch)

2003-10-04 Thread Chris McDonough
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 updated when indexes were specified.  The new
(correct) behavior may break some applications that depended on the bug,
and I'm sorry it broke yours, but it was indeed a bug.

And, doh, yes, I need to forward-port the fix to the 2.7 branch and the
HEAD. :-(

On Fri, 2003-10-03 at 16:49, Dieter Maurer wrote:
 Yuppie wrote at 2003-10-3 10:14 +0200:
   Yesterday I spent some hours tracking down why catalog Metadata and 
   catalog Indexes are getting out of sync in my CMF Site.
   
   I found that checkin
   
 http://cvs.zope.org/Zope/lib/python/Products/ZCatalog/Catalog.py.diff?r1=1.98.6.10r2=1.98.6.11
   
   including this new condition
   code
if not idxs:
# if the caller specifies that we should update only a
# specific set of indexes, we don't do a metadata update.
self.updateMetadata(object, uid)
   /code
   
   Could anybody tell me what's the rationale behind that checkin?
   
   - it breaks backwards compatibility
   - it's only in Zope-2_6-branch, not in Zope-2_7-branch or HEAD
   - I can't see what this 'if' is good for anyway
 
 I can ;-)
 
 The idxs argument is often provided to update only special indexes:
 e.g. workflow indexes or AllowedRolesAndUsers and when you
 update selected indexes from the Indexes tab.
 In these cases, it is often not necessary to update the Metadata.
 
 Metadata updates are often monstruous. In one of our applications,
 Metadata updates are responsible for a 500 kB transaction
 when a single workflow state changes.
 
 I am now advocating not to use Metadata at all.
 They are only relevant when you process large result sets
 (e.g. for sorting or statistics).
 
 
 Dieter
 
 ___
 Zope-Dev maillist  -  [EMAIL PROTECTED]
 http://mail.zope.org/mailman/listinfo/zope-dev
 **  No cross posts or HTML encoding!  **
 (Related lists - 
  http://mail.zope.org/mailman/listinfo/zope-announce
  http://mail.zope.org/mailman/listinfo/zope )


___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )


Re: [Zope-dev] Using 2.3.2 for Zope 2.7

2003-10-04 Thread Craeg K Strong
+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

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.

 



___
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )