This is what I did now. 1. I maintain a registry of the worksheets which I have made online available, tested 100% of them, found ca. 30% broken and corrected those. Remaining problems are the NULL problem for R sheets and failure to plot factorial(x). I still have to go through and eventually correct all my online scripts with embedded SageCells but I have no chance even to find those cells which are embedded in Math questions in a large question library. 2. I issued a warning to the colleagues in my network, asking them to check SageCells before using them for teaching, informed them about the workarounds I know and asked them to report to me any other error that they may find. Will forward those.
We seriously discussed here already some time ago whether we might set up our own SageCell server, but decided that we wouldn't have the capacity to run and support it. Am Fr., 14. Feb. 2020 um 18:21 Uhr schrieb Andrey Novoseltsev < [email protected]>: > I understand very well how unpleasant it is to discover your > code/worksheets broken. Note, however, that each new version of Sage may > and usually does break something. The goal is to have deprecation warnings > before a break occurs for a year or longer and that's I think is the real > problem with Python 3 transition - there were no warnings that print > statement will stop working or map will change the returned value from a > list to an iterator. This is very unfortunate, but since nobody was going > to work on it the only thing under our control was timing the unpleasant > transition. For SageMathCell is was the winter break, CoCalc still has 8.9 > as the default. > > For situations where having no unexpected upgrades and downtime is > crucial, i.e. when you are using something for exams, the only reliable > solution for SageMathCell is to run your own server, which is precisely > what I have done many years ago. Took me quite a while to setup, but was > one of the reasons I could pick up maintenance and development when Jason > Grout left. I've tried to simplify this independent setup option, but have > no idea how many people are taking advantage of it. Running old versions of > Sage used to be on my TODO list, but it never seemed to be a high priority > for anybody else and for me updates are never unexpected anymore ;-) > > -- > 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/Kz4koL1C1nU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-cell/f1b16004-d9d3-44bf-8d67-7354bd89d572%40googlegroups.com > <https://groups.google.com/d/msgid/sage-cell/f1b16004-d9d3-44bf-8d67-7354bd89d572%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "sage-cell" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-cell/CAK-88tAADOEb7sUGVuCD4f4EnWcGFxLeN-Yhr39FmHqxZ3r87A%40mail.gmail.com.
