Pipenv: dependencies could not be resolved

Created on 10 Oct 2018  路  3Comments  路  Source: pypa/pipenv

just now, i upload an module to PyPi. Then i install it, but got an error while update lock file.

Adding utilityhelper to Pipfile's [packages]...
Pipfile.lock (3e9aa7) out of date, updating to (de4848)...
Locking [dev-packages] dependencies...
Locking [packages] dependencies...

Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.
You can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.
Hint: try $ pipenv lock --pre if it is a pre-release dependency.
Could not find a version that matches utilityhelper (from -r c:\windows\temp\pipenv-ckgvtu-requirements\pipenv-u8pl3f-constraints.txt (line 35))

No versions found

Was https://pypi.tuna.tsinghua.edu.cn/simple reachable?

Duplicate

Most helpful comment

+1, in my case I couldn't install backports-ssl-match-hostname with the latest pipenv

All 3 comments

+1, in my case I couldn't install backports-ssl-match-hostname with the latest pipenv

Yes, I have a release coming out shortly which fixes name normalization -- there are a number of issues open on this topic, please see #2951, #2956, or #2963 for tracking this issue

I got an new conclusion.i install that package via command line, the package source i assigned is "https://pypi.org/simple" but the source in my pipfile is "https://pypi.tuna.tsinghua.edu.cn/simple".
i could not find that package in tsinghua source.
Maybe this result in update pipfile.lock fail.

Was this page helpful?
0 / 5 - 0 ratings