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/conditions/operators.py
djblets/conditions/values.py
djblets/conditions/tests/test_choices.py
djblets/conditions/tests/test_conditions.py
djblets/conditions/tests/test_operators.py
djblets/conditions/tests/test_values.py
djblets/configforms/apps.py
djblets/configforms/forms.py
djblets/configforms/mixins.py
djblets/configforms/pages.py
djblets/configforms/registry.py
djblets/configforms/views.py
djblets/configforms/tests/test_config_page.py
djblets/configforms/tests/test_config_page_form.py
djblets/configforms/tests/test_config_page_registry.py
djblets/configforms/tests/test_config_pages_view.py
djblets/datagrid/apps.py
djblets/datagrid/grids.py
djblets/datagrid/tests.py
djblets/datagrid/templatetags/datagrid.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...