pipenv misses some dependencies during installs

Hi guys. I believe there is a bug somewhere in pipenv which is causing the behaviour highlighted here: fabric/fabric#1675.

In short, I had to manually specify a dependency of another dependency in my Pipenv file because someone (pipenv? virtualenv? something else?) wasn’t able to see it and therefore import it while issuing CLI commands within the scope of a pipenv shell session.

Anything you need me to do to help troubleshoot this please let me know. Thank you in advance.

[vphilippon]

I’d put my money on another case of “wrong wheel used for dependencies resolving”, which is fixed in 8.2.7.

What likely happened is that a Py3.4+ wheel of cryptography was selected for listing the dependencies (even if the environment was Py2, that’s the bug), which didn’t list enum34 as a dependency (as its only needed for Py<3.4). Then, when installing, pipenv strictly installed what was in Pipfile.lock (using the equivalent of pip install --no-deps), assuming the Pipfile.lock included all the right dependencies, which wasn’t the case due to the bug. This is how enum34 ended up missing in the environment, causing the ImportError.

Could you update to pipenv 8.2.7, lock with a cleared cache (pipenv lock --clear), and confirm if its fixed?

[erinxocon]

Closing this in favor of issue #909 😃