If we allow an UTF-8 banner then we may also allow UTF-8 string representations for Sage objects (why not?). But I think we do not want to force the user to have UTF-8 output because it is always harder to parse an UTF-8 string than an ASCII string (this argument is also valid for the Sage banner). It might be useful to have two console modes, ASCII and unicode, and I have no objection of having unicode as default. Finally, I strongly believe that we do not want to change the sage-banner at each release.
Vincent -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.