Chris Sewell

Sorry, couldn't resist 😅, but over at https://github.com/pallets/jinja and https://github.com/pallets/markupsafe this kind of highlights my "fear"; within a few hours of a marksafe release that breaks a version of jinja...

> Even a few hundred could be handled in not too long a time, especially if it's a generic response like "Please upgrade". As long as one of you guys...

thanks @rowanc1 > with an addition of being able to label the code cell in any language with a simple `target` tag > ```python > # (myPlot)= > plt.plot([1,2,3]) >...

> not having the notebooks available when you want to re-render markup (I want to pull someone else’s variables into my new document); The other consideration here, that I didn't...

> Yes, keeping the target in the source code can simplify things from a UI perspective. This could certainly be viable 👍 > Cross-reference resolution is one of the last...

> putting this in similarly to a tag might be better ughh, I'm not a great fan of "abusing" tags to do everything: they have their place and are helpful...

> Should we consider transparency of the process of exposing variables over being kernel agnostic? Thanks @stevejpurves, but can you explain a little more what you mean by transparency here?...

> two related but different workflows here yep thats also what I felt @stevejpurves was referring to, and relates to my "Using dynamic kernel injection" section in the initial comment....

> yet but also executing code from myst content ... could produce a different result, as it injects new computation into that linear flow Not in https://github.com/executablebooks/MyST-NB/pull/382 no, because it...

> curvenote: cons: No guaranteed that code output is updated with their dependencies This is definitely a key consideration for me: the trade-off, between execution and caching I believe the...