[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Python bindings

From: Lele Gaifax <lele_at_nautilus.homeip.net>
Date: 2004-05-10 15:40:42 CEST

>>>>> "Greg" == Greg Stein <gstein@lyra.org> writes:

>> You seem to think they are not even up to simple tasks.

    Greg> Heh. I've been using the Python bindings for
    Greg> years. Literally.

Yes, of course, and me too, through your code :)

But that does not imply that one can actually use them to code say an
equivalent of "svn add --no-auto-props somefile.py"... After few hours
I gave up on swig, while it took *half* an hour to understand how to
do the same for pysvn and contribute it back.

That's the top priority for bindings, imho: assuming one master at
least one of the two involved domains and is able to read/understand
code/documentation of the other, he should definitively be in position
of contribute to them. This is not currently so, as SWIG push in a
third domain, almost as tricky and complicated as the sum of the other
two. Pyrex promises just that, and even the C++ layer used by pysvn is
closer.

    Greg> But that said: I doubt that Ben was bashing the Python
    Greg> bindings in that way. Instead, I think each of you were just
    Greg> overreacting and should have stopped to take a breath :-)

I concede that :) Sorry Ben for my possibly unweighted words. And
thanks Greg for raising up my mood!-)

ciao, lele.

-- 
nickname: Lele Gaifax	| Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas	| comincerò ad aver paura di chi mi copia.
email: lele@seldati.it	|		-- Fortunato Depero, 1929.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon May 10 15:41:16 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.