There is a cross-reference to namedtuple in SimpleNamespace's docs, but not vice-versa, despite these types being fairly similar.

The NT docs are already very long and I don't think an additional crossref is beneficial (NTs are closer to tuples and SNs are closer to dicts).   Also, the uptake for SNs are nearly zero.

> Also, the uptake for SNs are nearly zero.

That suggests to me that pointing users to it could help. It's currently hidden in the types module and if I didn't know it existed, I could end up looking in collections, and failing to find it there, write my own.

I use SimpleNamespace in just about every project I'm currently working on.  I would *not* say that their uptake is "nearly zero" :)

And yes, I wouldn't be aware of it if I hadn't been following python-dev when it was introduced, and had (before it was introduced) written my own variations numerous times.

People do have problems that SimpleNamespace can solve:

- Why Python does not support record type i.e. mutable namedtuple [1]
- Does Python have anonymous classes? [2]
- How to create inline objects with properties in Python? [3]
- python create object and add attributes to it [4]

[1] http://stackoverflow.com/questions/5227839/why-python-does-not-support-record-type-i-e-mutable-namedtuple
[2] http://stackoverflow.com/questions/1123000/does-python-have-anonymous-classes
[3] http://stackoverflow.com/questions/1528932/how-to-create-inline-objects-with-properties-in-python
[4] http://stackoverflow.com/questions/2827623/python-create-object-and-add-attributes-to-it

New changeset 678d93c273de by Raymond Hettinger in branch 'default':
Issue #24842:  Cross-reference types.SimpleNamespace from the namedtuple docs
https://hg.python.org/cpython/rev/678d93c273de