I must admit i havent code digging too much into clutter but as it is the bindings are all ok for what i've tested ;)

Enviado do meu iPod

No dia 2008/10/15, às 05:16, Emmanuele Bassi <[EMAIL PROTECTED]> escreveu:

On Tue, 2008-10-14 at 23:40 +0100, Jan Jokela wrote:
You can grab pyclutter from trunk.
As far as I know it is maintained, it's more of a thing about ebassi
kind-of hating the python bindings.

oh, I don't *hate* the python bindings. ;-P I just don't like the misery
they're imposing on me on every release cycle.

I'm also apparently unable to understand the lack of feedback or testing
for a binding that supposedly many people are using - considering the
questions on IRC and on this very mailing list. I try releasing stable
bindings if I know they are stable: no major bug/crasher, locked
dependencies and API stable; if nobody reports anything on SVN trunk it
either means the code is perfect or that everyone is still using 0.6.

now, for the former: I might be good, but I'm not *that* good. so it
must be the latter, which really bugs me because it means that I'll
always have to make two releases of the python bindings: 0.<even>.0 for testing and 0.<even>.1 to fix the issues and maybe even change the API - because nobody bothered giving back feedback on trunk. by the way: there
is a reason if I use a public revision control system, so that people
can check out what the hell am I doing.

in any case, I finally came to the realization that this is all fine by
me: if this is what python developers expect far be it from me not to
give them what they want.

ciao,
Emmanuele.

Jan.

On Tue, Oct 14, 2008 at 11:27 PM, "Frédéric Van der Essen"
<[EMAIL PROTECTED]> wrote:
       Hello,
       It seems that the latest python bindings are for clutter 0.6.2
       only.
       Is pyclutter still maintained ? When is the next release
       planned ?

       Thanks, Fred.


--
Emmanuele Bassi, Intel Open Source Technology Center

--
To unsubscribe send a mail to [EMAIL PROTECTED]

--
To unsubscribe send a mail to [EMAIL PROTECTED]

Reply via email to