From: john f j. <joh...@kn...> - 2009-01-09 17:07:12
|
Is the following GRAMPS error another manifestation of the bsddb problem or is it a different one. I tried to report this via the GRAMPS bug reporting mechanism yesterday. Thanks in advance, John Jarvis 12182: ERROR: DbLoader.py: line 281: Failed to open database. Traceback (most recent call last): File "/usr/local/share/gramps/DbLoader.py", line 272, in read_file self.dbstate.db.load(filename, self.uistate.pulse_progressbar, mode) File "/usr/local/share/gramps/gen/db/dbdir.py", line 450, in load return self.__load(name, callback, mode) File "/usr/local/share/gramps/gen/db/dbdir.py", line 483, in __load self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) # clean up unused logs AttributeError: 'module' object has no attribute 'DB_LOG_AUTOREMOVE' |
From: Josip <jo...@pi...> - 2009-01-09 17:13:04
|
john f jarvis wrote: > Is the following GRAMPS error another manifestation of the bsddb problem > or is it a different one. I tried to report this via the GRAMPS bug > reporting mechanism yesterday. > Thanks in advance, John Jarvis > > 12182: ERROR: DbLoader.py: line 281: Failed to open database. > Traceback (most recent call last): > File "/usr/local/share/gramps/DbLoader.py", line 272, in read_file > self.dbstate.db.load(filename, self.uistate.pulse_progressbar, mode) > File "/usr/local/share/gramps/gen/db/dbdir.py", line 450, in load > return self.__load(name, callback, mode) > File "/usr/local/share/gramps/gen/db/dbdir.py", line 483, in __load > self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) # clean up unused logs > AttributeError: 'module' object has no attribute 'DB_LOG_AUTOREMOVE' > > Use of Gramps 3.0.4 solve this. see: http://gramps-project.org/wiki/index.php?title=Python2.6 -- Josip |
From: Benny M. <ben...@gm...> - 2009-01-09 17:24:58
|
Yes, 3.0.4 was released to support python 2.6 and bsddb 4.7 version. It might be that python2.5 is installed on your system and editing /usr/bin/gramps to use that solves the problem, however, some distro's use python 2.5 with newer bsddb 4.7 module too.... 3.0.4 is the safest bet Benny 2009/1/10 Josip <jo...@pi...> > john f jarvis wrote: > > Is the following GRAMPS error another manifestation of the bsddb problem > > or is it a different one. I tried to report this via the GRAMPS bug > > reporting mechanism yesterday. > > Thanks in advance, John Jarvis > > > > 12182: ERROR: DbLoader.py: line 281: Failed to open database. > > Traceback (most recent call last): > > File "/usr/local/share/gramps/DbLoader.py", line 272, in read_file > > self.dbstate.db.load(filename, self.uistate.pulse_progressbar, mode) > > File "/usr/local/share/gramps/gen/db/dbdir.py", line 450, in load > > return self.__load(name, callback, mode) > > File "/usr/local/share/gramps/gen/db/dbdir.py", line 483, in __load > > self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) # clean up unused logs > > AttributeError: 'module' object has no attribute 'DB_LOG_AUTOREMOVE' > > > > > > Use of Gramps 3.0.4 solve this. > see: http://gramps-project.org/wiki/index.php?title=Python2.6 > > -- > Josip > > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: S. C. <ste...@gm...> - 2009-01-09 17:16:57
|
> File "/usr/local/share/gramps/gen/db/dbdir.py", line 483, in __load > self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) # clean up unused logs > AttributeError: 'module' object has no attribute 'DB_LOG_AUTOREMOVE' This one was fixed back in 3.0.4. What version of GRAMPS are you using? Stéphane |
From: Dave C. <da...@da...> - 2009-01-10 08:18:53
|
Stéphane Charette wrote: >> File "/usr/local/share/gramps/gen/db/dbdir.py", line 483, in __load >> self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) # clean up unused logs >> AttributeError: 'module' object has no attribute 'DB_LOG_AUTOREMOVE' > > > This one was fixed back in 3.0.4. What version of GRAMPS are you using? Fedora 10 still only has 3.0.3 in its official repositories. I see that there's a 3.0.4 RPM for F10 available from the Gramps site tho'. http://sourceforge.net/project/showfiles.php?group_id=25770&package_id=109309 Dave... |
From: David R. <re...@os...> - 2009-01-10 13:39:58
|
On Fri, 09 Jan 2009 11:40:18 -0500 john f jarvis wrote: > Is the following GRAMPS error another manifestation of the bsddb > problem or is it a different one. I tried to report this via the > GRAMPS bug reporting mechanism yesterday. > Thanks in advance, John Jarvis > > 12182: ERROR: DbLoader.py: line 281: Failed to open database. > Traceback (most recent call last): > File "/usr/local/share/gramps/DbLoader.py", line 272, in read_file > self.dbstate.db.load(filename, self.uistate.pulse_progressbar, > mode) File "/usr/local/share/gramps/gen/db/dbdir.py", line 450, in > load return self.__load(name, callback, mode) > File "/usr/local/share/gramps/gen/db/dbdir.py", line 483, in __load > self.env.set_flags(db.DB_LOG_AUTOREMOVE, 1) # clean up unused > logs AttributeError: 'module' object has no attribute > 'DB_LOG_AUTOREMOVE' Hello John, I encountered this same problem with Gramps-3.0.3. It's fixed in Gramps-3.0.4. The underlying problem has to do with the version of BerkeleyDB installed on your machine. Old versions use db.DB_LOG_AUTOREMOVE while new versions use db.DB_LOG_AUTO_REMOVE (not the added "_"). If memory serves, this problem occurs 2 or 3 places in the code. I expect you could modify the python source code to fix things. It'd probably be better to use the newer version of gramps as it has the fix built in. HTH, David |
From: Douglas S. B. <db...@cs...> - 2009-01-10 14:04:46
|
> On Fri, 09 Jan 2009 11:40:18 -0500 > john f jarvis wrote: [snip] > Hello John, > > I encountered this same problem with Gramps-3.0.3. It's fixed in > Gramps-3.0.4. > > The underlying problem has to do with the version of BerkeleyDB > installed on your machine. Old versions use db.DB_LOG_AUTOREMOVE while > new versions use db.DB_LOG_AUTO_REMOVE (not the added "_"). > > If memory serves, this problem occurs 2 or 3 places in the code. I > expect you could modify the python source code to fix things. One nice thing about most open source projects is that every change is done in the open. You can actually see every change made to every file over time. You can see exactly what was needed here: http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/gen/db/dbdir.py?r1=11297&r2=11354 and here: http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/gen/db/dbdir.py?r1=11354&r2=11360 > It'd > probably be better to use the newer version of gramps as it has the > fix built in. Agreed. But, Python is a nice language to learn if any of you are interested, and the sources are easy to get and install. -Doug > HTH, > > David > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Benny M. <ben...@gm...> - 2009-01-12 08:53:54
|
2009/1/10 Douglas S. Blank <db...@cs...> > > One nice thing about most open source projects is that every change is > done in the open. You can actually see every change made to every file > over time. You can see exactly what was needed here: > > > http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/gen/db/dbdir.py?r1=11297&r2=11354 > > and here: > > > http://gramps.svn.sourceforge.net/viewvc/gramps/trunk/src/gen/db/dbdir.py?r1=11354&r2=11360 > As this is the users list, I'd like to point out above changes are for the trunk version, so future 3.1.x, NOT for the current STABLE version 3.0.x. That would be not trunk, but branches/gramps30 Benny |
From: David R. <re...@os...> - 2009-01-10 20:22:43
|
On Sat, 10 Jan 2009 09:04:31 -0500 (EST) Douglas S. Blank wrote: ...[snip]... > > It'd > > probably be better to use the newer version of gramps as it has the > > fix built in. > > Agreed. But, Python is a nice language to learn if any of you are > interested, and the sources are easy to get and install. > > -Doug H'lo Doug, I agree that Python is a nice language and use it (among various others). One thing I've not yet found is a nice debugger. pydb is usable but somewhat primitive. What do the Gramps developers use for debugging? Regards, David |
From: Serge N. <Ser...@fr...> - 2009-01-10 22:10:40
|
Le/The samedi 10 janvier 2009, David Relson a écrit/wrote : > On Sat, 10 Jan 2009 09:04:31 -0500 (EST) > Douglas S. Blank wrote: > > ...[snip]... > > > It'd > > > probably be better to use the newer version of gramps as it has the > > > fix built in. > > > > Agreed. But, Python is a nice language to learn if any of you are > > interested, and the sources are easy to get and install. > > > > -Doug > > H'lo Doug, > > I agree that Python is a nice language and use it (among various > others). One thing I've not yet found is a nice debugger. pydb is > usable but somewhat primitive. What do the Gramps developers use for > debugging? I use pdb In a module use : import pdb Then when you nedd to debug : use pdb.set_trace() see : http://www.ferg.org/papers/debugging_in_python.html > > Regards, > > David |
From: Jérôme <rom...@ya...> - 2009-01-11 08:25:55
|
> One thing I've not yet found is a nice debugger. pydb is > usable but somewhat primitive. This let me remember : I didn't test Eero trick yet ! > Python has facilities for debugging issues in code written in Python. > For memory leaks, you should look into the "gc" module. > --------------------- > import gc > gc.set_debug(gc.DEBUG_UNCOLLECTABLE) > --------------------- Jérôme David Relson a écrit : > On Sat, 10 Jan 2009 09:04:31 -0500 (EST) > Douglas S. Blank wrote: > > ...[snip]... >>> It'd >>> probably be better to use the newer version of gramps as it has the >>> fix built in. >> Agreed. But, Python is a nice language to learn if any of you are >> interested, and the sources are easy to get and install. >> >> -Doug > > H'lo Doug, > > I agree that Python is a nice language and use it (among various > others). One thing I've not yet found is a nice debugger. pydb is > usable but somewhat primitive. What do the Gramps developers use for > debugging? > > Regards, > > David > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Cedric S. <ce...@no...> - 2009-01-12 09:52:01
|
ddd is a graphical frontend to various debuggers and it now now supports pydb. I haven't used it to debug python but I have used it in the past (when I had a real job) for debugging C and perl and I found it much more user friendly than gdb or perl -d. Cedric On Saturday 10 January 2009 20:22:39 David Relson wrote: > On Sat, 10 Jan 2009 09:04:31 -0500 (EST) > Douglas S. Blank wrote: > > ...[snip]... > > > > It'd > > > probably be better to use the newer version of gramps as it has the > > > fix built in. > > > > Agreed. But, Python is a nice language to learn if any of you are > > interested, and the sources are easy to get and install. > > > > -Doug > > H'lo Doug, > > I agree that Python is a nice language and use it (among various > others). One thing I've not yet found is a nice debugger. pydb is > usable but somewhat primitive. What do the Gramps developers use for > debugging? > > Regards, > > David > > --------------------------------------------------------------------------- >--- Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users |
From: Douglas S. B. <db...@cs...> - 2009-01-10 20:53:37
|
> On Sat, 10 Jan 2009 09:04:31 -0500 (EST) > Douglas S. Blank wrote: > > ...[snip]... >> > It'd >> > probably be better to use the newer version of gramps as it has the >> > fix built in. >> >> Agreed. But, Python is a nice language to learn if any of you are >> interested, and the sources are easy to get and install. >> >> -Doug > > H'lo Doug, > > I agree that Python is a nice language and use it (among various > others). One thing I've not yet found is a nice debugger. pydb is > usable but somewhat primitive. What do the Gramps developers use for > debugging? That's an interesting question... personally, I don't use one. I've written a Python Gramplet that gives GRAMPS an embedded interpreter, and so I can inspect the running system that way (some code I can interactively set a debug switch, which will then show additional data, but you have to code it to do that). I use Emacs, and some print statements, and the Reload plugins button on the Help -> Plugins dialog (in the new GRAMPS 3.1 version) when writing plugins. I use "grep" a lot to find code an insert print statements, and so can manually "trace" code. But I suspect every developer does their own thing. I'm not sure if there is a better solution than pydb (other than "print" :) ... -Doug > Regards, > > David > > ------------------------------------------------------------------------------ > Check out the new SourceForge.net Marketplace. > It is the best place to buy or sell services for > just about anything Open Source. > http://p.sf.net/sfu/Xq1LFB > _______________________________________________ > Gramps-users mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-users > |
From: Benny M. <ben...@gm...> - 2009-01-12 09:05:46
|
2009/1/10 Douglas S. Blank <db...@cs...> > > On Sat, 10 Jan 2009 09:04:31 -0500 (EST) > > Douglas S. Blank wrote: > > > > ...[snip]... > >> > It'd > >> > probably be better to use the newer version of gramps as it has the > >> > fix built in. > >> > >> Agreed. But, Python is a nice language to learn if any of you are > >> interested, and the sources are easy to get and install. > >> > >> -Doug > > > > H'lo Doug, > > > > I agree that Python is a nice language and use it (among various > > others). One thing I've not yet found is a nice debugger. pydb is > > usable but somewhat primitive. What do the Gramps developers use for > > debugging? > > That's an interesting question... personally, I don't use one. I've > written a Python Gramplet that gives GRAMPS an embedded interpreter, and > so I can inspect the running system that way (some code I can > interactively set a debug switch, which will then show additional data, > but you have to code it to do that). > > I use Emacs, and some print statements, and the Reload plugins button on > the Help -> Plugins dialog (in the new GRAMPS 3.1 version) when writing > plugins. I use "grep" a lot to find code an insert print statements, and > so can manually "trace" code. > > But I suspect every developer does their own thing. I'm not sure if there > is a better solution than pydb (other than "print" :) ... > I thought you where going to say: We don't make errors :-D We might need a wiki page about debugging. Many possibilities are given in this thread. Some extra: 1. we have a plugin in the debug tools: show uncollected objects 2. we have a profiling function to profile the code quickly in the Utils 3. we have the logging system that is set up in all modules (see GeoView in trunk for use) and that lets you output debug, info, warning, ... messages depending on a switch Benny |