On Thu, Dec 8, 2011 at 2:11 PM, Luke Kenneth Casson Leighton <[email protected]> wrote: > On Thu, Dec 8, 2011 at 7:50 PM, Lex Berezhny <[email protected]> wrote: >> >> If we're going to be pure than we should also switch from git to >> mercurial. Mercurial has all of the features of git and it's written >> in Python. I think mercurial should be used by default unless there is >> a good reason to not use it and instead to use git. > > ahh... now you've got me :) git was written by absolute sodding > geniuses. i have more respect for the developers of git than i do for > the developers of mercurial, so mercurial is out. > > howeverrr, it _is_ possible to "have cake and eat it" because there > exists a python implementation of git, called "dulwich". it was under > development at the time so i went with python-git. python-git was > investigating conversion over to use dulwich, so it would just mean > doing an upgrade (he said, crossing fingers...) and the > python-git-jsonrpc service that i wrote would then be an entirely > python-based solution... that so happened to be completely compatible > with the format of the git object store.
i believe dulwich may use libgit2 if it's available, but libgit2 implements most of what you need anyway, save the network protocol. it's been quite some time since i looked at Mercurial, but i use git specifically because it's incredibly simple a the bottom most layer -- 3 object types, and key/value. it can be explained in one paragraph. all the "complexity" at higher levels is simply due to the incredible flexibility stemming from this inherent simplicity ... a fractal of self-repeating DAG rules. On Thu, Dec 8, 2011 at 2:29 PM, Lex Berezhny <[email protected]> wrote: > > I don't understand the logic of using git because you respect the > developers but then saying you're okay with switching to dulwich. Is > dulwich written by the same developers as git? for me at least it's less the developers, and more the fact that git's data structure ... for lack of a better word, rocks. > If you're willing to switch to dulwich, why not switch to mercurial? > Lots of prominent open source Python projects (including python > itself) use mercurial. indeed, but python mainly chose that because it was a bit more favored among the core devs, and worked better on windows. > Seems like almost by definition mercurial will be better maintained > and more stable than dulwich by the shear number of users and > developers of mercurial. i'd wager git has an order of magnitude more steam in both depts ... there are oodles of projects that not only use git, but are built *on* it, eg ikiwki/bup/etc. recently on the btrfs mailing list, C. Mason recommended using git's packfile format and other git concepts for implementing btrfs-send/recieve (all related xfering a filesystem to a remote machine, IIRC) because it had "so much weight/interest behind it". git-fast-export and friends have also more-or-less become the defacto interchange format between SCMs. imo ... git > $insert_competitor :-) -- C Anthony

