2,186
edits
Changes
→Dependency upgrades
==Dependency upgrades==
==Gramps 3.1==
For 3.1 we have: Python 2.5 or greater, PyGTK2 2.10 or greater, Python Glade bindings, librsvg2 (svg icon view), xdg-utils
Recommended or optional: GraphViz, gtkspell, ttf-freefont. Documentation is in mediawiki.
==Gramps 3.2==
For 3.2:
* change to PyGTK 2.12. Reason: Move away from libglade to GtkBuilder. Info: [http://www.micahcarrick.com/05-30-2008/gtk-builder-libglade-faq.html], example: [http://www.micahcarrick.com/01-01-2008/gtk-glade-tutorial-part-3.html]. ''Developers'': ? - ''Reviewers'': ?
* keep python 2.5 compatibility, while preparing for python 3.x.
Reason: At the moment there are no features of the 2.6/7 versionGRAMPS needs that require python 2.5 support to be dropped. Version3.2 will however be the last GRAMPS version on python 2.x, with thenext version of GRAMPS (3.3) being python 3.x only. For that reason,the move to python 3.0 needs to be prepared. For this we need thesupport that python 2.6 offers. That is, people should start to run
GRAMPS with:
python -3 gramps.py
which will print out depreciation warnings for all syntax that is notcompatible with Python 3.0. The goal is then to clean up all Python3.0 depreciation warnings using the new functionality that python 2.6offers for this, while still providing fallback for python2.5 (using
eg __future__ module and try, except blocks).
Should somebody come forward with an important improvement thatrequires python2.6, or if removing the warnings of python -3 isimpossible with backward python2.5 compatibility present, keepingpython2.5 compatibility can be dropped after talking it through on thedevel list. In other words, support for python2.5 should not bedropped without giving it a try first.
''Developers'': All
* it appears there is a drive to use enchant for spell checking. The API is better than gtkspell and has a python interface. We should investigate if we should not move entirely to this package and deprecate gtkspell. At a minimum we will look into adding enchant as a possible spell checking backend to GRAMPS, using it when installed. Packagers could then choose to let GRAMPS depend on enchant or gtkspell (part of gnome-extras now). ''Developers'': Benny, ''Status'': enchant is working
==Gramps 3.3==
For 3.3:
* Only support Python 2.6 or later (''configure.in, gramps.py, windows/builder/gramps2.nsi'')
* Update [[Deprecated]] list ?
==Gramps 3.4==
For 3.4:
**python 3.x?
==Database backend changes==
