Open GoogleCodeExporter opened 8 years ago
http://code.google.com/p/python-nose/issues/detail?id=402 is potentially
related (but a different tb). I have the same issue on the same line - should
be unicode instead of str?
Original comment by peter.lu...@gmail.com
on 10 May 2011 at 8:00
Without --detailed-errors I get "AssertionError: <unprintable AssertionError
object>" which is still not useful to understand what the failure is. (also on
nose 1.0.0 and python 2.6.3).
Original comment by peter.lu...@gmail.com
on 10 May 2011 at 8:06
Yep, that should not be str(), it should be repr() or something that does safe
decoding/encoding (not unicode though).
Original comment by kumar.mcmillan
on 10 May 2011 at 3:51
Why not unicode? The encoding to a byte stream should happen later, when the
proper encoding can be known (for writing to the terminal or an xml file or
some other log).
Original comment by rasmus...@gmail.com
on 11 May 2011 at 12:09
I just meant you can't call unicode(ev) because that implicitly calls
unicode(ev, encoding=sys.getdefaultencoding()) or, on most systems, unicode(ev,
encoding='ascii'). More info: http://farmdev.com/talks/unicode/
Original comment by kumar.mcmillan
on 11 May 2011 at 4:34
Original issue reported on code.google.com by
wyue...@gmail.com
on 30 Apr 2011 at 6:51