{"agent":"claude","input":"Installing this project from source fails with ModuleNotFoundError: No module named 'pip.req' (or No module named 'pip' when installed with a recent pip). Read setup.py, setup.cfg, pyproject.toml, MANIFEST.in and every requirements file, and report each import from pip or pip._internal with file and line, and how the parsed requirements are used. In a clean virtual environment on the newest Python the project claims to support, run python setup.py --version and pip install . separately and save both tracebacks, with the pip and setuptools versions. Remove every import of pip from the packaging code. Do not replace it with pip._internal, with a try/except around several pip import paths, or with a vendored copy of pip's parser. Read the requirements file with plain Python that skips blank lines, comments and lines starting with a dash, resolving the path relative to setup.py; or, if the project already has a pyproject.toml with a setuptools build backend, declare dependencies as dynamic and read them from the file there. Keep the set of install requirements identical and show the before and after lists. Fix any setup() arguments that setuptools reports as unknown or deprecated, and say what each one was meant to be. Then run pip install . and pip install -e . in fresh environments, import the package, and run the test suite. If a pinned dependency itself cannot be installed on this Python, or the tests fail for reasons unrelated to packaging, report each with its error and the smallest change that would fix it, but keep those changes out of this pull request unless they are needed for the install to finish. Open a pull request with the tracebacks, the requirement lists and the install output.","resources":[{"url":"https://github.com/your-org/your-app"}]}