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

Re: SVN Python questions and suggestions

From: Barry Scott <barry_at_barrys-emacs.org>
Date: 2003-10-02 20:19:07 CEST

What would be really cool is that I could do:

import svn

list = svn.ls( 'http://x/repos/foo' )

list = svn.status( r'c:\workspace\svn' )

Of course this overlooks the problem of the options on each command.

Now that solves the problem of where to put all them functions as
you no longer care!

         Barry

At 02-10-2003 15:18, C. Michael Pilato wrote:
>Barry Scott <barry@barrys-emacs.org> writes:
>
> > How about this:
> >
> > in svn.apr expose the apr_* from core
> > in svn.config export the svn_config_* from core
> > etc.
>
>I think the goal was to try to avoid modules that had, oh, 3 functions
>in them. :-) I really don't want my programs to look like:
>
> import svn.apr
> import svn.pool
> import svn.config
> import svn.path
> import svn.io
> ...
>
>It just gets kinda junky, ya know? On the flip side, I'm so
>completely picky about consistency and such, so I hear you, I really
>do.
>
>Whatever the community decides is fine with me.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 2 20:20:14 2003

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.