Fix changed imports in dogpile.cache 0.6.0

In the latest release of dogpile.cache, 0.6.0, a couple of backwards
incompatible import rejiggering broke our usage in openstack-health's
distributed dbm backend proxy. This commit updates the imports to work
with 0.6.0 and newer versions of dogpile.cache.

Change-Id: Iad50ab66c88a2164146fea98edf435a445e0ee6c
This commit is contained in:
Matthew Treinish 2016-06-07 11:52:08 -04:00
parent 2a69274760
commit 2a447a8c5d
No known key found for this signature in database
GPG Key ID: FD12A0F214C9E177
2 changed files with 3 additions and 3 deletions

View File

@ -14,9 +14,9 @@
from dogpile.cache.backends import memcached from dogpile.cache.backends import memcached
from dogpile.cache import compat
from dogpile.cache import proxy from dogpile.cache import proxy
from dogpile.cache import util from dogpile import util
from dogpile.util import compat
from pymemcache.client import base from pymemcache.client import base

View File

@ -4,7 +4,7 @@
pbr>=1.6 # Apache-2.0 pbr>=1.6 # Apache-2.0
Flask<1.0,>=0.10 # BSD Flask<1.0,>=0.10 # BSD
pymemcache >= 1.3.5 # Apache-2.0 pymemcache >= 1.3.5 # Apache-2.0
dogpile.cache>=0.5.7,<0.6.0 # BSD dogpile.cache>=0.6.0 # BSD
subunit2sql>=1.6.0 # Apache-2.0 subunit2sql>=1.6.0 # Apache-2.0
SQLAlchemy<1.1.0,>=1.0.10 # MIT SQLAlchemy<1.1.0,>=1.0.10 # MIT
flask-jsonpify # MIT flask-jsonpify # MIT