coverage2sql

History

Hervé Beraud 12b53e108a 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: I46f1872407495af231e65cfe784cee731b345f3b		2020-06-02 20:09:13 +02:00
..
versions	Update hacking for Python3	2020-03-28 10:47:17 +01:00
README	Add migration and shell	2016-04-19 19:00:55 +09:00
__init__.py	Add __init__.py to migrations	2016-04-19 19:06:03 +09:00
alembic.ini	Add unit tests and remove oslo_db	2016-11-11 11:33:43 +09:00
cli.py	Update hacking for Python3	2020-03-28 10:47:17 +01:00
env.py	Stop to use the __future__ module.	2020-06-02 20:09:13 +02:00
script.py.mako	Add migration and shell	2016-04-19 19:00:55 +09:00

Generic single-database configuration.