On Oct 23, 2008, at 5:27 AM, Hermann Himmelbauer wrote: > Am Mittwoch 22 Oktober 2008 16:44:58 schrieb Satchidanand Haridas: >> What version of zope.session are you using? >> >> A fix (using zope.minmax) for ConflictErrors related to the update of >> access time on sessionData object was committed into zope.session in >> rev76899. Not sure if that solves this problem of conflict errors >> that >> you see, but if you are using a version of zope.session prior to >> r76899, upgrading may make those problems go away. > > Hmmm, I'm using zope.session from the KGS, so I'm unsure which > revision I have. However, when looking at the "$Id:" lines in the > python files, I can see e.g. the following line: > > tests.py:$Id: tests.py 80055 2007-09-25 21:28:54Z rogerineichen > > That probably indicates, that my revision > r76899, is that true?
Yes you have higher revision. However, there was another issue that was fixed in -r 87351. The following line should be there: $Id: tests.py 87351 2008-06-12 21:02:43Z gary $ That version was released immediately in -r 87352 as zope.session-3.5.2 and the change log states: version 3.5.2 (2008-06-12) -------------------------- - Remove ConflictErrors caused on SessionData caused by setting ``lastAccessTime``. Using zope.session-3.5.2 is worth the try. Zvezdan _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org 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 )