On Thu, Dec 8, 2011 at 3:11 PM, Luke Kenneth Casson Leighton <[email protected]> wrote: > On Thu, Dec 8, 2011 at 7:50 PM, Lex Berezhny <[email protected]> wrote: > > 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 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? 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. 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. If we are python programmers than wouldn't it make sense to use the open source tools common in the python ecosystem? - lex

