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

Re: More cvs2svn broken in 0.17.0?

From: <cmpilato_at_collab.net>
Date: 2003-01-23 18:29:21 CET

Edward S. Marshall esm@logic.net writes:

 (warning, half-baked idea follows)
 Although, this does give me an interesting idea; a lot of functions have
 optional arguments (optional in the sense that the argument is NULL if
 there's nothing to be passed). Is there any way that this could be mapped
 to python's optional argument syntax (ie. foo(arg1, arg2=None)) in a
 semi-automated manner?

Regarding the above: I don't think so.

 (Maybe this would be better done in fs.py, to compliment the svn_fs_
 stripping done for everything exported by _fs? And mimic'd where needed
 in other modules? If this approach was taken, it's probably an effort
 best left until svn is a little closer to 1.0...)

Regarding the above: I think so.


We're going to have to whip the module wrappers into shape soon. I've
been avoiding the issue for as long as possible because it means the
Subversion team itself has to doubly maintain all of our APIs, instead
of the current scenario where if the bindings change, we only have to
change the tools that we provide and that use those particular APIs of
the bindings.

But as 1.0 seems a distant and nebulous thing, perhaps it's time to
just dive in and get those .py files looking beautiful.

Any volunteers? I'd be glad to offer feedback on interface decisions,
and I'm sure Greg Stein would be more than happy to guide us toward
the light on this.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 14 02:09:36 2006

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.