Suppose I have a class that looks like this:

    class A:
        def cleanup(self):
            print("Doing essential cleanup")

and on an instance `a = A()`, I do: `atexit.register(a.cleanup)`.

Then it's not obvious from the documentation that an `atexit.unregister(a.cleanup)` will successfully undo the effect of the reigster call: the second `a.cleanup` is a different object from the first:

    >>> a = A()
    >>> clean1 = a.cleanup
    >>> clean2 = a.cleanup
    >>> clean1 is clean2
    False

Luckily, though the two bound methods are different objects, they're equal:

    >>> clean1 == clean2
    True

and from looking at the source, it's apparent that `atexit.unregister` compares by equality rather than identity, so everything works.

It would be good to add a sentence to the documentation for `atexit.unregister` to clarify that this can be expected to work.

New changeset 12803c59d54ff1a45a5b08cef82652ef199b3b07 by Jack DeVries in branch 'main':
bpo-38062: [doc] clarify that atexit uses equality comparisons internally. (GH-26935)
https://github.com/python/cpython/commit/12803c59d54ff1a45a5b08cef82652ef199b3b07

New changeset 08aa26e4355da6f916da0c97d00774800ee0fc46 by Miss Islington (bot) in branch '3.10':
bpo-38062: [doc] clarify that atexit uses equality comparisons internally. (GH-26935) (GH-26956)
https://github.com/python/cpython/commit/08aa26e4355da6f916da0c97d00774800ee0fc46

New changeset 02859df10591789c72eb185a4f7dd9cc1ea8dcbb by Miss Islington (bot) in branch '3.9':
bpo-38062: [doc] clarify that atexit uses equality comparisons internally. (GH-26935) (GH-26957)
https://github.com/python/cpython/commit/02859df10591789c72eb185a4f7dd9cc1ea8dcbb