On sage-cell, Py3 was brought up. I mentioned how permalinks there may cause trouble at the eventual Py3 changeover for Sage, since at the very least print statements will be gone. William brings up an interesting possibility, and I wonder how/whether this would be useful for Sage proper. A lot of broken code overnight won't make anyone happy; I don't know how easy to use the various converters Py2->Py3 are to use for non-sage-devel people who might just have some random scripts or Sage/Jupyter notebook worksheets. Anyway, hopefully people might have useful commentary on a broader email list, thanks! - kcrisman
> Along these lines, it occurs to me that if/when Sage switches to Py3, > > "when", I hope! E.g., I personally always use the python3 version of > Sage, and it works well for me. > > > there will be a lot of broken permalinks - especially if people used > "print blah" instead of "print(blah)". Is there any way to avoid this? > > It could be avoided using the preparser, with a deprecation warning > printed. There's probably a trac ticket about this somewhere. > > William > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
