Summary

When pip fails with "Getting requirements to build wheel exited with 1", the error message is confusing because it appears to be a dependency resolution issue. This change adds helpful hints to guide users toward the actual cause.

Problem

When running pipenv install . with a local package that has issues in its pyproject.toml or referenced files (like README.md with encoding problems), users see:

Resolving dependencies...
Locking Failed!
ERROR:pip.subprocessor:Getting requirements to build wheel exited with 1

This error appears to be about dependency resolution, but the actual problem is often:

• Invalid pyproject.toml syntax or configuration
• Encoding issues in files referenced by pyproject.toml (e.g., README.md with special characters like em-dashes — or ellipses …)
• Missing or incompatible build dependencies

Solution

Add helpful hints when the "Getting requirements to build wheel" error is detected:

Hint: The error 'Getting requirements to build wheel' often indicates:
  • Invalid pyproject.toml syntax or configuration
  • Encoding issues in files referenced by pyproject.toml (e.g., README.md with special characters)
  • Missing or incompatible build dependencies
Try running $ pip install . -v in your project directory for more detailed error output.

Changes

1. pipenv/exceptions.py: Enhanced ResolutionFailure exception to detect the error pattern and add hints
2. pipenv/utils/resolver.py: Added hint detection in the resolver error output path

Fixes #6058

Pull Request opened by Augment Code with guidance from the PR author