Get rid of __future__ imports

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

david
Djblets
release-3.x
djblets

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.

Summary
Get rid of __future__ imports
Description From Last Updated

This and the import removal snuck into this change instead of the six change.

chipx86chipx86

Too many blank lines.

chipx86chipx86

"Django"

chipx86chipx86

Too many blank lines.

chipx86chipx86

Too many blank lines.

chipx86chipx86
chipx86
  1. 
      
  2. djblets/extensions/testing/testcases.py (Diff revision 1)
     
     

    This and the import removal snuck into this change instead of the six change.

  3. djblets/registries/errors.py (Diff revision 1)
     
     
     
     
     
     
     

    Too many blank lines.

  4. djblets/testing/testcases.py (Diff revision 1)
     
     

    "Django"

  5. djblets/util/humanize.py (Diff revision 1)
     
     
     
     

    Too many blank lines.

  6. djblets/webapi/errors.py (Diff revision 1)
     
     
     
     

    Too many blank lines.

  7. 
      
david
chipx86
  1. Ship It!
  2. 
      
david
Review request changed

Status: Closed (submitted)

Change Summary:

Pushed to release-3.x (9282724)
Loading...