David James wrote:
> For sure! The link on the issues page is just an example. I don't
> think that 'single example' is representative at all of what needs to
> be done.
>
> What I'd really like to see is a general clean up of the Python
> bindings to have a more usable class structure, similar to the Ruby
> bindings. It'd be great if you could just type:
That's the idea, of course. What I'm wondering is whether there are
many (more) known things that you currently _can't do_ in Python, no
matter how clunky and disgusting you're willing to make the code. I
understand fairly well the scope of adding an extra Python layer do do
syntax like you've described, and that is definitely going in the
proposal. However, if the actual SWIG-level bindings have to be fixed
in multiple non-trivial ways before I can even start on that, it's going
to limit the amount of time I can spend actually 'pythonificating'.
Apologies if I wasn't clear on that.
-Walter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue May 2 19:54:13 2006