Make gl3w_gen.py compatible with both Python 2 and Python 3 #19
Conversation
This file contains 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
Change to functional print() statements, and use a __future__ import to allow Python2.6+ to use them.
… of the older % style
…on2's urllib2 on failure
|
Thanks for the patch. |
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.
These changes make the gl3w_gen.py script run in both Python 2 (tested with 2.7.8) and Python 3 (tested with 3.4.2). Everything should also work in Python 2.6, according to the documentation.
Note: Some sources suggest using
from __future__ import unicode_literalsfor string compatibility. I'm not sure which is better, but it might be worth investigating.