72bc9a91ab
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: Ifd61bc8e043ac9af446ae31bffd82f67f34facbc
This directory contains the plumbing for the Alembic migrations that modify the Monasca database. If you need to add a new migration, run alembic revision -m '<revision message>' in this directory, where <revision message> is a short description for what your migration does such as 'Add volume field to alarm'. Alembic will then create a revision script in the alembic/versions/ directory. You will need to edit this script to add upwards and downwards migrations for the change you want to make.