Skip to content

Wildcard version dependency pins wildcard instead of specific version #4278

@GPHemsley

Description

@GPHemsley

Spun off from #4263. This is a regression from 2018.11.26.

Issue description

Dependencies with wildcards get locked with a wildcard version instead of a specific version.

Steps to replicate

  • Run pipenv install 'example-test-package==1.0.*'

Expected result

Pipfile.lock contains:

        "example-test-package": {
            "hashes": [
                "sha256:0b164142f6adbef9d719de6885db0ead7b8af66bed3b0a2145dad75420e18a25",
                "sha256:54fec966dab3f3d4f2f5aa6d237bcd30af09a3dc7a0602da0306f39d8c625ec7"
            ],
            "index": "pypi",
            "version": "==1.0.0"
        }

Actual result

Pipfile.lock contains:

        "example-test-package": {
            "hashes": [
                "sha256:0b164142f6adbef9d719de6885db0ead7b8af66bed3b0a2145dad75420e18a25",
                "sha256:54fec966dab3f3d4f2f5aa6d237bcd30af09a3dc7a0602da0306f39d8c625ec7"
            ],
            "index": "pypi",
            "version": "==1.0.*"
        }

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions