C. Michael Pilato wrote:
> David James writes:
> > C. Michael Pilato wrote:
> > > I have to say (and have said in a few private email already today)
> > > that I'm quite confused by the point of this whole effort.
> > Would you prefer if I took the more direct approach and just built
> > thorough tests for the Python bindings? I'm not married to the idea of
> > creating a command-line client in Python. :) In fact, it might make my
> > life easier to take the direct approach. What do you think?
> I would very much prefer such a thing. I've started down the road
> myself several times, but kept getting hung up on our build system.
> I'd like it very much if 'make swig-py' would create ready-to-install
> / ready-to-test modules linked against the C libraries still in the
> build tree. Upon that foundation could 'make swig-py-check' be built.
Sounds good. I think that your suggested approach would be easier and
could offer more benefits to the project as a whole. If I keep the
tests relatively simple, it will leave more time for me to work on
other aspects of the bindings, such as automatic pool management.
Opinions?
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 29 20:24:57 2005