From: David Aguilar <davvid@gmail.com>
To: Jelmer Vernooij <jelmer@samba.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: I've added Dulwich to the Git Wiki
Date: Fri, 16 Jan 2009 18:37:53 -0800 [thread overview]
Message-ID: <402731c90901161837r1c7187dk590c1a46be49e1e9@mail.gmail.com> (raw)
In-Reply-To: <1232146991.24098.13.camel@ganieda.vernstok.nl>
On Fri, Jan 16, 2009 at 3:03 PM, Jelmer Vernooij <jelmer@samba.org> wrote:
>>
>> BTW I find it a bit distressing that more and more projects crop up doing
>> substantial and valuable work around Git, but without even bothering to
>> mention it on this list. There might have been a good chance, too, to
>> avoid having _three_ Python libraries for exactly the same task.
> I wasn't aware of PyGit (and its homepage doesn't seem to work), but
> Python-Git is just a wrapper around the git command line tools, it
> doesn't parse/write the file formats itself.
>
> Cheers,
>
> Jelmer
>
> --
> Jelmer Vernooij <jelmer@samba.org> - http://samba.org/~jelmer/
> Jabber: jelmer@jabber.fsfe.org
>
Hello
This sounds like a great project.
I've talked with the authors of GitPython in the past and I believe
the reason it was never mentioned here was that they were probably too
shy or intimidated (you guys are pretty hardcore ;-) ).
Anyways, as you said, GitPython is purely a wrapper around git
commands. BTW, git is bloody fast so it's actually not that bad and
works pretty well.
GitPython's license is the New BSD license and thus it can't use git
code nor could it use libgit2. I think the best route for a useful
Python module would be to wrap something like libgit2 which aims to be
a true library for git. If that's the goals for Dulwich then all the
better. If not (and it instead aims to be a pure-Python
implementation) then that's cool too, but for performance reasons I
think the community would best be served by pursuing a core git
library with various language bindings built on top of it.
In any case, this sounds like a neat development and it does seem like
the goals are slightly different then the existing GitPython module.
GitPython was basically a port of the Ruby Grit library, which also
just wraps git commands. I'll keep my eye on this and see if there's
anywhere I can help.
--
David
next prev parent reply other threads:[~2009-01-17 2:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 22:42 I've added Dulwich to the Git Wiki Johannes Schindelin
2009-01-16 23:03 ` Jelmer Vernooij
2009-01-16 23:30 ` Johannes Schindelin
2009-01-17 2:37 ` David Aguilar [this message]
2009-01-16 23:04 ` Adeodato Simó
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=402731c90901161837r1c7187dk590c1a46be49e1e9@mail.gmail.com \
--to=davvid@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jelmer@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).