Here's a roundup of tools links, to make sure we're all on the same page: Git HG Rosetta Stone =================== https://github.com/sympy/sympy/wiki/Git-hg-rosetta-stone#rosetta-stone BugWarrior =========== BugWarrior works with many issue tracker APIs https://warehouse.python.org/project/bugwarrior/ bugwarrior is a command line utility for updating your local taskwarrior
database from your forge issue trackers. It currently supports the following remote resources:
- github (api v3) - bitbucket - trac - bugzilla - megaplan - teamlab - redmine - jira - activecollab (2.x and 4.x) - phabricator
[...]
DVCS Interaction ================ Hg <-> Git ---------------- * https://warehouse.python.org/project/hg-git/ (dulwich) * hg-github https://github.com/stephenmcd/hg-github Git <-> Hg ------------------ * https://pypi.python.org/pypi/git-remote-hg/ * https://github.com/felipec/git-remote-hg Python <-> Hg ----------------------- | Wikipedia: https://en.wikipedia.org/wiki/Mercurial | Homepage: http://hg.selenic.org/ | Docs: http://mercurial.selenic.com/guide | Docs: http://hgbook.red-bean.com/ | Source: hg http://selenic.com/hg | Source: hg http://hg.intevation.org/mercurial/crew * http://evolution.experimentalworks.net/doc/user-guide.html * (growing list of included extensions) Python <-> Git ---------------------- * GitPython, pygit2 (libgit2), dulwich * https://github.com/libgit2/pygit2 (libgit2) * https://pythonhosted.org/GitPython/ (Python) * https://github.com/jelmer/dulwich (Python) * http://docs.saltstack.com/en/latest/topics/tutorials/gitfs.html#installing-d... GitHub -> BitBucket ----------------------------- * https://bitbucket.org/ZyX_I/gibiexport Sphinx Documentation ==================== * http://read-the-docs.readthedocs.org/en/latest/webhooks.html * https://github.com/yoloseem/awesome-sphinxdoc * changelogs, charts, csv, ipython, %doctest_mode Is there an issue ticket or a wiki page that supports Markdown/ReStructuredText, where I could put this? Which URI do we assign to this artifact? On Mon, Dec 1, 2014 at 8:37 AM, Wes Turner <wes.turner@gmail.com> wrote:
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)