bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] Database interface


From: Jim Segrave
Subject: Re: [Bug-gnubg] Database interface
Date: Tue, 25 May 2004 21:54:06 +0200
User-agent: Mutt/1.4i

On Tue 25 May 2004 (14:13 +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 think it's a limitation in the FreeBSD thread support. One of these
days, if I ever have any spare time again, I'll install FreeBSD 5.2 or
5.3 which should have better threading

-- 
Jim Segrave           address@hidden




reply via email to

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