Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Environment variables PIPENV_SKIP_LOCK does not work.

See original GitHub issue

I don’t know if it is bug or my misunderstanding of document.

Issue description

Expected result

As the document described, if PIPENV_SKIP_LOCK is setted to true, it will skip locking mechanisms.

Actual result

when my OS Environment variables PIPENV_SKIP_LOCK is true , pipenv still excute locking.

Steps to replicate

$ echo $PIPENV_SKIP_LOCK
true
$ pipenv uninstall autopep8
Un-installing autopep8…
Uninstalling autopep8-1.4.3:
  Successfully uninstalled autopep8-1.4.3

Removing autopep8 from Pipfile…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
Updated Pipfile.lock (1402f9)!

Issue Analytics

State:
Created 5 years ago
Comments:11 (4 by maintainers)

Top GitHub Comments

2reactions

BeyondEvilcommented, Jun 18, 2019

This (still?) doesn’t work with the latest version of pipenv. @frostming

$ echo $PIPENV_SKIP_LOCK
true

$ pipenv install pytest
Installing pytest…
Adding pytest to Pipfile's [packages]…
✔ Installation Succeeded 
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
✔ Success! 
Updated Pipfile.lock (1c4d3d)!
Installing dependencies from Pipfile.lock (1c4d3d)…
  🐍   ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 12/12 — 00:00:02
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run.

$ pipenv --version
pipenv, version 2018.11.26

$ python3 --version
Python 3.7.3

$ uname -a
Darwin Kernel Version 18.5.0: Mon Mar 11 20:40:32 PDT 2019; root:xnu-4903.251.3~3/RELEASE_X86_64 x86_64

$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.14.4
BuildVersion:   18E226

I also tried adding PIPENV_SKIP_LOCK=true to the project .env-file with same result.

1reaction

alejandrobalderascommented, Mar 3, 2021

I was just having the same exact issue when trying to install pipenv in a docker container via the apt package manager. I switched to installing pipenv via pip and now it works as expected.

FROM python:3.8-slim
ENV PIPENV_SKIP_LOCK=1
- RUN apt update && apt -y install pipenv
+ RUN pip3 install pipenv
WORKDIR /app
COPY . .
RUN pipenv install