memcached Python API development status

[Vicente Arteaga]

You can take a look at swig (swig.org), which may help a lot! (btw I've 
never used it, although the next project I can I will use it)

Regards!

Damon Hart wrote:

> Hi all -
>
> I have been using the memcached Python API (caching Python objects 
> used by multiple machines constructed from data in a PostgreSQL 
> database.) I have noticed both the request for maintainers of this 
> code on the API web page and an external web page 
> (http://www.tummy.com/journals/entries/jafo_20041212_192853) 
> suggesting that there was at least one other person interested in 
> supporting this code.
>
> I have some observations about the Python code and would like to see 
> some features made accessible in Python implemented which are not 
> present in the Python API.
>
> Are patches posted to the memcached list appropriate in the absence of 
> a designated maintainer?
>
> What  are the pros and cons of maintaining the current Python API in 
> comparison to a Python wrapper around libmemcache? The effort to 
> update and add features to the all-Python API might be seen as 
> superfluous in the presence of a libmemcache wrapper.  While I can 
> suggest changes to the current API, I have no experience in creating a 
> wrapper. Is anybody contemplating/working on one?
>
> thanks
>
> Damon
>

-- 
Vicente Arteaga
Tecnobe Tecnología, S.L.
C/ Diagonal, 34A 3o1a
08290 Cerdanyola del Valles
93 580 98 95

-------------- next part --------------
A non-text attachment was scrubbed...
Name: varteaga.vcf
Type: text/x-vcard
Size: 307 bytes
Desc: not available
Url : http://lists.danga.com/pipermail/memcached/attachments/20050316/182e37b7/varteaga.vcf