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.
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.