FlaskRedis.init_app method no longer takesstrict parameter. Pass this flag when creating your FlaskRedis'REDIS', so unless you change that, you can still access the extension viaapp.extensions['redis'] as before.redis.StrictRedis. You can switch back to the old redis.Redis class bystrict=False in the FlaskRedis kwargs.Redis keyword arguments (such asdecode_responses) to FlaskRedis and they will be correctly passed overredis-py instance. Thanks, @giyyapan!redis_store['key'] = value, redis_store['key'], anddel redis_store['key'] is now supported. Thanks, @ariscn!flask_redis.Redis to
flask_redis.FlaskRedis. Using the old name still works, but emits
a deprecation warning, as it will be removed from the next versionREDIS_DATABASE (or equivalent) now
emits a deprecation warning as it will be removed in the version in
favor of including the database number in REDIS_URL (or
equivalent)FlaskRedis.from_custom_provider(provider) class method for
using any redis provider class that supports instantiation with a
from_url class methodstrict parameter to FlaskRedis which expects a boolean
value and allows choosing between using redis.StrictRedis and
redis.Redis as the defualt provider.FlaskRedis register as a Flask extension through Flask's
extension API__getattr__ magic method to pass calls to the underlying
client