bugfix: typo `text` -> `data`
+speed: `textmining.extractor.NamedEntityExtractor`

Small efficiency improvement in NLTK Named Entity Extractors
+func: Named Entity TokenMergers
bumped version numbers
bugfix: banner for Cheshire3 interactive console tuple -> str
+func: improved input navigation in Cheshire3 console

Achieved by importing readline module
bugfix: typo `text` -> `data`
gracefully degrade console UX in absence of readline
bugfix: time delta arithmetic in DateTokenizer

Time delta arithmetic error in calculating last microsecond of any
given year under by 1 day (30th Dec not 31st).
bugfix: flexible end month date in `DateRangeTokenizer`
tests: updated for `DateRangeTokenizer` fixes
style: PEP8 fixes for tokenizer
docs: updated README and CHANGES files
Bugfix release 1.0.16

Merge branch 'hotfix/1.0.16'
Merge tag '1.0.16' into develop

Bugfix release 1.0.15

See CHANGES file for details

Conflicts:
	CHANGES.rst
	README.rst
	VERSION.txt
	cheshire3/commands/console.py
	cheshire3/internal.py
style: consistent message for "0 documents in database"
+func: sortStore contains both lowest and highest value

This enables retrieval of either the low or high value, making results of
ResultSet ordering in ascending/descending order more intuitive. i.e.
when sorting in ascending order the lowest value should be used, when
descending, the highest.
style: `indexStore` PEP8 fixes
style: `resultSet` PEP8 fixes
+func: use low/high value when sorting ascending/descending

When ordering ResultSets by Index, use lowest value for ascending
order, and highest value for descending order.