Pipenv: The `pipenv install --deploy --system` command is no longer working.

[ryan-blunden]

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:

• HOSTNAME
• SHLVL
• PYTHON_PIP_VERSION
• HOME
• GPG_KEY
• PATH
• LANG
• PYTHON_VERSION
• PWD
• PYTHONDONTWRITEBYTECODE
• PIP_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:/bin
• LANG: C.UTF-8
• PWD: /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.

[nhamlh]

It's required that the Pipfile.lock presents in the current folder for the --system option to work.

[uranusjr]

We can probably improve the error message to let the user know what to do next.

[ryan-blunden]

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, [e-mail]
wrote:

We can probably improve the error message to let the user know what to do
next.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/2183#issuecomment-388572572, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIHlkzz1Gorrw2QyXaNbXDOnKx7n0atks5txyQIgaJpZM4T8c5z
.

[uranusjr]

@ryan-blunden I didn’t check but #2181 could help.

[skorokithakis]

I got the same error trying to run pipenv install. Shouldn't it have created the lockfile itself, instead of give an error?

[stardust85]

With --deploy command you should definitely have Pipfile.lock and you should have it up-to-date. However the error message it gives should mention this. Without --deploy I'm not sure if it should require running pipenv lock explicitly.

[skorokithakis]

In my case, I'm using neither --deploy nor --system. Pipenv just seems to think I am.

[techalchemy]

Fixed by #2181

[ryan-blunden]

Many thanks!

On Tue., 15 May 2018, 16:59 Dan Ryan, [e-mail] wrote:

Closed #2183 https://github.com/pypa/pipenv/issues/2183.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pypa/pipenv/issues/2183#event-1628454561, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAIHlgWbDLh1KYuUITpjot7zlobsnAI1ks5ty2vdgaJpZM4T8c5z
.

[ryan-blunden]

Hi @techalchemy,

This needs to be re-opened as pipenv install --deploy --system is still failing.

Tested just now with pipenv version pipenv-2018.5.18.

[ryan-blunden]

I tried changing the command just to pipenv install --system but that didn't work either.

pipenv install --system
Warning: --system is intended to be used for Pipfile installation, not installation of specific packages. Aborting.
See also: --deploy flag.

I'm using https://gist.github.com/ryan-blunden/e27f8e48b134e041be22f07fcac943de to test.

[techalchemy]

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.

[ryan-blunden]

@techalchemy,

My apologies, that's not what I was trying to do.

I changed my gist to install pipenv from master (pip install git+https://github.com/pypa/pipenv.git) but I'm still getting the same error message.

Have I missed something? Is there a new way I tell pipenv to install system packages?

What do you want me to do? Should I open another ticket?

[uranusjr]

@ryan-blunden I think this has been fixed, and will be released soon. Please wait a few days to see if there is a new version, and open an issue if it is not fixed by then.

[ryan-blunden]

Ok, thanks @uranusjr. Will do.

[techalchemy]

@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 --system you can't install from a pipfile, you _must_ have a lockfile unless you pass --skip-lock. If you pass --deploy you 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 --deploy flag and add the --site-packages flag.

[nkatraga]

@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.

[TwoBitAlchemist]

:wave: Hi from 2020. I found this on Google and encountered this same misleading error. The problem was indeed a missing Pipfile.lock. Is there somewhere clearer I can +1 prioritizing the work to improve the error in this case? Cheers!

[uranusjr]

I don’t think there is one. Pipenv is entirely volunteer work, so the only way to prioritise something is to do it yourself (or sponsor someone to specifically do it).