Skip to content

FIX: workaround py2 unicode issues #7509

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 24, 2016

Conversation

tacaswell
Copy link
Member

9a8ed26 backported #7436 which fixed a
warning about non explicitly encoded non-ascii characters.

This 'just works' on python3, but we need to explicitly make the string
with the unicode (¶ for the links) as unicode for py2.

We can not use from __future__ import unicode_literals due to issues
with shpinx expecting bytes (str) not unicode.

This took way too long to track down, really looking forward to dropping python2.

@tacaswell tacaswell added this to the 2.0 (style change major release) milestone Nov 24, 2016
9a8ed26 backported matplotlib#7436 which fixed a
warning about non explicitly encoded non-ascii characters.

This 'just works' on python3, but we need to explicitly make the string
with the unicode (¶ for the links) as unicode for py2.

We can not use `from __future__ import unicode_literals` due to issues
with shpinx expecting bytes (str) not unicode.
@tacaswell
Copy link
Member Author

Failure is one of the transient tex / string IO related ones.

Self-merging to un-break 2.x

@tacaswell tacaswell merged commit 31ef622 into matplotlib:v2.x Nov 24, 2016
@tacaswell tacaswell deleted the fix_lpy_encoding branch November 24, 2016 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant