Remove from __future__ import with_statement #1799
Closed
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
This \_\_future\_\_ import is no longer required in Python >= 2.6. https://docs.python.org/2/library/__future__.html
rvagg
pushed a commit
that referenced
this pull request
Jun 26, 2019
This \_\_future\_\_ import is no longer required in Python >= 2.6. https://docs.python.org/2/library/__future__.html PR-URL: #1799 Reviewed-By: Rod Vagg <rod@vagg.org>
|
landed in afaaa29 also FYI, commit message became: metadata in commit summary: |
|
maybe I should have left this a bit longer, only 21 hours, it's pretty trivial but I guess we should have a proper delay to allow more eyes in future |
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.
This __future__ import is no longer required in Python >= 2.6.
Checklist
npm install && npm testpassesDescription of change