-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/08/2013 02:03 AM, Tres Seaver wrote:
One point to consider is that anybody who has been using ZODB on Py3k
since the beta will have to do surgeery on their filestorages to get
them to load after that change (the code doesn't make any attempt to
determine if the magic number is later; it just checks for an exact
match). I don't want to make the wait, we have five users, we can't
take out the tab requirement mistake here: anybody for whom this
would be a hardship needs to speak up pretty quickly.
I merged the 'issue_10' branch to trunk and released ZODB 4.0.0b3
yesterday. Today I found (as I expected) that I couldn't open the
database I created last week under Py3k after updating.
Am I the only person affected? Or do we need to add fallback code to
permit opening a filestorage with an older magic number in read-only
mode? In my case, the data is all test stuff, so I can just blow it away
and recreate it.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iEYEARECAAYFAlG4rpcACgkQ+gerLs4ltQ4h/gCcCc/PBE6rY0FcJ2+pXqAAXpEJ
SNkAn1v3O3ypcIfQYN+egYnBixNZIUii
=zQ3t
-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
