Using an InvalidURLPattern exception instead of just a plain ValueError
make binding regex pattern understand when an arity operator is wrong
add tests for bad routes
unit tests for ok routes
check HTTP method validity
test for valid method and also 'HEAD' presence with 'GET' methods
use terser names like InvalidMethod instead of InvalidRouteMethod