You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In v5.10.3, I addressed what I thought was all of the encoding warnings emitted by this test suite.
However, due to the way the warnings framework attempts to localize the usage, there was one warning (with two invocations) that I'd missed:
importlib_resources/tests/test_open.py::OpenDiskTests::test_open_text_FileNotFoundError
importlib_resources/tests/test_open.py::OpenDiskNamespaceTests::test_open_text_FileNotFoundError
/Library/Frameworks/Python.framework/Versions/3.12/lib/python3.12/unittest/case.py:237: EncodingWarning: 'encoding' argument not specified
callable_obj(*args, **kwargs)
That warning looks like it's coming from unittest.case:237, but when I looked at that code, I can see that it's just the wrapper created by use of assertRaises. Fortunately, the test names give some hint as to where the missed encoding parameter is (test_open_text_FileNotfoundError).
The text was updated successfully, but these errors were encountered:
In v5.10.3, I addressed what I thought was all of the encoding warnings emitted by this test suite.
However, due to the way the warnings framework attempts to localize the usage, there was one warning (with two invocations) that I'd missed:
That warning looks like it's coming from
unittest.case:237
, but when I looked at that code, I can see that it's just the wrapper created by use ofassertRaises
. Fortunately, the test names give some hint as to where the missedencoding
parameter is (test_open_text_FileNotfoundError
).The text was updated successfully, but these errors were encountered: