Issue 6850 - Remove generation of checksums

README.md

 # python-abp
 
 This repository contains a library for working with Adblock Plus filter lists
 and the script that is used for building Adblock Plus filter lists from the
 form in which they are authored into the format suitable for consumption by the
 adblocking software.
 
 ## Installation
 
 Prerequisites:
@@ skipping 10 matching lines @@
 
 The filter lists are originally authored in relatively smaller parts focused
 on a particular type of filters, related to a specific topic or relevant
 for particular geographical area.
 We call these parts _filter list fragments_ (or just _fragments_)
 to distinguish them from full filter lists that are
 consumed by the adblocking software such as Adblock Plus.
 
 Rendering is a process that combines filter list fragments into a filter list.
 It starts with one fragment that can include other ones and so forth.
-The produced filter list is marked with a version and a timestamp.
+The produced filter list is marked with a [version and a timestamp][1].
 
 Python-abp contains a script that can do this called `flrender`:
 
     $ flrender fragment.txt filterlist.txt
 
 This will take the top level fragment in `fragment.txt`, render it and save into
 `filterlist.txt`.
 
 The `flrender` script can also be used by only specifying `fragment.txt`:
     
@@ skipping 79 matching lines @@
 lines of a filter list: `parse_line`. It returns a parsed line object just like
 the items in the iterator returned by `parse_filterlist`. 
 
 For further information on the library API use `help()` on `abp.filters` and
 its contents in interactive Python session, read the docstrings or look at the
 tests for some usage examples.
 
 ## Testing
 
 Unit tests for `python-abp` are located in the `/tests` directory.
-[Pytest][3] is used for quickly running the tests
+[Pytest][2] is used for quickly running the tests
 during development.
-[Tox][4] is used for testing in different
+[Tox][3] is used for testing in different
 environments (Python 2.7, Python 3.5+ and PyPy) and code quality
 reporting.
 
 In order to execute the tests, first create and activate development
 virtualenv:
 
     $ python setup.py devenv
     $ . devenv/bin/activate
 
 With the development virtualenv activated use pytest for a quick test run:
 
     (devenv) $ pytest tests
 
 and tox for a comprehensive report:
 
     (devenv) $ tox
 
 ## Development
 
 When adding new functionality, add tests for it (preferably first). Code
 coverage (as measured by `tox -e qa`) should not decrease and the tests
 should pass in all Tox environments.
 
 All public functions, classes and methods should have docstrings compliant with
-[NumPy/SciPy documentation guide][5]. One exception is the constructors of
+[NumPy/SciPy documentation guide][4]. One exception is the constructors of
 classes that the user is not expected to instantiate (such as exceptions).
 
  [1]: https://adblockplus.org/filters#special-comments
- [2]: https://adblockplus.org/filters#options
- [3]: http://pytest.org/
- [4]: https://tox.readthedocs.org/
- [5]: https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt
+ [2]: http://pytest.org/
+ [3]: https://tox.readthedocs.org/
+ [4]: https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt