• 
      

    Get rid of __future__ imports

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

    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.

    Summary ID
    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
    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)
       
       
      Show all issues

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

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

      Too many blank lines.

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

      "Django"

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

      Too many blank lines.

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

      Too many blank lines.

    7. 
        
    david
    chipx86
    1. Ship It!
    2. 
        
    david
    Review request changed
    Status:
    Completed
    Change Summary:
    Pushed to release-3.x (9282724)