Fix syntax error in Python 3.3. #152
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
“Unicode Raw” strings are no longer supported in Python 3.3, and cause a syntax error. See http://bugs.python.org/issue15096. Without this fix, Pystache gives a syntax error when used in a Python 3.3 environment.
|
Thanks. Looks harmless. 😄 |
cjerdonek
added a commit
to cjerdonek/pystache
that referenced
this pull request
Sep 15, 2013
This commit is more a matter of style since the Python 3 code generated by 2to3 is valid under Python 3.3. This merges remote-tracking branch 'sentience/development' into development and closes issue defunkt#152.
|
Merged into development. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
“Unicode Raw” strings are no longer supported in Python 3.3, and cause a syntax error. See http://bugs.python.org/issue15096.
I understand that the source distribution of Pystache is not intended to by Python 3 compatible out of the box, but this syntax error seems unnecessary. With this change, the code is functionally equivalent, and the syntax is compatible with all Python versions.