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/tests/apps/evolve_tests/models.py
djblets/extensions/tests/apps/evolve_tests/evolutions/__init__.py
djblets/extensions/tests/apps/evolve_tests/evolutions/add_new_field.py
djblets/extensions/tests/apps/model_tests/models.py
djblets/extensions/tests/apps/templatetag_tests/templatetags/templatetag_tests.py
djblets/features/__init__.py
djblets/features/checkers.py
djblets/features/decorators.py
djblets/features/errors.py
djblets/features/feature.py
djblets/features/level.py
djblets/features/registry.py
djblets/features/testing.py
djblets/features/templatetags/features.py
djblets/features/tests/test_checkers.py
djblets/features/tests/test_decorators.py
djblets/features/tests/test_feature.py
djblets/features/tests/test_registry.py
djblets/features/tests/test_template_tags.py
djblets/features/tests/test_testing.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...