$ python3 -m pipenv.help
<details><summary>$ python -m pipenv.help output</summary>
Pipenv version: `'2018.05.18'`
Pipenv location: `'/home/kingname/.local/lib/python3.6/site-packages/pipenv'`
Python location: `'/usr/bin/python3'`
Other Python installations in `PATH`:
- `2.7`: `/usr/bin/python2.7`
- `2.7`: `/usr/bin/python2.7`
- `3.5`: `/usr/bin/python3.5m`
- `3.5`: `/usr/bin/python3.5`
- `3.6`: `/usr/bin/python3.6m`
- `3.6`: `/usr/bin/python3.6`
- `2.7.12`: `/usr/bin/python`
- `2.7.12`: `/usr/bin/python2`
- `3.6.5`: `/usr/bin/python3`
PEP 508 Information:
{'implementation_name': 'cpython',
'implementation_version': '3.6.5',
'os_name': 'posix',
'platform_machine': 'x86_64',
'platform_python_implementation': 'CPython',
'platform_release': '4.4.0-43-Microsoft',
'platform_system': 'Linux',
'platform_version': '#1-Microsoft Wed Dec 31 14:42:53 PST 2014',
'python_full_version': '3.6.5',
'python_version': '3.6',
'sys_platform': 'linux'}
show command not find
instead of raise python error.
When possible, provide the verbose output (--verbose
), especially for locking and dependencies resolving issues.
do it in Ububtu subsystem of Windows 10
Can’t reproduce. My guess is asdf stands for something particular in your environment. Pipenv does emit command not found error if it can’t find a command, but asdf seems to be actually found.
The command was found in this case. It is a pyenv dependency. https://github.com/tuvistavie/asdf-python
In my case, any string which is not a command will case this error. not only asdf, but also any other strings such as 'x123', 'mmmm', 'qqqq' and etc. but for existed commands, everything will be fine.
Can you provide the error message of that happening? The above error is an import error related to a missing system dependency required for the package asdf
In pipenv shell, any string will raise error if it is not an existed Command. But any valid Command work as normal. And if I exit the pipenv shell, everything will be ok.
Something is going quite wrong with your Python environment :| Pipenv is indeed related to the exceptions, but it’s caused by an underlying misconfiguration in your system somewhere.
This problem looks similar, but for apt-get instead of Pipenv (both are built with Python, however!). You might want to try the accepted solution and see if it solves your problem.
https://askubuntu.com/questions/720416/no-module-named-gdbm
problem solved, just to sudo apt-get install python3.6-gdbm
I changed the title to make this more searchable, in case others need this in the future.
Most helpful comment
problem solved, just to
sudo apt-get install python3.6-gdbm