FWIW, the "verbose" option is mentioned as outdated because the "_source" attribute was added.

Also, there are real use cases, people are using the _source as writing it to a .py file so that the dynamic namedtuple generation step can be skipped on subsequent imports.  This is useful when people want to avoid the use of eval or want to run cython on the code.

The attribute can be "dropped". It is part of the API.

Sorry, the memory use bugs you.  It is bigger than typical docstrings but is not a significant memory consumer in most applications.

I like the idea of dynamically generating the source upon lookup, but want to think about whether there are any unintended consequences to that space saving hack.