{"agent":"claude","input":"This Python project fails with \"ModuleNotFoundError: No module named 'pkg_resources'\" or depends on pkg_resources and will. Remove the dependency on pkg_resources. Find every use in the code, in setup.py and in build or test scripts, including namespace package declarations, and list them by kind: resource_filename, resource_string, resource_stream, get_distribution, require, iter_entry_points, parse_version, working_set, declare_namespace. In clean virtual environments, show what happens on import with no setuptools, with the newest setuptools, and with the last setuptools release that still ships pkg_resources, and quote the errors and warnings. Run the test suite in the working state as a baseline and record any failures. Replace each use: importlib.resources.files with read_text or read_bytes where the code only reads the file, importlib.resources.as_file where it needs a path on disk, importlib.metadata for versions and entry points, packaging.version for version parsing (declare packaging as a dependency if you add it). If a replaced call defined a module-level name, search for other uses and say that the name is removed. Check the minimum Python version the project declares against what the replacements need; raise python_requires and classifiers to match and say so, unless that drops a version CI still tests, in which case use the importlib_resources or importlib_metadata backport under a version check and declare it. Then uninstall setuptools from the environment and run the import and the test suite again; compare with the baseline and report any test whose result changed. Build a wheel, install it into a clean environment with no setuptools, and confirm from outside the source tree that the package imports and finds its data files. List deprecated setup.py options you noticed, such as setup_requires and tests_require, without changing them. Open a pull request.","resources":[{"url":"https://github.com/your-org/your-app"}]}