<div dir="ltr"><div><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 1, 2014 at 12:25 AM, Ethan Furman <span dir="ltr"><<a href="mailto:ethan@stoneleaf.us" target="_blank">ethan@stoneleaf.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">One argument that keeps coming up is transferability of knowledge:  knowing git and/or GitHub, as many seem to, it<br>
therefore becomes easier to commit to the Python ecosystem.<br>
<br>
What about the transferability of Python knowledge?  Because I know Python, I can customize hg;  because I know Python I<br>
can customize Roundup.<br>
<br>
I do not choose tools simply because they are written in Python -- I choose them because, being written in Python, I can<br>
work on them if I need to:  I can enhance them, I can fix them, I can learn from them.<br>
<br></blockquote><div><br></div><div><div>There are lots of Python tools written with Git:</div><div><br></div><div>* <a href="https://pypi.python.org/pypi/vcs">https://pypi.python.org/pypi/vcs</a></div><div>* <a href="https://pypi.python.org/pypi/dulwich">https://pypi.python.org/pypi/dulwich</a><br></div><div>* <a href="https://pypi.python.org/pypi/hg-git">https://pypi.python.org/pypi/hg-git</a></div><div>* <a href="http://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html">http://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html</a> ("GitFS")</div><div>  * <a href="https://github.com/libgit2/pygit2">https://github.com/libgit2/pygit2</a> (C)</div><div>  * <a href="https://pypi.python.org/pypi/GitPython">https://pypi.python.org/pypi/GitPython</a> (Python)</div><div>* <a href="https://pypi.python.org/pypi/pyrpo">https://pypi.python.org/pypi/pyrpo</a> (subprocess wrapper for git, hg, bzr, svn)</div></div><div> </div></div></div></div>