Enable Ruff UP rules

[cbrnr]

This PR enables Ruff UP rules (pyupgrade). These rules check if newer language constructs can be used (it automatically uses the minimum required version from pyproject.toml, so 3.9 in this case). I've only fixed some of the errors, the remaining ones need a bit more manual work. Thanks @hoechenberger for pointing out this very nice tool!

Edit: tutorials and examples are done.

[hoechenberger]

Very nice, I generally like the idea of making use of modern language features.

I only hope we don't accidentally introduce new bugs.....

[cbrnr]

I only hope we don't accidentally introduce new bugs.....

If this happens, our tests need to be udpated.

[cbrnr]

And at least one person needs to go over all changes I'm afraid.

[cbrnr]

Turns out this is a huge PITA. If anyone wants to take over the remaining ~350 conversions from % to f-string, please knock yourselves out. Otherwise, I'll do it sometime soonish, but probably not in the next days.

[hoechenberger]

I don't think we "need" to do these ... I mean it's great you're donating so much of your time, but I'm not sure if those strings are worth the effort!

[drammock]

Turns out this is a huge PITA. If anyone wants to take over the remaining ~350 conversions from % to f-string, please knock yourselves out. Otherwise, I'll do it sometime soonish, but probably not in the next days.

Thanks for getting the ball rolling; may I suggest disabling UP031 and merging this sooner, and opening an issue (maybe tagged good-first-issue?) to re-enable it and fix the %s later?

[cbrnr]

Yes, sure. Can we keep the changes I've already made?

[drammock]

Yes, sure. Can we keep the changes I've already made?

of course!

[hoechenberger]

Great idea, @drammock!

[cbrnr]

This should be good to go. I've created #12360 to follow up; we don't have a "good first issue" label, so I've used "EASY" for now (but feel free to change it).

[cbrnr]

We get some Numpy 2.0 related errors in Pyvista/Pyvistaqt. It seems like there's no issue in their repos yet, since they probably do not test against pre-release Numpy.

[drammock]

We get some Numpy 2.0 related errors in Pyvista/Pyvistaqt. It seems like there's no issue in their repos yet, since they probably do not test against pre-release Numpy.

I've just opened pyvista/pyvista#5472, and pyvista/pyvista#5473 to fix it.

[cbrnr]

Thanks! Let me know once the PR is merged, I can then re-run the pip-pre job.