[IPython-dev] Should we fix this bug before 0.10?

Fernando Perez fperez.net at gmail.com
Tue Mar 17 16:24:17 EDT 2009

2009/3/17 Laurent Dufrechou <laurent.dufrechou at gmail.com>:
> Hi all,
> Reviewing bugs, i’ve seen this one that has been shipped with a potential
> patch.
> Do one specialist see any bad things in the patch?
> https://bugs.launchpad.net/bugs/339642

For those not subscribed to the bug, here's what I said there:

That's indeed a bug, but the patch is removing a line that was put in
there explicitly for some reason.  So what I'd like to have, before
committing this, is a set of tests in a file named test_unicode.py,
that encapsulates all of the recent unicode work.

Unfortunately a lot of these unicode fixes have been made in a
completely ad-hoc manner, as people report problems, but we don't have
a centralized list of cases to check against.  His may be a reasonable
fix, for all I know, but I'm afraid that if we apply it we'll get back
10 old bugs again.  I don't know, maybe not, but there's simply no way
to be sure.

I'm one of the most ignorant of our bunch in unicode issues,
blissfully living in the stupidity of the ascii world.  It would be
great if one of us who knows more about this stuff could at least
write a set of simple unicode tests that catch many of the recently
reported encoding problems.  Jorgen, Ville, any chance you guys could
take this up at some point?  You know about it a lot more than I do...

More information about the IPython-dev mailing list