Re: Python 3 status

Another update:

We could do with more user testing of Python 3 support in certain areas, 
but I don't think there's anything blocking preparing a release with 
Python 3 support (with a view to such a release having that support marked 
experimental, and making it more likely that such testing will occur, with 
it also being likely that a series of quick bug fix releases should be 
made after the initial release with Python 3 support as people discover 
problems with that support).

The status of support for moving to Python 3 without export/import of the 
database is now understood and documented in upgrading.txt (postgresql 
works best, for sqlite you have to delete the sessions database, for 
anydbm and mysql you need to export/import; see my recent commit 
bc3e00a3d24b and issue2550975 for explanation of the problem with mysql 
databases having incorrect character sets recorded).  Needing to 
export/import with mysql isn't ideal but I don't think it should block 
making a release.

All the web interfaces that work with Python 2 now also work with Python 
3.  It would be good to get the mod_python support (see issue2550821) and 
ZRoundup (see issue2141835) working again and tested with Python 3, but 
given how long they've been broken with Python 2 I don't think that should 
block making a release either.

POP and IMAP input to roundup-mailgw has been fixed for Python 3 by code 
inspection; it would be good to have some testing there; see issue2550974.

-- 
Joseph S. Myers
[email protected]