This assertion was missing in commit 6bb804dc.

To complete a todo item that you finished yesterday, run

    topydo do -d yesterday

Or

    topydo do -d -1d

Inspired by issue #82.

When an ordinal tag filter is negated (i.e. -id:1), then this isn't seen
as a negation but as an ordinal tag filter with tag -id and value 1.
Which isn't likely to exist, resulting in every todo item to be excluded
from the result.

Related to commit cde8f8ed

https://bitbucket.org/ned/coveragepy/issues/90/lambda-expression-confuses-branch

When the due date tag or the start date tag is set, convert the value to
an absolute date if a relative date was given.

An explicit start date is given with the t: tag (unless configured
otherwise). Together with the due date, the start date is used to
calculate the length of a todo item (in days).

When no explicit start date is given, consider the creation date as the
start date (if present).

Improves branch coverage. Also related to commit cde8f8ed.

The lambdas, which are not all run, cause coverage to think that the
jump to the function exit was never made, polluting the results.
Therefore add this pragma to mask these instances of missing branch
coverage.

See also:

https://bitbucket.org/ned/coveragepy/issues/90/lambda-expression-confuses-branch

The result of a minor merge error.

This reverts commit bbdfb2a5.

(Wheel) dependencies are evaluated at build time, so they should stay in
extras_require, which are evaluated at install-time.

See issue #79.

Add new tests to increase lib coverage

Mainly adds a missed case in ExpressionCommand, where priority filters were not covered.

Installing from the source distribution (sdist), ushlex and
shutil_get_terminal_size were not installed. Putting the condition in
install_requires addresses this.

Oops! Almost forgotten.

When a user requests a specific todo ID, always show it, even when the
todo item is not relevant.

Conflicts:
	topydo/commands/ListCommand.py

Conflicts:
	setup.py

Also marked a few functions private.

Move format parsing logic to ListFormatParser

This way we can safely remove `PrettyPrinterIndentFilter` and output
length is still properly maintained by `ListFormatParser`.

ListFormatParser is now the core of PrettyPrinterFormatFilter, but can
also be easily used in another areas. Whole functionality of
PrettyPrinterAlignFilter was also moved into it.

Main advantage of having separate parser for list_format is possibility
of initializing it and resolving placeholders only once. Previous
implementation did that with each Todo object.

- From now on literal `%` signs always have to be escaped with `\` (`\%`),
even inside conditional braces.
- `%%` won't work anymore.
- Nonexistent placeholders (for example`%&`) will be expanded to empty
  strings (`''`).

This change fixes also some bugs:
- inappropriate output width when \t was used without %S
  (example: `%p{ }\t%{ }p`)
- curly braces inside conditional braces (example: `%{{}p{}}`)

Minor: recognize literal `\t` in list_format config option and in `-F`.