-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I posted an issue, including a gist showing the problem:
https://github.com/zopefoundation/ZODB/issues/10 The 'issue_10' branch adds a test (failing without the patch) and a patch for this issue: https://github.com/zopefoundation/ZODB/pull/11 I think we arrived at consensus that trying to emit backward-compatible pickles (bytes pickled using the string opcodes, as in Python2) was the wrong approach, and that when we get around to tackling the problem, we would do so by having Python2 emit forward-compatible pickles instead (using a custom 'binary' type for things which should be bytes in Py3k, and using the protocol 3 opcodes to pickle them). If I am correct about this consensus, then in addition to merging PR #11 for ZODB, we should also drop the 'bytes_as_strings' changes to 'zodbpickle'. Thoughts? Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@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/ iEYEARECAAYFAlGxN0YACgkQ+gerLs4ltQ7+SgCeNLwvgq56afQnu06kw8bUO30E 69wAnR2WcFwz43N7QmxxBU93zxrcD/aO =/9eb -----END PGP SIGNATURE----- _______________________________________________ For more information about ZODB, see http://zodb.org/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
