![]() Hint: try $ pipenv lock -pre if it is a pre-release dependency. Alternatively, you can use $ pipenv install -skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation. First try clearing your dependency cache with $ pipenv lock -clear, then try the original command again. ![]() You likely have a mismatch in your sub-dependencies. ✘ Locking Failed! : File "/Users/anthony/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/resolver.py", line 741, in _main : resolve_packages(pre, clear, verbose, system, write, requirements_dir, packages, dev) : File "/Users/anthony/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/resolver.py", line 702, in resolve_packages : results, resolver = resolve( : File "/Users/anthony/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/resolver.py", line 684, in resolve : return resolve_deps( : File "/Users/anthony/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/utils.py", line 1397, in resolve_deps : results, hashes, markers_lookup, resolver, skipped = actually_resolve_deps( : File "/Users/anthony/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/utils.py", line 1110, in actually_resolve_deps : resolver.resolve() : File "/Users/anthony/.local/pipx/venvs/pipenv/lib/python3.8/site-packages/pipenv/utils.py", line 835, in resolve : raise ResolutionFailure(message=str(e)) : Warning: Your dependencies could not be resolved. ✔ Installation Succeeded Pipfile.lock (29ca33) out of date, updating to (cc17c6).
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |