ValueError: Invalid fragment string

I’m trying to convert existing requirements.txt file with:

pipenv install -r requirements.txt

Describe your environment

1. Fedora 26
2. Python version: 3
3. Pipenv version: version 8.3.2

Expected result

Everything to be installed without errors

Actual result

It raises an error:

ValueError: Invalid fragment string egg=django-user-clipboard==0.6.1

Steps to replicate

You need to have requirements.txt file which will have URL entries pointing to package archive file but ending with #egg=<package-name>==<package.version>

For example:

https://github.com/IndustriaTech/django-user-clipboard/archive/0.6.1.zip#egg=django-user-clipboard==0.6.1

If you try to convert this requirements.txt file to Pipfile with pipenv install -r requirements.txt it will fail.

[jpz]

I’ve encountered this also - here is an example requirements file that pipenv does not like - https://github.com/home-assistant/home-assistant/blob/dev/requirements_all.txt

ValueError: Invalid fragment string suds-passworddigest-py3==0.1.2a 

[techalchemy]

@vstoykov but you’re just making up a number at that point. Internally, pip takes the number and (unless the path you supply is a file:// URI to a wheel) it just says ok, you told me it’s this version… cool whatever, still gonna install the thing you said. Ultimately it will get actual version info from the file.

Anyway we are having two conversations here. One relates to how we should build out our internals for handling requirements parsing, and the other relates to whether your syntax is valid/effective. I’d say that adding a specified to your URL probably isn’t doing anything at best, so the real question is just whether we adopt pip’s behavior of parsing links.