Re: session/otks gdbm db's not compatible - python3 conversion issue?

On Sun, 24 Mar 2019, John P. Rouillard wrote:

> The rdbms backends seem to be usable with both python versions. I
> wonder if this will also be an issue for using the anydbm backend
> rather than sqlite/mysql etc.

doc/upgrading.txt documents the compatibility issues if changing python 
version for an existing tracker:

  If your tracker uses the ``anydbm`` or ``mysql``
  backends, you also need to export the tracker contents using
  ``roundup-admin export`` running under Python 2, and them import them
  using ``roundup-admin import`` running under Python 3, as for a
  migration to a different backend.  If using the ``sqlite`` backend,
  you do not need to export and import, but need to delete the
  ``db/otks`` and ``db/sessions`` files when changing Python version.
  If using the ``postgresql`` backend, you do not need to export and
  import and no other special database-related steps are needed.

(See issue2550975 for discussion.  mysql is *not* compatible when you have 
non-ASCII data in your database because of how, with Python 2, databases 
store UTF-8 bytes incorrectly labelled as being in the default encoding.)

-- 
Joseph S. Myers
[email protected]