Run futurize --stage1 to make safe changes for python 3 compatibility.
#6063
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
Stage 1 of the futurize tool only makes safe changes, and it keeps the code base at Python 2. See http://python-future.org/futurize.html#forwards-conversion-stage1. Stage 2 will later convert this to actual Python 3 code. This command was ran on - src/python - test/python - contrib - examples - pants-plugins - build-support/bin/check-header-helper.py (not ran on testprojects)
|
cc @iantabolt and @mateor |
stuhood
approved these changes
Jul 2, 2018
| @@ -8,6 +8,8 @@ | |||
| # | |||
| # usage: check_header_helper.py dir1 [ dir2 [ ... ] ] | |||
|
|
|||
There was a problem hiding this comment.
Oh the irony of the "header check" script not using its own headers!
wisechengyi
approved these changes
Jul 2, 2018
kwlzn
approved these changes
Jul 3, 2018
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.
Problem
First stage of Python 3 port
Solution
Stage 1 of the futurize tool only makes safe changes, and it keeps the code base at Python 2. See http://python-future.org/futurize.html#forwards-conversion-stage1. Stage 2 will later convert this to actual Python 3 code.
This command was ran on
(not ran on testprojects)