Re: [matplotlib-devel] unicodeescape traceback on build of latest master in IPython

[Michael D. <md...@st...>]

I'll bring this to @minrk's attention in the original issue (#2534)

Mike

On 12/06/2013 02:20 PM, Thomas Kluyver wrote:
> On 6 December 2013 10:37, Joel B. Mohler <jm...@ga... 
> <mailto:jm...@ga...>> wrote:
>
>     It seems to me that this changeset needs to be rolled back, but I
>     don't clearly see the problem that it was intended to fix.
>
>
> I assume that someone wanted to work with the arguments as text (i.e. 
> unicode) strings. A robust way to do this would be something like the 
> str_to_unicode function we have in IPython - it's a no-op on Python 3, 
> and does a robust decode (using errors='replace') on Python 2.
>
> Thomas
>
>
> ------------------------------------------------------------------------------
> Sponsored by Intel(R) XDK
> Develop, test and display web and hybrid apps with a single code base.
> Download it for free now!
> http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel


-- 
                    _
|\/|o _|_  _. _ | | \.__  __|__|_|_  _  _ ._ _
|  ||(_| |(_|(/_| |_/|(_)(/_|_ |_|_)(_)(_)| | |

http://www.droettboom.com