[Zope-dev] zope-tests - FAILED: 4, OK: 12

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/25/2013 04:36 AM, Marius Gedminas wrote:
> On Thu, Apr 25, 2013 at 11:21:37AM +0300, Marius Gedminas wrote:
>> On Thu, Apr 25, 2013 at 01:00:01AM +0000, Zope tests summarizer
>> wrote:
>>> [3]    winbot / z3c.contents_py_265_32
>> 
>> Same old -- and I just managed to reproduce it at last.
> 
> ZODB.utils.newTid(None) returns "'\\x03\\x9e8\\x9a:>\\x12\\x88'",
> i.e. the repr of an 8-byte string instead of the 8-byte string
> itself.
> 
> AFAICT it's because repr(persistent.timestamp.TimeStamp(2013, 04, 25,
> 11, 30, 0)) changed in persistent 4.0.5:
> 
> https://github.com/zopefoundation/persistent/commit/e692af8281466fa309aae9273864039dcb287383
>
>  This was fixed in ZODB 4.0.4a4:
> 
> https://github.com/zopefoundation/ZODB/commit/8dfbff499d109b1cf86d1b4b2b98a6cf8d17ce43
>
> 
https://github.com/zopefoundation/ZODB/commit/994af0c5f9df63d403a0e21d80eec51d69686bc4
> https://github.com/zopefoundation/ZODB/commit/19e851c2230a20cfcebc68fca37ce2c0bb716b92
>
> 
https://github.com/zopefoundation/ZODB/commit/2ce7b945003ca8494f970a6946e4143dc18848e6
> 
> So latest stable ZODB3 (3.10.5) is incompatible with the two latest
> stable persistent releases (4.0.5 and 4.0.6).
> 
> What should we do?  Release ZODB3 3.10.6 with a backport of these 
> patches?

ZODB 3.10 bundles its own version of persistent:  the standalone one
shouldn't be used at all if ZODB 3.10 is in play.



Tres.
- -- 
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlF5NGgACgkQ+gerLs4ltQ5EmgCbBmbeaDMs/6pyN0SQc3jcIlzj
AakAoLwmtyjODMmz3JXHxGXy8rUMElAl
=5GSE
-----END PGP SIGNATURE-----