Py3.7 import failure running unit tests
Bug #1785641 reported by
Corey Bryant
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glance_store |
Fix Released
|
Medium
|
Cyril Roelandt | ||
Queens |
New
|
Undecided
|
Unassigned | ||
Rocky |
New
|
Undecided
|
Unassigned | ||
Stein |
Fix Released
|
Medium
|
Cyril Roelandt |
Bug Description
Unit tested execution with py3.7 fails with import error: https:/
Changed in glance-store: | |
status: | New → Triaged |
importance: | Undecided → Medium |
To post a comment you must log in.
So, looking at the Changelog for Python3.7:
"The configparser. ConfigParser constructor now uses read_dict() to process the default values, making its behavior consistent with the rest of the parser. Non-string keys and values in the defaults dictionary are now being implicitly converted to strings. (Contributed by James Tocknell in bpo-23835.)"
So, this *should* work.
Now, looking at msg320899 of https:/ /bugs.python. org/issue23835 :
$ python3.6 -c 'import configparser; configparser. ConfigParser( defaults= {"a": None})' ConfigParser( defaults= {"a": None})'
$ python3.7 -c 'import configparser; configparser.
...
TypeError: option values must be strings
This seems to be a regression in Python, reported a few days ago.