Documentation

In thecopy module documentation, the functioncopy.replace() has a.. versionadded:: annotation marking it as new in Python 3.13.

But the relatedobject.__replace__ dunder method — which is documentedmuuuuuch farther down the page, near the very end — has no such annotation.

IMHO the two are too far apart and separated by too much completely unrelated documentation, for the annotation fromcopy.replace() to be implicitly applicable toobject.__replace__ as well.

Module-level organization of content

To be perfectly honest, I'm not sure it makes sense forcopy.replace() to eventually be documentedso far from where it's initially introduced. Especially considering how brief that documentation actually is, the separation may do more harm than good.

No other module in the "Data Types" section starts with an "Interface summary:" like the one in thecopy documentation. The most similar doc is theenum module's, which has a §Module Contents at the start. But there inline version annotations are skipped to keep the TOC concise, instead they're collected down below the list itself. Relevant annotations are also included in the detailed documentation sections that follow.

The organization of thecopy docs is sort of... well, there's muchless organization there, than in the documentation for other modules. (Probably attributable to both the age and extremely short length of thecopy documentation.)