What you request is non-standard behavior, hence no module should ever automatically "bubble up" two caller levels to the "grandparent" *

It's the module in the middle which could use tricks to "transport" (hopefully well documented) behavior from the used "child" module to the to the "parent" caller.

For instance taking your examples

• constants are implemented as functions with an empty prototype, hence can be exported like all normal functions.
• warnings and strict can be propagated like explained here ²

*) though it's possible, by exporting import , but doing so means mangling with the dark side, young padawan.

²) this should (?) work with all modules depending on Exporter