Switching from setup.py to pyproject.toml

[john-science]

What is the change?

Here we are switching from setup.py to pyproject.toml, but the new pyproject.toml file actually replaces:

• MANIFEST.in
• pytest.ini
• requirements-docs.txt
• requirements-testing.txt
• requirements.txt
• ruff.toml
• setup.py

Please notice this means that the version of ARMI is now defined in pyproject.toml not armi/meta.py. So the code has to get the version information from importlib.

Why is the change being made?

The Python Org is forcing our hand on this. The official Python packaging docs now recommend switching to pyproject.toml. So this will close #1124.

However, the new solution is certainly more modern. I like that we are centralizing so many thing into one place.

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify that the new/changed code works.

• The code style follows good practices.
• The commit message(s) follow good practices.

• The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.
• The documentation is still up-to-date in the doc folder.
• The dependencies are still up-to-date in setup.py.

[john-science]

NOTE: I ran the docs GitHub Action before this PR and they worked. Just FYI.

[john-science]

@drewj-usnctech @sombrereau I don't expect this to affect you. But, just in case, I thought you'd want a head's up.

[drewj-usnctech]

👍 😻

[albeanth]

A few comments to consider. Though I'm well out of my wheelhouse with providing an actual review!

[albeanth]

I'll approve, but someone should provide a secondary review as I'm not particularly well versed in this section of ARMI....

[opotowsky]

I love this so much.

Tony ended up getting you to add the docs to the toml, which was a great addition. I really can't think of anything missing here. I eyeball checked that the dependencies and old MANIFEST.in files matched. All looks great to me!