Code behaves differently

[Ingo Dahn]

I see this expected behaviour in one page embedding sagecell:

but this unexpected behaviour in another page:

Any thoughts what might have casued this (the first is an isolated sagecell, the second is the first of a set of linked cells)?

[Andrey Novoseltsev]

No idea. Is the second cell executed as Sage/Python? Can you share a link to the page? We have recently upgraded to Sage-9.1, but I don't see how it could have affected this example.

[kcrisman]

My guess is that it is inadvertently being evaluated in Octave, because when you switch to that in the standalone server that is the format of error I get (and not with other languages):

  File "<string>", line unknown
SyntaxError: source("/home/sc_work/.sage/temp/sc-2B/14472/interface/tmp14672");
parse error near line 3 of file /home/sc_work/.sage/temp/sc-2B/14472/interface/tmp14672

  syntax error

>>> a=
      ^

error: source: error sourcing file '/home/sc_work/.sage/temp/sc-2B/14472/interface/tmp14672'

[Ingo Dahn]

Thank you - Indeed, the SageCell in the second document was generated by some Javascript and I had forgotten that this script generates Octave cells.

Ingo Dahn - Chat @ Spike

--
You received this message because you are subscribed to a topic in the Google Groups "sage-cell" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-cell/wLHvclyBFMY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-cell+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cell/d2308ac1-9e5b-4027-a7ad-47847a3ff0dc%40googlegroups.com.