pipenv: The `pipenv install --deploy --system` command is no longer working.
Be sure to check the existing issues (both open and closed!).
The pipenv install --deploy --system command is no longer working.
$ python -m pipenv.help output
Pipenv version: '11.10.4'
Pipenv location: '/usr/local/lib/python3.6/site-packages/pipenv'
Python location: '/usr/local/bin/python'
Other Python installations in PATH:
-
3.6:/usr/local/bin/python3.6m -
3.6:/usr/local/bin/python3.6 -
3.6:/usr/local/bin/python3.6 -
3.6.5:/usr/local/bin/python -
3.6.5:/usr/local/bin/python -
3.6.5:/usr/local/bin/python3 -
3.6.5:/usr/local/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.9.87-linuxkit-aufs',
'platform_system': 'Linux',
'platform_version': '#1 SMP Fri Mar 16 18:16:33 UTC 2018',
'python_full_version': '3.6.5',
'python_version': '3.6',
'sys_platform': 'linux'}
System environment variables:
HOSTNAMESHLVLPYTHON_PIP_VERSIONHOMEGPG_KEYPATHLANGPYTHON_VERSIONPWDPYTHONDONTWRITEBYTECODEPIP_PYTHON_PATH
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binLANG:C.UTF-8PWD:/usr/src/app
Contents of Pipfile (‘/usr/src/app/Pipfile’):
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[packages]
records = "*"
[dev-packages]
[requires]
python_version = "3.6"
Expected result
The pipenv install --deploy --system command completes successfully.
Actual result
Command exists with code 1 with the following output.
+ pipenv install --deploy --system
Warning: --system is intended to be used for Pipfile installation, not installation of specific packages. Aborting.
See also: --deploy flag.
Steps to replicate
See the gist at https://gist.github.com/ryan-blunden/e27f8e48b134e041be22f07fcac943de and run `make build.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 19 (7 by maintainers)
Hi @ryan-blunden. The Issue tracker is used for tracking changes merged into master. We already read your issue and fixed it in master, please do not use this as a forum to tell us how to run the project.
We can probably improve the error message to let the user know what to do next.
It’s required that the Pipfile.lock presents in the current folder for the
--systemoption to work.@ryan-blunden, I believe the error you were getting is because you missed adding the Pipfile, and Pipfile.lock to the directory in the container. Pipenv is unable to find your files. Try adding those files (If they are in your current working directory, you can do “COPY . /” ) to docker before running Pipenv install step. I was able to make it work with “Run Pipenv install --system” in the Dockerfile.
@ryan-blunden with the gist you linked, you should be getting an error, but it seems like you’re getting the wrong error. If you are passing
--systemyou can’t install from a pipfile, you must have a lockfile unless you pass--skip-lock. If you pass--deployyou can’t install from an out-of-date lockfile (one that is out of sync with your pipfile) which means you must both include your pipfile AND your lockfile and they must be in sync.If you want to do the resolution step in a container you need to drop the
--deployflag and add the--site-packagesflag.In my case, I’m using neither
--deploynor--system. Pipenv just seems to think I am.That would be great.
What exactly is the problem with that command now? Is there still a way to install libraries globally?
On Sat., 12 May 2018, 11:03 Tzu-ping Chung, notifications@github.com wrote:
With
--deploycommand you should definitely have Pipfile.lock and you should have it up-to-date. However the error message it gives should mention this. Without--deployI’m not sure if it should require runningpipenv lockexplicitly.