-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/15/2012 02:44 PM, Tres Seaver wrote:
These three are at least partly my fault: the new persistent release enforces that tids are bytes objects, but ZODB still computed them via 'repr(timestamp)', which is a string. I have checked in a change which make ZODB us 'timestamp.raw()' instead. There are still some failures to work through.
I have checked in changes which have the ZODB trunk tests passing now under Python 2.6 2.7.
Looking at the tests list page: I see a bunch of failures related to the same ZODB issues; those should clear up after tonights report.
Looks like clearing those failures will requre another ZODB release. Jim, can you push out a 4.0.0a4, or make me a maintainer? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@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/ iEYEARECAAYFAlDOaDwACgkQ+gerLs4ltQ75lACfZHmqlE7dQmcMFB5uoit8G5tg +iUAn1EEGVWY0Aoh62m0rh40/scfBdA6 =Yel2 -----END PGP SIGNATURE-----