Currently, the importlib.resources tests (and fixtures) are intermingled with other importlib tests, making it more difficult to determine which functionality belongs to which aspect of importlib. Instead, these tests should be in their own package to reflect their purpose and to ease the mapping to the importlib_resources backport.
The text was updated successfully, but these errors were encountered:
…urces. (#95219)
* gh-95218: Move tests for importlib.resources into test_importlib.resources.
* Also update makefile
* Include test_importlib/resources in code ownership rule.
jaraco commentedJul 24, 2022
Currently, the importlib.resources tests (and fixtures) are intermingled with other importlib tests, making it more difficult to determine which functionality belongs to which aspect of importlib. Instead, these tests should be in their own package to reflect their purpose and to ease the mapping to the importlib_resources backport.
The text was updated successfully, but these errors were encountered: