Apply black to the files still involved in other pull requests

[Remi-Gau]

• realized that during the hackathon some people would use black and end up reformating files that should not have because they are still involved in other PRs
• some of the PRs with those files have been opened for a certain amount of time and it may still take some time for them to be finished

it would be nice to find a way to be able to apply black to the whole codebase and minimize merge conflicts on those old PRs

possible route:

• apply black to a file in main
• use the same black config to reformat the file in the PR
• hopefully this should be easy (#FamousLastWords)

[bthirion]

No better suggestion. How far are we with black. I thought it was over (did not check carefully, sorry).

[Remi-Gau]

We are done for all the files not involved in PR.
The list of excluded files is in the pyproject.toml.
But during the hackathon we realized that those excluded files can still lead to headaches if people's IDE is set to auto reformat or if they run black manually on some files.
So it is better to find a way to finish the job completely.

[bthirion]

We should try your approach in one submodule and see how well it goes.

[Remi-Gau]

Either that or do it PR by PR.

[ymzayek]

We can start with files in PRs opened by core devs

[Remi-Gau]

You read my mind.

[Remi-Gau]

started trying "fixing black" on some of the old PRs... it feels that it will prove a bit of headache in any case
will try with a couple more but it seems that there will always some merge conflicts to fix

[bthirion]

But "There is no alternative" as they put it...

[ymzayek]

I linked these latest PRs here but I misread the title of the issue. The new blacked files are NOT involved in pull requests