Switch to pyproject.toml

[xylar]

Summary

Objectives:

• Modernize packaging but switching from setup.cfg and setup.py to pyproject.toml
• Remove a deprecated option in pre-commit config

Select one: This pull request is...

• a bug fix: increment the patch version
• a small improvement: increment the minor version
• a new feature: increment the minor version
• an incompatible (non-backwards compatible) API change: increment the major version

Please fill out either the "Small Change" or "Big Change" section (the latter includes the numbered subsections), and delete the other.

Small Change

• To merge, I will use "Squash and merge". That is, this change should be a single commit.
• Logic: I have visually inspected the entire pull request myself.
• Pre-commit checks: All the pre-commits checks have passed.

[xylar]

Needs to be rebased after #735

[forsyth2]

Thanks @xylar! I reviewed the new commit (e03e7f6). And I see the GitHub Actions are passing for 3.11, 3.12, 3.13.

Once @tomvothecoder signs off on #735, we can merge that one, and then this PR. (I think because the first 6 commits are included in #735, they should just disappear once #735 is merged, but yes rebasing and pushing again would also work).

[xylar]

(I think because the first 6 commits are included in #735, they should just disappear once #735 is merged, but yes rebasing and pushing again would also work).

They won't disappear without a rebase so that will be cleaner.

[forsyth2]

@xylar I just merged https://github.com/E3SM-Project/zppy/pull/739/commits, so you can rebase and merge.

They won't disappear without a rebase

Yes, I see they haven't disappeared. I definitely thought I've seen that happen before though. Maybe a different case.

[xylar]

Yes, I see they haven't disappeared. I definitely thought I've seen that happen before though. Maybe a different case.

The only context I can imagine that working is if the commits get added to main without a merge commit (or a squash commit). Since I never work with branches with that kind of linear history, I haven't seen that before.

[xylar]

In any case, this is rebased and ready for review. Please make sure I didn't accidentally undo any of your most recent changes. I don't think so.

[forsyth2]

The only context I can imagine that working

Hmm maybe I simply forgot that it required a rebase first; in any case, not a big deal.

this is rebased and ready for review. Please make sure I didn't accidentally undo any of your most recent changes. I don't think so.

Yes, this looks good to me, thanks!