Py2/3 Compatible Imports for ConfigParser #126
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
Py3 renamed 'ConfigParser' to 'configparser'. This fails on Py3 setup, because it tries to import 'ConfigParser' and not 'configparser'. Otherwise it should work identically.
This was referenced Jun 9, 2018
Closed
hugovk
approved these changes
Jun 9, 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.
Py3 renamed 'ConfigParser' to 'configparser'. This fails on Py3 setup, because it tries to import 'ConfigParser' and not 'configparser'. Otherwise it should work identically.
Note that I got here from the PyPI page. Unless you upload a Python2 only wheel and not a Python3 wheel, it's going to be able to install from the source you uploaded, which is not yet Python3 compatible. However, this change should fix the Py3 problem.