{"id":1540,"date":"2016-09-02T13:46:44","date_gmt":"2016-09-02T11:46:44","guid":{"rendered":"http:\/\/blog.gocept.com\/?p=1540"},"modified":"2016-09-02T13:46:44","modified_gmt":"2016-09-02T11:46:44","slug":"zodb-py3migrate-1","status":"publish","type":"post","link":"https:\/\/blog.gocept.com\/2016\/09\/02\/zodb-py3migrate-1\/","title":{"rendered":"zodb.py3migrate: Migrate an existing ZODB Data.fs to be used with Python 3"},"content":{"rendered":"

At\u00a0Berlin Strategic sprint 2016<\/a>\u00a0we\u00a0developed a tool to analyze a ZODB Filestorage to find\u00a0Python 2 string objects. If\u00a0they are in an encoding besides ASCII this is\u00a0preventing using this Filestorage with Python 3 because of decoding errors arising on loading the pickles.
\nThe tool is even able to convert those strings either to unicode by decoding them using a configurable encoding or convert them to\u00a0zodbpickle.binary<\/code>\u00a0so Python 3 will read them as\u00a0bytes<\/code>.
\nThere is\u00a0
documentation<\/a>\u00a0of the tool and\u00a0a repository on GitHub<\/a>\u00a0where the code lives.<\/p>\n

There are still some questions open:<\/p>\n