Pandas 2.2; remove some deprecated behavior; update black+pyright

[twoertwein]

Also reduced the number of failures on nightly, but it still fails.

I should have put the black changes in a different commit, but I realized that too late.

edit: run black on a new branch, rebased, and force pushed to separate black and the other changes

[twoertwein]

(Not too keen on the new formatting)

[Dr-Irv]

thanks @twoertwein .

I had to resolve some merge conflicts.

[twoertwein]

Thank you for taking care of the conflicts!

Can probably have a new release - or wait for the open PRs!

[Dr-Irv]

Can probably have a new release - or wait for the open PRs!

I'm going to wait for the open PR's.

Will you see if you can get nightly working?

[twoertwein]

I think I can get that done this evening. How do we want to handle breaking changes in 3.0 (that do not warn on 2.2 but fail on 3.0)? Ignore in the CI or proactively remove them from the stubs? I'm fine with either.

[Dr-Irv]

I think I can get that done this evening. How do we want to handle breaking changes in 3.0 (that do not warn on 2.2 but fail on 3.0)? Ignore in the CI or proactively remove them from the stubs? I'm fine with either.

Don't change the stubs for nightly. Just change the test modules so that they avoid/change the test if the version is larger than 2.2.99.

In tests/__init__.py, we have this:

PD_LTE_21 = Version(pd.__version__) < Version("2.1.999")

So you'd change that to now be PD_LTE_22 using version 2.2.999 and then if some test is inappropriate for nightly, just surround it with if PD_LTE_22 so that it runs with 2.2., but is skipped on nightly.