Refactor spec/version matching.

Instead of choosing the comparison on each `.match()` call, the
expression is converted to a combination of `Range()` expressions
(simple comparison to a semver-compliant `Version`).

`Range()` objects can be combined with `And` and `Or` through the
`AnyOf` and `AllOf` clauses (sticking to Python's naming scheme).

Some specific flags have been provided to those range, allowing users to
subtly alter the matching behaviour - thus accomodating different
versioning schemes:
- `<0.1.2` won't match `0.1.2-rc1`, unless the prerelease_policy flag is
  set to either `always` or `same-patch`
- `<0.1.2` will match `0.1.1-rc1`, unless the `prerelease_policy` flag
  is set to `same-patch`
- `==0.1.2` will always match `0.1.2+build44`, unless the `build_policy`
  is set to `strict`.

The `Spec` item has been updated, alongside `SpecItem`.
Those objects keep the original expression as attributes, but don't use
them for comparisons.

1 files changed, 5 insertions, 0 deletions

diff --git a/ChangeLog b/ChangeLog
index 687d899..169bd2a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -18,6 +18,11 @@ ChangeLog
 
     * Remove support for Python2 (End of life 4 months after this release)
 
+*Refactor:*
+
+    * Switch spec computation to a two-step process: convert the spec to a combination
+      of simple comparisons with clear semantics, then use those.
+
 
 2.6.0 (2016-09-25)
 ------------------