A bunch of `DeprecationWarning`s got promoted to `ExpiredDeprecationError` post-release, so we should update the tests. Would be good to expect the exception in 3.0.x and remove the deprecated code in `master`.