Comment 12 for bug 339642

On Tue, Apr 14, 2009 at 11:16 AM, Jörgen Stenarson
<email address hidden> wrote:
> Fernando Perez skrev:

> I agree, but part of the problem here is that part of the problem is to
> have the correct visual output in the shell and this may be difficult to
> check automatically. I have a feeling that this problem is also platform
> dependent making it necessary to run the tests on several platforms as
> well to see that the bug has been fixed.

Well, even if we have a special file we need to re-run by hand, that
would be better than little snippets as we have. At least the file
can be run by the test suite automatically and not crashing is a good
start. Core developers can then re-run it by hand (we can put an "if
__name__" main section at the bottom for this) to check visually.
This is basically what we are doing now with snippets all over the
mailing list, I'm just suggesting that unless all those checks are:

- collected in one file
- auto-executed

we'll never get anywhere reliable on these unicode problems. We can
then have a note to manually do

%run test_unicode

ourselves for the full visual verification.

Cheers,

f