GitHub has a better pricing model and is more popular for OSS, hence
the move.

This will allow the CI to run on github rather than gitlab, allowing
me to transfer.

This is a global kill switch that when set to false will prevent any
rate limiting. The usage is meant for testing.

Now it has been released.

The former has been deprecated.

This is based on Quart's configuration.

Note typing now exists for aioredis and pytest.

The latter is correct if there are proxies between the quart app and
the client and equivalent to the former if there are none.

The latest major release changes the API.

This allows the configuration to be moved to pyproject.toml leaving
only flake8.

This has been working well for Quart-Auth and Quart-Schema and so I'm
happy to use here as well.

This upgrades to the latest Quart release, mostly typing related with
a few changes to use Werkzeug more.

Also locally if the redis tox environment is used - it is not default
as I don't have redis locally.

The test failure is related to the latest version of Quart not
providing a method to override the remote address.

By including it in the CI testing.

The recursive and dont-skip arguments are no longer required.

datetime objects cannot be natively stored in redis, so they are
converted to timestamps (floats) that can be.

This can by helpful when adding default limits (or blueprint wide
limits) to ensure that a specific route is no affected by the limits.

This should make it clearer how to use these features.

This allows,

    @rate_limit(1, timedelta(seconds=5))
    @rate_limit(10, timedelta(seconds=60))

to become

    @rate_limit(limits=[
        RateLimit(1, timedelta(seconds=5)),
        RateLimit(10, timedelta(seconds=60)),
    [)

if the user prefers this syntax. It also applies to the
limit_blueprint function.

As there is support to limit a route, and to limit every route in a
app it makes sense to also add support to limit every route in a
blueprint. This is possible via the new ``limit_blueprint`` function.

At some point it seems to have changed from build to pipeline.

This is to ensure that the setup works correctly, and follows a trend
in the Python community of moving code to within a src directory -
particularly as Flask has done so. In addition it looks to clear up
the outstanding confusion with the coverage command.

This allows for tox -e py37 -- … to pass through args to pytest.
pytest: configure testpaths to look into tests/ only.

This copies 3c0b62daeb0d781c2a784ab7f117f436f53a5d78 from Hypercorn
from @blueyed.

Now that Python 3.8 has been released.