[1/N] Use list,tuple,dict for typing

[cyyever]

What does this PR do?

Replace typing.{List,Tuple,Dict} with {list, tuple,dict}. Due to the large amount of all changes, they are split into smaller PRs.

[ydshieh]

Happy to have these changes. But could this be produced via a single command?

[Rocketknight1]

Hi @cyyever, yes, this looks good! But as @ydshieh said, for security reasons it's preferable if we can run a command to do the update ourselves, because reviewing a 15k line diff manually is challenging. Can you give us the command / script you used to make this?

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

[ydshieh]

They are several PRs and now I am a bit lost

#37809
#37039

etc.

I'm not completely against the PRs, update ruff could be OK from time to time, there is no hard rules about the decisions.

For this PR (simply changing {List,Tuple,Dict} with {list, tuple,dict}., it's ok.

[cyyever]

@ydshieh Thank you, these are also based on ruff and sed, focusing on these types for easier review.

[cyyever]

Happy to have these changes. But could this be produced via a single command?

No because ruff is not strong enough to fix comments.
For your audit, ruff UP006 was used, followed by

sed -i -e 's/\<Dict\]/dict]/g'  src/**/*.py
sed -i -e 's/\[Dict/[dict/g'  src/**/*.py
sed -i -e 's/\<\[Dict/[dict/g'  src/**/*.py
sed -i -e 's/\<Dict\[/dict[/g'  src/**/*.py
sed -i -e 's/\<Tuple\[/tuple[/g'  src/**/*.py
sed -i -e 's/\<List\[/list[/g'  src/**/*.py
sed -i -e 's/\<typing.tuple\[/tuple[/g'  src/**/*.py
sed -i -e 's/\<typing.list\[/list[/g'  src/**/*.py

ruff format was also used after all changes.

[Rocketknight1]

cc @ydshieh @cyyever, if you're okay with it, I'll make a new PR to:

1. Add UP006 to our ruff checks
2. Apply it
3. Run the sed commands above

Obviously, I expect this to be exactly the same as this PR, but it's just for security reasons!

[ydshieh]

Yes, go ahead. Thank you a lot.

I'm not sure what 1/N means in the title, but let's not be distracted frequently by this ruff stuffs 🙏 .

If you have a list of things to be updated before py39 reaches EOL, let's see if we can do it once (you can open an issue to describe them and we can discuss).

[cyyever]

@Rocketknight1 Do what you want. But commit 23aea60 is required and should be picked to fix checkers.

[cyyever]

@ydshieh I prefer following @Rocketknight1 's advice, he makes a big PR from some commands that is reproducible and be reviewed internally.