Benjamin Peterson added the comment: On Thu, Jun 2, 2016, at 18:28, Martin Panter wrote: > > Martin Panter added the comment: > > FWIW I doubt Git is any better at this than Mercurial: > <https://github.com/python/cpython/blame/master/Lib/test/test_string.py#L190> > > Git can automatically pick up file renames and copies when analysing the > history, but has no special metadata for this. I understand Mercurial is > the opposite (has metadata, but at least by default does not pick up > copies and renames from the history). Perhaps that is what Benjamin was > thinking of. I understand Git will only pick up movements of the majority > of a file, not parts of files (unless something has changed recently).
git blame -C works quite well in my experience for detecting moved lines of code. In general, I think we shouldn't be afraid to reorganize code for fear of breaking "VCS" history. The tools will catch up. (I think they largely have already.) At worst, one must manually "follow" the move of some code through history. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27185> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
