[Matplotlib-devel] Python 2.7 build failing due to Unicode characters...

[Benjamin Root]

as a general rule, we have a set of __future__'s that we put at the top of
every python source:

```
from __future__ import (absolute_import, division, print_function,
                        unicode_literals)
```

Now, whether or not this would fix your problem or not, I haven't a clue.

On Fri, Sep 8, 2017 at 1:49 PM, Jody Klymak <jklymak at uvic.ca> wrote:

> Hi all,
>
> Very sorry to be ignorant, but my python 2.7 build of the constrained_layout
> manager <https://github.com/matplotlib/matplotlib/pull/9082> is failing
> because the underlying functions don’t accept unicode strings. i.e.
> boo(‘test’) fails with a warning: TypeError: Expected object of typefloat,
> int, or long. Got object of type unicode instead. OK, the warning is a
> little confused - strings get converted to floats inside this fcn, but you
> get the idea…
>
> Am I supposed to put # -*- coding: utf-8 -*- at the top of every source
> that might create a string that calls these functions? Or should I convert
> the string somehow in my wrappers before passing down? Or does from
> __future__ import unicode_literals do this?
>
> Thanks for bearing with me, Jody
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20170908/ea933799/attachment.html>