nbval and the %load mechanic about nbval HOT 4 OPEN

Hi Vincent!

That's an interesting one. %load and similar commands like %recall break the usual execution model by modifying the input. I guess they might also not do the expected thing if you 'run all' in the notebook.

It's easy enough to add a special case for IPython's %load magic and work around it - looking at asekuro, that's what you've done. Maybe %load is common enough that it makes sense to do that in nbval as well. But I'm not super keen on that.

Perhaps a better way to do it would be to check the execute_reply payloads for a set_next_input payload, and if one is found, run the code from that without checking its output (since there's presumably no equivalent cell in the reference notebook).

from nbval.

from nbval.

That deprecation is somewhat theoretical. They're kind of ugly and we want to redesign how that information is sent at some point, but they work, and replacing them is not high on anyone's priority list. So I think it would be reasonable to check them in nbval if you want.

from nbval.

Yeah we've internally decided that we want to stop using asekuro. Instead we'd love to add this feature to this project. I do want to double check: is this considered deprecated or not?

from nbval.