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/privacy/tests/test_base_consent_requirement.py
djblets/privacy/tests/test_consent_config_page_form_mixin.py
djblets/privacy/tests/test_consent_data.py
djblets/privacy/tests/test_consent_form_mixin.py
djblets/privacy/tests/test_consent_requirement_field.py
djblets/privacy/tests/test_consent_requirement_hook.py
djblets/privacy/tests/test_consent_requirement_widget.py
djblets/privacy/tests/test_consent_requirements_registry.py
djblets/privacy/tests/test_consent_tracker.py
djblets/privacy/tests/test_consent_views.py
djblets/privacy/tests/test_djblets_privacy_tags.py
djblets/privacy/tests/test_multi_consent_requirement_widget.py
djblets/privacy/tests/test_multi_consent_requirements_field.py
djblets/privacy/tests/test_pii.py
djblets/privacy/tests/testcases.py
djblets/recaptcha/apps.py
djblets/recaptcha/mixins.py
djblets/recaptcha/siteconfig.py
djblets/recaptcha/widgets.py
djblets/recaptcha/templatetags/djblets_recaptcha.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...