Attached is a patch to add documentation for Py_ReprEnter and Py_ReprLeave.  Assigning to docs@python for review.

I think this is a bit misleading. These functions are only needed if you are implementing a container. For the general case where you don't display another Python object in your repr() (or you only display objects which are themselves atomic, such as strings and integers), these functions are not necessary.

Good point.  My perspective is skewed by all of the time that I spend working on container types. :-)

How about if I change the first sentence to the following?

    Properly implementing :attr:`tp_repr` for container types requires
    special recursion handling.

> How about if I change the first sentence to the following?
> 
>     Properly implementing :attr:`tp_repr` for container types requires
>     special recursion handling.

This looks good to me.

Possibly related: #9840

Thanks.  New patch attached with a cross-reference to reprlib.recursive_repr.

Patch LGTM, except for “As examples” which I’ve never read before (but I’m not a native speaker).

Yep, looks good, please commit.

Committed in r87339.  Thanks everyone for the feedback!

Err... in r87339 there is a typo in all occurrences of 'Py_ReprEntr': Py_ReprEnter of course!

On Fri, Dec 17, 2010 at 2:17 PM, Amaury Forgeot d'Arc wrote wrote:
> Err... in r87339 there is a typo in all occurrences of
> 'Py_ReprEntr': Py_ReprEnter of course!

Well, that's embarrassing.  Fixed in r87354.