Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 5526:df3f553fa414
Update documentation for Python 3 support (issue 2550968, issue 2550980).
A few obsolete references to Python 2.3 or 2.4 also removed or
updated.
| author | Joseph Myers <jsm@polyomino.org.uk> |
|---|---|
| date | Mon, 03 Sep 2018 00:12:46 +0000 |
| parents | e2978ed3b550 |
| children | bc3e00a3d24b |
comparison
equal
deleted
inserted
replaced
| 5525:bb7865241f8a | 5526:df3f553fa414 |
|---|---|
| 35 | 35 |
| 36 Although the ``MySQLdb`` module from | 36 Although the ``MySQLdb`` module from |
| 37 https://pypi.org/project/MySQL-python/ is still supported, it is | 37 https://pypi.org/project/MySQL-python/ is still supported, it is |
| 38 recommended to switch to the updated module from | 38 recommended to switch to the updated module from |
| 39 https://pypi.org/project/mysqlclient/. | 39 https://pypi.org/project/mysqlclient/. |
| 40 | |
| 41 Python 3 support | |
| 42 ---------------- | |
| 43 | |
| 44 Many of the ``.html`` and ``.py`` files from Roundup that are copied | |
| 45 into tracker directories have changed for Python 3 support. If you | |
| 46 wish to move an existing tracker to Python 3, you need to merge in | |
| 47 those changes. If your tracker uses the ``anydbm`` backend, you also | |
| 48 need to export the tracker contents using ``roundup-admin export`` | |
| 49 running under Python 2, and them import them using ``roundup-admin | |
| 50 import`` running under Python 3, as for a migration to a different | |
| 51 backend. If using the ``sqlite`` backend, you do not need to export | |
| 52 and import, but need to delete the ``db/otks`` and ``db/sessions`` | |
| 53 files when changing Python version. | |
| 40 | 54 |
| 41 Migrating from 1.5.1 to 1.6.0 | 55 Migrating from 1.5.1 to 1.6.0 |
| 42 ============================= | 56 ============================= |
| 43 | 57 |
| 44 Update tracker config file | 58 Update tracker config file |