Update code to Python 3.7 compliance

[oke-aditya]

Simply runs pyupgrade with the option --py37-plus

Since Python 3.6 has officially reached end of life from this year. It might be nice to keep our code a bit up to date :)

P.S. My health has recovered. And extremely sorry for all the delays this month.

[facebook-github-bot]

💊 CI failures summary and remediations

As of commit 9e6a4ad (more details on the Dr. CI page):

---

💚 💚 Looks good so far! There are no failures yet. 💚 💚

---

This comment was automatically generated by Dr. CI (expand for details).

Please report bugs/suggestions to the (internal) Dr. CI Users group.

Click here to manually regenerate this comment.

[oke-aditya]

This is the solution to run recursively on all python files. I am sure I will forget this command and won't find it easily again. Hence pasting it here.

pyupgrade `find . -name "*.py" -type f` --py37-plus

[pmeier]

Thanks @oke-aditya, LGTM! Although I'm wondering why this only pops up for Python >= 3.7. All of the changes also work for Python 3.6 which is evident by the green CI.

[oke-aditya]

Then I guess our code was already compliant to python 3.7 and we aren't using any special Features introduced in python 3.7.

[pmeier]

Although it looks like we could automate this, #4585 (review) implies that we can't have it as pre-commit hook. This mean, we probably should run pyupgrade regularly to fix stuff like this.

[oke-aditya]

Python 3.7 end of life is in 2023 so probably we don't need to run this soon to upgrade python to 3.8.

But we would need to run it remove code which carries old python syntax.
I guess we can run some cronjob once in 2 months ? Which just reports if such old code exist? Or just leave it as it as. I think doesn't affect much.

[github-actions]

Hey @datumbox!

You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py