Re: [vdrpylib-devel] pending patches?

[Rob S. <ro...@in...>]

Dominic Morris wrote:
> Hey, 

Hi, welcome to the list.  Sorry for the late reply.


> I hadn't noticed, until today, that this project was under new 
> maintainership.

Yep, I'm working on another project that I've been using it for and 
decided it would be easier to maintain vdrpylib than to send patches to 
a dead project. ;)


> I was wondering if there are any outstanding patches that have been on the 
> list but can't be accessed via the sf interface that might fix a few 
> things that break with my setup.

There is a patch from Vlad here which contains some changes which I may 
include.  I haven't gone through it all yet because on my vacation 
(which just ended) I decided to goof off instead of hack.  What issues 
are you having?


> Also, whilst I'm thinking about it, does anyone have a cunning idea how to
> share a vdr object amongst multiple python interpreters? I got the
> previous version running a few months ago and reading in all the epg data
> took up about 30-40MB of memory which multipled by however many clients 
> are connected doesn't scale too well!

It sounds like you should build a server process which is the single 
point of communication to VDR.  In my other project, Freevo 
(http://freevo.sf.net), we are working on an EPG library (pyepg) which 
can use vdrpylib to fill its database.  You may be interested in that 
sort of thing.  I have also been working on a client-server 
implimentation of pyepg but that part is specific to Freevo so far.

-Rob