Matt McKay

Could we have an argument `start` and `end` -- rather than two different directives: ```` ```{solution} start ``` ```{solution} end ``` ```` I guess we should also think about other...

hey @jstac this is a nice format option -- I like it. I think we will still get issues with executing the nested code-blocks (cc: @chrisjsewell) as it breaks the...

I wonder if we could have `tabbed` code blocks in jupyter notebooks which had an execution rule of `left` to `right`. This would then directly translate to the notebooks format...

thanks @choldgraf -- that is a thought I had as well and might be the best we can do (unless `jupyter-cache` implements something like pre-execution filters/transforms). My concern though is...

@choldgraf just to clarify one point on your suggestion. Would all the `jupyter-sphinx` directives be executed by the same `independent` kernel (at the file level)? Perhaps we can introduce an...

@choldgraf @chrisjsewell I am going to dive into this issue. I think using this as a prototype to figure out the best way to setup `nested code` will be useful...

@AakashGfude thanks for the brainstorming today. It looks like we could support `styling` only through the use of `visit_solution_start` and `visit_solution_end` nodes injecting updates to `html` and `latex` but it...

**Update:** 27th October 2021. I see two syntax options when building out tests for this. Playing around the two syntax choices I think I am actually in favour of `option...

> Just checking: I hope with this change in place, the original single directive will still stay, is this correct? thanks @akhmerov -- for sure -- not thinking we would...

I have now setup an working prototype of this idea for `sphinx-exercise` https://github.com/executablebooks/sphinx-exercise/pull/45 I quite like the gated directive approach as it tends to simplify the syntax (when compared with...