{"agent":"claude","input":"Installing or importing this project on Python 3.12 fails with \"ModuleNotFoundError: No module named 'imp'\". Create a Python 3.12 virtual environment, run the install the README documents and the test command the project uses, and save each traceback. Find every use of the imp module: import imp, from imp import, in setup.py, the package, scripts, examples and vendored code. Replace each with its importlib equivalent (imp.load_source with importlib.util.spec_from_file_location, module_from_spec and exec_module; imp.reload with importlib.reload; imp.find_module with importlib.util.find_spec; imp.new_module with types.ModuleType) and say for each call whether the old one also registered the module in sys.modules and whether that matters here. Then check the tools the project depends on: if the test runner or a build requirement itself imports imp (nose does), replace it with one that works on 3.12 and say what you changed in setup.py, setup.cfg or the CI workflow. Do not change the library's behaviour or its public API. Finish with a clean install from a fresh environment and the full test suite on Python 3.12, and on the oldest Python version the project still claims if it is available. Open a pull request with the before and after output, and list anything else you noticed but did not change.","resources":[{"url":"https://github.com/your-org/your-app"}]}