Skip to content
Structure-aware diff for html and xml documents
Python Shell
Latest commit 0e28f56 May 12, 2011 @christian-oudard Merge pull request #1 from lucaswiman/patch-1
Add html5lib dependency
Failed to load latest commit information.
htmltreediff Fixed text splitting on non-recognized characters. Mar 18, 2011
LICENSE Added a BSD-style license file. Feb 17, 2011
MANIFEST.in Fixed contents of the manifest file. Dec 17, 2010
README.rst
pylint.sh
pylintrc
run_tests.sh Refactored the last of the test cases into parameterized tests. Feb 11, 2011
setup.py

README.rst

HTML Tree Diff

Structure aware diff of XML and HTML documents.

The intended use is to concisely show the edits that have been made in a document, so that authors of html content can review their work.

What do we mean by "HTML Tree Diff"?

  • HTML: The inputs to the diff function are HTML documents
  • Tree: It considers the full XML tree structure of the inputs, not just text based changes.
  • Diff: The output is human-readable HTML, using <ins> and <del> tags to show the changes.

Command line interface

You can execute htmltreediff.cli directly as a python module, passing it html files to diff:

$ python -m htmltreediff.cli one.html two.html
<h1>
  <del>
    one
  </del>
  <ins>
    two
  </ins>
</h1>

Python API

You can also use htmltreediff from within a python program as a library.

For HTML Changes:

>>> from htmltreediff import diff
>>> print diff('<h1>...one...</h1>', '<h1>...two...</h1>', pretty=True)
<h1>
  ...
  <del>
    one
  </del>
  <ins>
    two
  </ins>
  ...
</h1>

And also for text-only changes:

>>> print diff(
...     'The quick brown fox jumps over the lazy dog.',
...     'The very quick brown foxes jump over the dog.',
...     plaintext=False,
... )
The <ins>very </ins>quick brown <del>fox jumps</del><ins>foxes jump</ins> over the<del> lazy</del> dog.

Running the unit tests

The unit test suite requires the packages nose and coverage to run. Just run the run_tests.sh script, and all the tests will run, with code coverage. Code coverage should always be at 100%.

Something went wrong with that request. Please try again.