#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:
-------------------------------------+--------------------------------------
Changes (by {'newvalue': u'Volker Braun', 'oldvalue': ''}):
* author: => Volker Braun
Comment:
Replying to [comment:9 vbraun]:
> Can we actually finish #14153 before switching to python 3? Without
checking, I would guess that there are tons of things that will go wrong
when feeding the python 2.7 doctest module with unicode strings.
We're actually using quite little of the Python doctest module. Besides,
with Python's duck-typing, there is not that much difference between
strings and unicode strings.
> There is no compromise needed since the byte string version of this
ticket should never meet the unicode version of the doctest framework.
What I'm trying to say is that the current string version of the
doctesting framework might see byte strings encoded as UTF-8, even when
not using the `unicode` type. Remember that Sage uses UTF-8 encoded source
files, so any strings defined in doctests will be encoded as UTF-8.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14375#comment:10>
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.
