(original) (raw)

On Mon, Dec 1, 2014 at 12:25 AM, Ethan Furman <ethan@stoneleaf.us> wrote:

One argument that keeps coming up is transferability of knowledge: knowing git and/or GitHub, as many seem to, it
therefore becomes easier to commit to the Python ecosystem.

What about the transferability of Python knowledge? Because I know Python, I can customize hg; because I know Python I
can customize Roundup.

I do not choose tools simply because they are written in Python -- I choose them because, being written in Python, I can
work on them if I need to: I can enhance them, I can fix them, I can learn from them.

There are lots of Python tools written with Git:

\* https://pypi.python.org/pypi/vcs

\* https://pypi.python.org/pypi/dulwich

\* https://pypi.python.org/pypi/hg-git

\* http://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html ("GitFS")

\* https://github.com/libgit2/pygit2 (C)

\* https://pypi.python.org/pypi/GitPython (Python)

\* https://pypi.python.org/pypi/pyrpo (subprocess wrapper for git, hg, bzr, svn)