Get rid of __future__ imports

Review Request #11944 — Created Jan. 20, 2022 and submitted — Latest diff uploaded

Information

Djblets
release-3.x

Reviewers

Now that Djblets is Python 3.7+, we don't need to import stuff from
__future__ in every file. This change does that, and removes some old
leftover per-file copyright headers while I'm in there.

Ran unit tests.

djblets/extensions/templatetags/djblets_extensions.py
djblets/extensions/testing/__init__.py
djblets/extensions/testing/testcases.py
djblets/extensions/tests/base.py
djblets/extensions/tests/test_base_registry_multi_item_hooks.py
djblets/extensions/tests/test_datagrid_columns_hook.py
djblets/extensions/tests/test_extension.py
djblets/extensions/tests/test_extension_hook.py
djblets/extensions/tests/test_extension_hook_point.py
djblets/extensions/tests/test_extension_info.py
djblets/extensions/tests/test_extension_manager.py
djblets/extensions/tests/test_extension_settings.py
djblets/extensions/tests/test_middleware.py
djblets/extensions/tests/test_setting_list_wrapper.py
djblets/extensions/tests/test_signal_hook.py
djblets/extensions/tests/test_template_hook.py
djblets/extensions/tests/test_templatetags.py
djblets/extensions/tests/test_url_hook.py
djblets/extensions/tests/test_views.py
djblets/extensions/tests/apps/urls.py
This diff has been split across 18 pages: < 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 >
Loading...