Summary

Fixes#6119

Problem

When a package (A) installed from a local path depends on another package (B) also installed from a local path, the sub-dependency (B) was not being properly recorded inPipfile.lock. The lockfile entry for B would be empty ({}) instead of containing the file/path information.

Expected Result:

"namespace-library": {"editable":true,"file":"../namespace-library-file"},"namespace-utils": {"editable":true,"file":"../namespace-utils"}

Actual Result (before fix):

"namespace-library": {"editable":true,"file":"../namespace-library-file"},"namespace-utils": {}

Root Cause

Theformat_requirement_for_lockfile() function inpipenv/utils/locking.py was settingentry["file"] = req.link.url for all file:// URLs. However:

1. For localdirectories, we should usepath (with a relative path) instead offile (with a URL)
2. The version and index entries should be removed for file/path dependencies
3. The editable flag should be preserved

Solution

This fix:

• Differentiates between local directories (usepath) and archive files (usefile) for file:// URLs usingreq.link.is_existing_dir()
• Converts file:// URLs to relative paths for local directories usingensure_path_is_relative()
• Removesversion andindex entries for file/path dependencies
• Preserves theeditable flag if set on the requirement

Testing

To test this fix, you can use the reproduction repository from the issue:

git clone https://github.com/AlexandreArpin/pipenv-reprocd pipenv-repro/my-app-file-deppipenv lockcat Pipfile.lock# namespace-utils should now have path info

Pull Request opened byAugment Code with guidance from the PR author