| commit | 8aea021537f72821b2015fe945629982d4aae8ce | [log] [tgz] |
|---|---|---|
| author | Hervé Beraud <hberaud@redhat.com> | Tue Jun 02 21:01:54 2020 +0200 |
| committer | Felipe Monteiro <felipe.carneiro.monteiro@gmail.com> | Fri Jul 24 04:27:38 2020 +0000 |
| tree | 77e5aa63e18b3d89d990a47185e858e44cecc9a4 | |
| parent | 257f3b009f7978723a8748f9f5b413aa8eb38e3a [diff] |
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: I522388e474c205aa2bdf2e5167193f4e6b3381a4