[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Database interface

From: Marco van Tol
Subject: Re: [Bug-gnubg] Database interface
Date: Tue, 25 May 2004 14:49:55 +0000
User-agent: Mutt/1.4.2i

On Tue, May 25, 2004 at 02:13:57PM +0000, Joern Thyssen wrote:
> On Tue, May 25, 2004 at 01:44:24PM +0000, Marco van Tol wrote
> > On Tue, May 25, 2004 at 01:12:56PM +0100, Jon Kinsey wrote:
> > 
> > [...]
> > 
> > > I'm not sure about using python to access the database.  It wasn't a 
> > > problem as there is a pysqlite module, I just don't think it's 
> > > necessary.  To put it another way, it adds a dependency that isn't 
> > > strictly required.  I imagine the code could easily be changed so that 
> > > the database access is in the C layer and the python code changed to use 
> > > this.  Is there any other reason to use python for this?
> > 
> > Perhaps more to give a signal of life then to contribute something useful:
> > I'm a bit curious to know the answer to this as well. :)
> > 
> > I actually currently compile gnubg on my FreeBSD machine with
> > 'WITHOUT_PYTHON' so it doesn't consume _all available cpu_ even while not
> > really doing anything. Not sure if that's FreeBSD specific though.
> that's a weird problem... Are you sure that it is python that consumes
> CPU time?  I'm guesing that it's a GTK+ problem...

I should have been more correct, by WITHOUT_PYTHON I meant
'./configure --without-python', which completely gets rid of the symptom.
(It's a poor excuse but the ports collection in FreeBSD heavely uses
'WITH_<X>'/'WITHOUT_<X>' ;-)

I understood from Jim something along the lines that it had
something to do with (linux)threading on FreeBSD.  Unfortunately, I haven't
dug into this one myself yet.

...the only way to maintain a moderate sum of happiness in this life,
is not to worry about the future or regret the past too much.
- Mel Gibson 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]