Hervé Beraud 64e3c41167 Stop to use the __future__ module. ... The __future__ module [1] was used in this context to ensure compatibility between python 2 and python 3. We previously dropped the support of python 2.7 [2] and now we only support python 3 so we don't need to continue to use this module and the imports listed below. Imports commonly used and their related PEPs: - `division` is related to PEP 238 [3] - `print_function` is related to PEP 3105 [4] - `unicode_literals` is related to PEP 3112 [5] - `with_statement` is related to PEP 343 [6] - `absolute_import` is related to PEP 328 [7] [1] https://docs.python.org/3/library/__future__.html [2] https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html [3] https://www.python.org/dev/peps/pep-0238 [4] https://www.python.org/dev/peps/pep-3105 [5] https://www.python.org/dev/peps/pep-3112 [6] https://www.python.org/dev/peps/pep-0343 [7] https://www.python.org/dev/peps/pep-0328 Change-Id: I82b61a2d7687ff109051815e01619eb612ea9073		2020-06-02 20:14:31 +02:00
..
drivers	Stop to use the __future__ module.	2020-06-02 20:14:31 +02:00
__init__.py	doc: Clean up unnecessary left vertical lines	2019-12-23 13:58:32 +00:00
base.py	Remove vim header	2014-01-14 16:03:28 +00:00
cleaner.py	Remove vim header	2014-01-14 16:03:28 +00:00
client.py	Add cache-manage utility using v2 API	2019-02-27 06:43:13 +00:00
prefetcher.py	Fix string interpolation to delay by logging	2020-01-09 08:53:55 -06:00
pruner.py	Remove vim header	2014-01-14 16:03:28 +00:00