One thing that comes to mind beyond/independent of preparser tricks (which 
can be hard to make robust):
sagecell already has a lot of "languages". Would it be possible to have 
sage-py2 and sage-py3 as languages? We could then start out having "sage" 
as an alias to sage-py2. At some point we can change over the default. At 
that point, people can "fix" problems by setting the language to sage-py2. 
Once we've had that for a while, we can remove sage-py2. At that point we 
should probably keep sage and sage-py3 as aliases because changing them 
would cause further breakage.

-- 
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.

Reply via email to