Be sure to check the existing issues, both open and closed.
pipenv graph
returns all empty, and pipenv graph --json
raises an error,'raise JSONDecodeError("Expecting value", s, err.value) from None'
Here is my Pipfile:
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[packages]
records = "*"
pyodbc = "*"
cython = "*"
pymssql = "*"
configparser = "*"
ipython = "*"
pymysql = "*"
[dev-packages]
[requires]
python_version = "3.6"
Some package dependency informaton
Empty, and pipenv graph has no option --verbose.
Not sure, might be after installing configparser.
thanks for the report.
is there any way to resolve this issue?
@eduedix Like most issues, you can resolve this by tracing the code, committing a fix, and sending in a pull request :)
@uranusjr sure. I have seen the issue as closed but wasn't sure about how it got resolved. That's why I ask the question here :) Is it resolved for real or just closed but not resolved?
I honestly donβt know. Our resolver is still receiving a lot of rewrites between versions, and as the nature of resolving packages is, the behaviour can vary between versions even with seemingly unrelated changes. We have a significant portion of issues closed like this because they donβt pop up anymore, but in reality we donβt actually know if they are fixed.
I cannot reproduce this myself, but the resolution logic is by nature quite dependant on the local environment. Youβd be better suited to fix this if you can reproduceβ¦ :(
Or to provide logs and detail after upgrading.
Thanks now fixed after upgrading to version 2018.05.18 with pip install --upgrade pipenv --user
Regression? I still see no output (well a newline) from "pipenv graph" after "pipenv install --dev"
api; pip install --upgrade pipenv --user
Collecting pipenv
Downloading https://files.pythonhosted.org/packages/eb/64/9b2747d54f2008ac3dfe86c0b1c8ec126042726fd8a540d5208d26732701/pipenv-2018.7.1-py3-none-any.whl (5.0MB)
100% |ββββββββββββββββββββββββββββββββ| 5.0MB 3.0MB/s
Requirement already satisfied, skipping upgrade: virtualenv in /home/thayer/.pyenv/versions/3.6.1/lib/python3.6/site-packages (from pipenv) (15.1.0)
Requirement already satisfied, skipping upgrade: certifi in /home/thayer/.pyenv/versions/3.6.1/lib/python3.6/site-packages (from pipenv) (2017.11.5)
Requirement already satisfied, skipping upgrade: virtualenv-clone>=0.2.5 in /home/thayer/.pyenv/versions/3.6.1/lib/python3.6/site-packages (from pipenv) (0.2.6)
Requirement already satisfied, skipping upgrade: pip>=9.0.1 in /home/thayer/.pyenv/versions/3.6.1/lib/python3.6/site-packages (from pipenv) (18.0)
Requirement already satisfied, skipping upgrade: setuptools>=36.2.1 in /home/thayer/.pyenv/versions/3.6.1/lib/python3.6/site-packages (from pipenv) (38.4.0)
Installing collected packages: pipenv
Successfully installed pipenv-2018.7.1
:::: fang 11:38:10 (cgthayer-hc-unittests) 0 api;
:::: fang 11:38:10 (cgthayer-hc-unittests) 0 api; pipenv graph
:::: fang 11:38:16 (cgthayer-hc-unittests) 0 api;
I am on version 9.0.0. I am able to reproduce this bug. Is there any possibility to fix this issue in upcoming versions? I truly respect the maintainers' time and efforts. Thanks :)
Version 9.0.0 was released in 2017, FYI.
I have this problem in Linux container right now. How to debug it?
Try running pipdeptree and see if that works; IIRC thatβs how Pipenv uses internally.
pipdeptree
return a correct tree
Most helpful comment
Thanks now fixed after upgrading to version 2018.05.18 with
pip install --upgrade pipenv --user