It is in no way specific to permalinks - all webpages with cells in Python2 will be broken. And things do get broken gradually with new versions of Sage as well. So it would be nice if Sage had good explanations and warnings for what is happening, if Python3 itself does not have it, but as far as SageMathCell is concerned I see my task only in transitioning smoothly to Python3 whenever Sage will do it.
Alternatively, we can let sagecell.sagemath.org run the last Python2 version for a year or so, while switching activity and all documentation for newcomers to sagecell3.sagemath.org. After a year sagecell. can redirect to sagecell3. so old stuff that does not depend on Python2 still works. But I am not at all convinced that there is much point in such efforts. Unicode-wise permalinks handling was probably the trickiest, just because it is a bit convoluted how things are sent around, and it seems that I've succeeded in switching it to Python3. The rest should not be particularly difficult, I think, but switching to new Tornado will require some work. We are currently using version 4, 5 deprecated a bunch of stuff we rely on, and the current 6 has removed it, so while permalinks code worked with Python3, I had to stick to Tornado 5 for now. -- 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/3cd3dcd4-d720-4264-9b24-36f1be563552%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
