Comments

I'm sure Alex or Jason or one of the other Sage cell developers will address this, but my gut is that you are really using undocumented behavior with the `**kwargs` bit there - I'm sure that they are still working out bugs with nested interacts. I did see a couple of commits on github that seemed perhaps connected.

2 answers

I thinkthis is an issue related to a change we made regarding how defining controls in the interact decorator works. I've opened an issue about that behavior here: https://github.com/sagemath/sagecell/...

In the meantime, since t is being defined in the function globals, you can access it from there (or just by the variable t). One thing you might want to do for now to ensure consistent behavior with local variables and kwargs for the function is to either define all interacted variables in the interact decorator or define all interacted variables in the function itself until the issue is resolved.

Alex is correct; there was a change in the new experimental options dealing with defining controls in the interactpart. We (on the sagecell dev team) talked about this a few weeks ago, and we realized that this change has unintended consequences, so we'll be changing it back. For now, you can use aleph1.sagemath.org (which uses our code from last year).