-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VCS install with --skip-lock fails with "empty revision" error #6189
Comments
dennisvang
changed the title
Editable install from VCS with --skip-lock fails with "empty revision" error
Install from VCS with --skip-lock fails with "empty revision" error
Jul 10, 2024
dennisvang
changed the title
Install from VCS with --skip-lock fails with "empty revision" error
VCS install with --skip-lock fails with "empty revision" error
Jul 11, 2024
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue description
Starting from a clean slate, with a dir containing only a single
Pipfile
with a single VCS dependency, runningpipenv install --skip-lock
fails with the error:This happens even though a proper revision is specified, as in:
Moreover, the exact same
Pipfile
works without issue when doing a normalpipenv install
, without--skip-lock
.Reproduced on Ubuntu 22.04.4 LTS and Amazon Linux 2023, running Python 3.11 with
pipenv
version 2024.0.1, both witheditable = true
andeditable = false
.This is relevant for deployment to AWS Elastic Beanstalk, because that uses
--skip-lock
, as explained here, unless we provide aPipfile.lock
or arequirements.txt
, which is not an option.Expected result
I expected the specified version of the package to be installed without issue.
Actual result
command line output (using `editable=true`)
Steps to replicate
Create an empty dir, add the following
Pipfile
:The
requests
package is just a random example. The same issue arises with other packages.Run
pipenv install --skip-lock
$ pipenv --support
Pipenv version:
'2024.0.1'
Pipenv location:
'/home/me/.local/lib/python3.11/site-packages/pipenv'
Python location:
'/home/me/.pyenv/versions/3.11.6/bin/python3.11'
OS Name:
'posix'
User pip version:
'24.0'
user Python installations found:
PEP 508 Information:
System environment variables:
SHELL
SESSION_MANAGER
QT_ACCESSIBILITY
PIPENV_VENV_IN_PROJECT
COLORTERM
PYENV_SHELL
XDG_CONFIG_DIRS
SSH_AGENT_LAUNCHER
XDG_MENU_PREFIX
GNOME_DESKTOP_SESSION_ID
LANGUAGE
LC_ADDRESS
GNOME_SHELL_SESSION_MODE
LC_NAME
SSH_AUTH_SOCK
GIT_PS1_SHOWDIRTYSTATE
XMODIFIERS
DESKTOP_SESSION
LC_MONETARY
GTK_MODULES
PWD
LOGNAME
XDG_SESSION_DESKTOP
XDG_SESSION_TYPE
SYSTEMD_EXEC_PID
XAUTHORITY
HOME
USERNAME
IM_CONFIG_PHASE
LC_PAPER
LANG
LS_COLORS
XDG_CURRENT_DESKTOP
VTE_VERSION
WAYLAND_DISPLAY
GNOME_TERMINAL_SCREEN
GNOME_SETUP_DISPLAY
LESSCLOSE
XDG_SESSION_CLASS
TERM
LC_IDENTIFICATION
LESSOPEN
USER
GNOME_TERMINAL_SERVICE
DISPLAY
SHLVL
LC_TELEPHONE
QT_IM_MODULE
LC_MEASUREMENT
PAPERSIZE
XDG_RUNTIME_DIR
PYENV_ROOT
LC_TIME
XDG_DATA_DIRS
PATH
GDMSESSION
DBUS_SESSION_BUS_ADDRESS
LC_NUMERIC
OLDPWD
_
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PYTHONFINDER_IGNORE_UNSUPPORTED
Pipenv–specific environment variables:
PIPENV_VENV_IN_PROJECT
:1
Debug–specific environment variables:
PATH
:/home/me/.pyenv/versions/3.9.18/bin:/home/me/.pyenv/versions/3.8.18/bin:/home/me/.pyenv/versions/3.11.6/bin:/home/me/.pyenv/versions/3.8.13/bin:/home/me/.pyenv/shims:/home/me/.npm-global/bin:/home/me/.local/bin:/home/me/.pyenv/bin:/home/me/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin
SHELL
:/bin/bash
LANG
:en_CA.UTF-8
PWD
:/home/me/Desktop/temp/pipfiletest
Contents of
Pipfile
('/home/me/Desktop/temp/pipfiletest/Pipfile'):Contents of
Pipfile.lock
('/home/me/Desktop/temp/pipfiletest/Pipfile.lock'):The text was updated successfully, but these errors were encountered: