The catch, of course, is that we can't know if there's anyone that
relies on it for other reasons. I'd be happy to rip it out otherwise.
Removing that code causes many tests to break, and all the breakage
appears incidental rather than fundamental.
Would people be happy with the current behavior as a default, and a
way to set an attribute of the TALInterpreter instance to use the
cleaner behavior? An attribute on the page template object could then
be used to record the application's requirements.
The catch, of course, is that we can't know if there's anyone that
relies on it for other reasons. I'd be happy to rip it out otherwise.
Removing that code causes many tests to break, and all the breakage
appears incidental rather than fundamental.
Would people be happy with the current behavior as a default, and a
way to set an attribute of the TALInterpreter instance to use the
cleaner behavior? An attribute on the page template object could then
be used to record the application's requirements.