> The spec identifies how a module should be loaded (or how it was loaded and should be reloaded).  We should be careful to preserve that identify and not invite uses to modify the spec after (or while) the module is loaded.

But they may want to modify it to influence reloading. There's a discussion somewhere where I talked about this with Nick and he agreed with me that trying to keep specs like receipts and all of these other attributes as mutable values had not really panned out after all of these years.

> +1 on a proxy (with read-only attrs) for everything but __name__, __file__, and __path__ (which can all be different than the spec).

I'm -1 on a proxy as that doesn't simplify the situation. Having (nearly) duplicate attributes is confusing and I have yet to see it benefit anyone.