Hervé Beraud 99841adb93 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: I292be888fef955705fae5e29c27d4083ae455d59		2020-06-02 20:34:33 +02:00
..
tests	Use unittest.mock instead of third party mock	2020-04-22 20:39:38 +00:00
__init__.py	Reorganize into package and add tox for testing	2016-07-14 12:23:41 -05:00
auth.py	Fix tox pep8 errors and add parenthesis to print.	2018-03-14 08:00:05 +00:00
build_nodes_json.py	Update default power managemnt driver to 'ipmi'	2020-03-16 14:29:25 +01:00
deploy.py	Stop to use the __future__ module.	2020-06-02 20:34:33 +02:00
openstackbmc.py	bmc: assume powering-on state is ACTIVE	2019-12-09 16:51:39 -05:00