On Wed, 2006-04-05 at 06:28 +1000, Graham Williams wrote: > No. That did not help. The problem seems to be with Spell. If I > comment out the line in Sources.py that imports Spell (just before the > import of DdTargets), gramps at least starts up. > > In fact, if I comment out in Spell.py just: > > gtkspell.Spell(gtk.TextView()).set_language(lang) > > then again it starts up. > > Simulating this interactively: > > ======================================================================== > Python 2.3.5 (#2, Mar 6 2006, 10:12:24) > [GCC 4.0.3 20060304 (prerelease) (Debian 4.0.2-10)] on linux2 > Type "help", "copyright", "credits" or "license" for more information. > >>> import gtk > >>> import gtkspell > >>> import locale > >>> lang = locale.getlocale()[0] > >>> lang > >>> lang==None > True > >>> locale.getlocale() > (None, None) > ========================================================================>>> > > That is perhaps the problem?
Well, setting the language to None should trigger an exception.
Here's what happens on my machine:
$ python
>>> import gtkspell
>>> import gtk
>>> gtkspell.Spell(gtk.TextView()).set_language(None)
Traceback (most recent call last):
File "<stdin>", line 1, in ?
RuntimeError: Error setting language
and GRAMPS would catch that exception. If the above crashes for you
instead of raising a RuntimeError exception then it seems to be
a bug in python2.3-gnome2-extras package.
GRAMPS could of course also work around this by checking for
lang being None and refusing to go further.
--
Alexander Roitman http://www.gramps-project.org
signature.asc
Description: This is a digitally signed message part
