-
Notifications
You must be signed in to change notification settings - Fork 885
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
chokes on rb"literal"
#56
Comments
The problem is that the original code isn't correct. "rb" isn't accepted by "br" is. One of the limitations of lib2to3 (and therefore YAPF) is that it requires the code to be well-formed. Here's what I saw:
|
Useful for e.g. not having to escape backslashes in bytestrings. |
Ah! My mistake. I was using 2.7. |
Marking this as a bug, but I'm not sure what we can do here. Might be the same issue as |
Yeah, I'll have to see what we do about places where lib2to3 fails. Maybe deeper monkey-patching will help |
This is an upstream lib2to3 bug. Reported http://bugs.python.org/issue23894 Monkey patching this in lib2to3 is pretty complex -- I don't see this as very high priority at this time. |
Adding a lib2to3 bug label. |
Python 3 seems to have fixed this. |
yapf currently chokes on raw bytestring literals:
This is using revision 7a01d00.
The text was updated successfully, but these errors were encountered: