Issue 5456

[matteius]

Thank you for contributing to Pipenv!

The issue

Fixes #5456

After named package categories was released, the lock file generation had the default behavior of --keep-outdated being passed true.

[oz123]

Code linting is broken, but other than that it looks fine .

[JGSweets]

FYI, I believe this PR has introduced a bug for local packages.
The lines:

if not keep_outdated:
    try:
        del lockfile[category]
    except KeyError:
        pass

forces the category to be resolved latter. This strips the path key for local packages which does not get reintroduced into the lockfile later. This causes a cannot resolve package error during installation despite Pipfile.lock being created.

i.e. the Pipfile.lock for the <LOCAL_PACKAGE> loses the path.

"<LOCAL_PACKAGE>": {
    "hashes": [
        "sha256:<VALUE>"
    ],
    "path": "<PATH>"
}

becomes

"<LOCAL_PACKAGE>": {
    "hashes": [
        "sha256:<VALUE>"
    ]
}

[oz123]

Can you please open a separate issue, so it's easier to track?

[JGSweets]

Can you please open a separate issue, so it's easier to track?

#5542