Skip to content

Conversation

corona10
Copy link
Member

@corona10 corona10 commented Jun 17, 2018

@jrideout
Copy link

jrideout commented Nov 7, 2018

Any reason this was closed? This is still an issue on the 3.6 branch.

@corona10
Copy link
Member Author

@jrideout
I don't think that my PR was the right approach.
I think that we have to read the standard about how to handle
non-ascii characters which is over 78.

If you know the standard we can discuss how to solve this issue

Thanks!

@vstinner
Copy link
Member

FYI PR #12020 has been merged into master: a different fix for the same issue.

@corona10 corona10 deleted the bpo-33529 branch May 14, 2019 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants