In some scenarios it is desirable to have a specific scope attached to every call of a given method. Instead of pushing a scope in every caller of that method it could make more sense to decorate the method with a pushed scope and then modify that temporary scope at the top of the method (or even assign the scope attributes in the decorator call).
As found in #523, bootstrapping the current push_scope API with decorator functionality is not simple. It seems that some amount of API-breakage is necessary in order allow push_scope to work as a decorator. Due to this, it's a good idea to discuss the intentions of and use cases for push_scope.
In some scenarios it is desirable to have a specific scope attached to every call of a given method. Instead of pushing a scope in every caller of that method it could make more sense to decorate the method with a pushed scope and then modify that temporary scope at the top of the method (or even assign the scope attributes in the decorator call).
As found in #523, bootstrapping the current push_scope API with decorator functionality is not simple. It seems that some amount of API-breakage is necessary in order allow push_scope to work as a decorator. Due to this, it's a good idea to discuss the intentions of and use cases for push_scope.