#14375: Indicate escape codes in doctest output
-------------------------------------+--------------------------------------
Reporter: jdemeyer | Owner: roed
Type: enhancement | Status: new
Priority: minor | Milestone: sage-5.9
Component: doctest framework | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Volker Braun | Merged in:
Dependencies: | Stopgaps:
-------------------------------------+--------------------------------------
Comment (by vbraun):
Mix & matching byte string and unicode mostly works if you are willing to
ignore the !UnicodeWarning ;-)
I agree that the doctest code can see arbitrary binary data (including
UTF-8) right now as anything might be printed by the code being tested.
Its possible (but unlikely) that some of the non-ascii garbage will be
translated into `<ESC-?>` by this patch. So what? The end goal should be
unicode + 100% coverage of ansi control sequences, and this patch is
closer to that goal than leaving out some random control sequences because
they aren't used much.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14375#comment:11>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
