** Patch added: "py38.patch" https://bugs.launchpad.net/ubuntu/+source/python-oslo.utils/+bug/1841072/+attachment/5306166/+files/py38.patch
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1841072 Title: test_reflection.CallbackEqualityTest.test_different_instance_callbacks fails on Python 3.8 Status in oslo.utils: New Status in python-oslo.utils package in Ubuntu: New Status in python3-defaults package in Ubuntu: New Bug description: When running the unit test on Python 3.8, it fails with the following traceback: oslo_utils.tests.test_reflection.CallbackEqualityTest.test_different_instance_callbacks --------------------------------------------------------------------------------------- Captured traceback: ~~~~~~~~~~~~~~~~~~~ b'Traceback (most recent call last):' b' File "/tmp/oslo.utils/oslo_utils/tests/test_reflection.py", line 156, in test_different_instance_callbacks' b' self.assertTrue(reflection.is_same_callback(b.b, c.b, strict=False))' b' File "/tmp/oslo.utils/.tox/py38/lib/python3.8/site-packages/unittest2/case.py", line 702, in assertTrue' b' raise self.failureException(msg)' b'AssertionError: False is not true' b'' This is apparently caused by a behavior change in Python 3.8 due to [1]. I have confirmed the different behavior by running tests manually on 3.6, 3.7 (both return True) and 3.8. According to [2], only taskflow seems to be using that method now, and it is not changing the default value for the "strict" parameter. [1] - https://bugs.python.org/issue1617161 [2] - http://codesearch.openstack.org/?q=is_same_callback&i=nope&files=&repos= To manage notifications about this bug go to: https://bugs.launchpad.net/oslo.utils/+bug/1841072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
