From: Julio Sanchez <julio.sanchez@gm...> - 2005-09-03 08:57:42
Sorry for the broken message, let's try again.
Exporting to GEDCOM has started failing to me with this message:
Database error: so-and-so is defined as his or her own ancestor
This is produced by descendants_too_old in Utils.py and the message is
bogus. That person has no descendancy. Unlinking the person will
only shift the error to a different person.
It sems that the last change to descendants_too_old that added the
handling of a current set needs some consideration. My guess is that
it happens when there are multiple descendancy paths to some person
(all the cases I was getting are children of first or second cousins),
so finding the person in the set is not an error.
I have disabled that part and it works for me again.
Get latest updates about Open Source Projects, Conferences and News.