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.

Changes between revision 1 and 2

orig
1
2

Commits

Summary ID Author
Get rid of __future__ imports
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. Testing Done: Ran unit tests.
e72a32b6b97ed0a817756f04c96b75c694fc76f7 David Trowbridge
Get rid of __future__ imports
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. Testing Done: Ran unit tests.
7a1c28c14bf3000e5ac3b934588f4ae2239462df David Trowbridge
djblets/dependencies.py
djblets/settings.py
djblets/extensions/staticfiles.py
djblets/extensions/tests/test_templatetags.py
djblets/registries/errors.py
djblets/testing/testcases.py
djblets/util/humanize.py
djblets/util/tests/test_compressed_tags.py
djblets/util/tests/test_djblets_utils_tags.py
djblets/util/tests/test_json_utils.py
djblets/webapi/errors.py
djblets/webapi/resources/base.py
Loading...