On Sunday, December 1, 2024 at 2:02:14 PM UTC-5 Edward K. Ream wrote: On Sun, Dec 1, 2024 at 12:31 PM Thomas Passin <[email protected]> wrote:
Ah, my mistake. It's not python cells that have the language specified in the header line, it's markdown cells: # %% [markdown] So it isn't the import that has the bug but my memory. Here's another factoid. @language jupytext isn't all that important. Why? Because jupytext converts markdown parts to python comments when importing. I'm not sure of the exact rules, and the jupytext docs don't seem clear on this point. Anyway, my experiments show that jupytext does add comments. But that means that @language python would work! For VR3, there are two aspects here. First, in general a jupytext file will have a mixture of code and markdown nodes. So VR3 can't assume that all nodes will be Python. Second, VR3 cannot assume that a single @language python directive at the top of an at-file will mean that all child nodes will be python, again because there can be a mixture. Not a problem, VR3 is designed to handle a mixture. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/25f88fa4-4955-4842-b67f-fa658638b161n%40googlegroups.com.
