@ChrisBarker-NOAA have you looked into the possibility of embedding a diagram? (#1276 (comment))
I think, it's important to demonstrate unidirectional flow of the version sourcing.

OK -- I think this is in good shape, and has addressed the concerns of everyone.

Open Question: whether to include a diagram -- see: #1580 (comment)

Other than that -- good to go.

Editors -- anything else?

Open Question: whether to include a diagram -- see: #1580 (comment)

Thanks for acknowledging that you saw my request. What's your opinion? I don't think I saw you sharing it anywhere — have I missed it?

What would the diagram contain? I'm guessing some flow that depicts pyproject.toml -> build backend -> project/__init__.py:__version__ -> version in package metadata? Not sure how I'd translate those into picture form short of just writing those words with rectangles round them.

Open Question: whether to include a diagram --
What's your opinion?

I don't think it's necessary -- it's just not that complicated.

But I'm happy for the doc editor(s) to decide.

-CHB

@bwoodsend I made a diagram in this comment a while back: #1276 (comment). I imagined it'd be reused, maybe with some modifications. It's made with Mermaid.

@ChrisBarker-NOAA okay, I hear you. In the interest of unblocking the effort, I withdraw that request for now.

Thanks for slogging through all our comments, I think the end result is really nice and clear now!

Glad it got through to the end this time!

Thanks all -- it was a slog, but it's a much better document as a result of all the input.

Here's to never seeing FileNotFoundError: .../site-packages/xyz/version.txt ever again!