Use backports configparser package for python < 3.6 #248
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
in order to simplify imports, we should use the backport package `configparser`
3 similar comments
alurban
approved these changes
Apr 12, 2019
There was a problem hiding this comment.
LGTM @duncanmmacleod, and this takes away more lines than it adds, so you get double points!
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 PR updates the dependencies to use the backports
configparserpackage for python < 3.6. This allows us to simplify the imports of that module to use up-to-date ('python3') names, removing the need forsixat least in this case, and removing ambiguity about which package (stdlibconfigparser, backportsconfigparser, or stdlibConfigParser) will be used at runtime.