On Fri, Jun 13, 2008 at 4:46 PM, Sage La Torra <sagelt_at_gmail.com> wrote:
> On Wed, Jun 11, 2008 at 2:16 PM, David Glasser <glasser_at_davidglasser.net>
> wrote:
>>
>> On Tue, Jun 10, 2008 at 8:26 AM, David James <james_at_cs.toronto.edu> wrote:
>> > On Mon, Jun 9, 2008 at 5:01 AM, John Szakmeister <john_at_szakmeister.net>
>> > wrote:
>> >> Hi! I assume that this email is reaching the same David James that is
>> >> part of the Subversion project. I just wanted to ping you about the
>> >> status of ctypesgen... and for that matter, csvn. It appears
>> >> development has stalled (I'm not complaining... I certainly understand
>> >> having demands for your time). I didn't know if this was a sign of
>> >> "it's ready for prime time" or if you (and others) just didn't have
>> >> the energy to finish it.
>> >>
>> >> I'd be interested in helping... I don't like SWIG much, and ctypes is
>> >> a pain for complex APIs without something to help it. :-) BTW, is
>> >> there a group that I should be posting this on? I didn't see anything
>> >> on the Google Code page.
>> >
>> > Hi John,
>> >
>> > That's great news! We could certainly use the help.
>> >
>> > Right now, the ctypes python bindings are in pretty good shape. The
>> > low level bindings (which are similar to the SWIG bindings) are
>> > complete and work really reliably and well.
>> >
>> > We also have higher level python wrappers, which make it really easy
>> > to use the python bindings.
>> >
>> > The biggest work we need to do is figure out how to build the ctypes
>> > bindings on Windows. It may be possible to just build the ctypes
>> > python wrapper on Linux and copy it over to Windows and make a few
>> > changes and it will work. This is because we are generating pure
>> > Python bindings so in theory they could be platform independent. Note
>> > that you will need Subversion as a DLL to use them in ctypes on
>> > Windows, and that is a new feature in Subversion 1.5.
>> >
>> > Currently the ctypes python bindings are on a branch and working
>> > pretty well, but I'm not sure about where to go from here.
>> >
>> > I see two options:
>> > 1) Merge the ctypes Python bindings to trunk and integrate them with
>> > the Subversion build system
>> > 2) Launch ctypes bindings as a separate project.
>> >
>> > Where do you think we should go from here?
>>
>> I think we should ship the low-level, automatically-generated ctypes
>> bindings with Subversion starting with 1.6, and launch the high-level
>> more usable library built on top of that as a separate project.
>
> +1. I think that getting the full ctypes version into trunk will meet with
> some resistance, but this approach gets all the code out there and gets the
> most important part into trunk.
>
> Hopefully I'll have time to start coding again, getting my Master's
> seriously sidetracked development. Once I get set up at my new job I'll
> hopefully have a life again, and I can track down the few remaining issues.
Awesome! It would be great to see you having time to help out with
ctypes and svn again.
--dave
--
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-06-16 21:49:24 CEST