-
-
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
2018.11.14 regression: pipenv fails to install editable extras #3230
Comments
Hey @bertjwregeer, We did a quick check and this issue looks very darn similar to
This could be a coincidence, but if any of these issues solves your problem then I did a good job 😄 If not, the maintainers will get to this issue shortly. Cheers, |
@duplicate-issues: No, they are not the same or similar. |
Can't replicate here, can you try installing from a public pypi source? Or can you provide more info about the package structure, say, does it contain |
frostming, folder structure:
The projects themselves are stock standard setup tool projects. Nothing fancy going on. The issue is that pipenv or another library is adding a second set of quotes to the extra to be installed:
Notice the double quotes followed by the single quotes. It doesn't matter where I install the dependencies for the project from, private or not, this is currently broken. |
@bertjwregeer Please try to prune the virtualenv |
@frostming the issue occurred when running If I create the |
@frostming the nuance here is going to be that this is a local package which has a setupfile, yet we are escaping the extras for reasons which make no discernible sense. I'm going to venture a random guess that this is related to the upstream restructuring we made to @bertjwregeer -- I tried to get as close as possible to your setup as I could but I can't reproduce the issue -- are your extras in your here was my test run (using setup.cfg files): [[sources]]
url = "https://pypi.org/simple"
name = "pypi"
verify_ssl = true
[packages]
pylint = "*"
installer = {path = "./installer", editable = true, extras = ["virtualenv"] }
vistir = { path = "./vistir", editable = true, extras = ["spinner"] }
[dev-packages]
[requires]
python_version = "2.7"
[pipenv]
allow_prereleases = true /t/test2 pipenv install --dev
Creating a virtualenv for this project…
Pipfile: /tmp/test2/Pipfile
Using /home/hawk/.pyenv/versions/2.7.15/bin/python2 (2.7.15) to create virtualenv…
⠏ Creating virtual environment...New python executable in /home/hawk/.virtualenvs/test2-h6PFdzq5/bin/python2
Also creating executable in /home/hawk/.virtualenvs/test2-h6PFdzq5/bin/python
Installing setuptools, pip, wheel...
done.
Running virtualenv with interpreter /home/hawk/.pyenv/versions/2.7.15/bin/python2
✔ Successfully created virtual environment!
Virtualenv location: /home/hawk/.virtualenvs/test2-h6PFdzq5
Pipfile.lock (a7c78d) out of date, updating to (d69bb7)…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
✔ Success!
Updated Pipfile.lock (a7c78d)!
Installing dependencies from Pipfile.lock (a7c78d)…
🐍 ▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉▉ 47/47 — 00:00:09
To activate this project's virtualenv, run pipenv shell.
Alternatively, run a command inside the virtualenv with pipenv run. |
My extras are defined in
|
- Fixes #3230 Signed-off-by: Dan Ryan <[email protected]>
Awesome, that was exactly what I needed to sort this out. Thanks for the excerpt |
Issue description
Downgrading to pipenv version 2018.10.13, and everything works as expected.
Expected result
Pipfile.lock
is generatedActual result
💥
Steps to replicate
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
pipenv lock
$ pipenv --support
Pipenv version:
'2018.10.13'
Pipenv location:
'/home/vagrant/.local/lib/python2.7/site-packages/pipenv'
Python location:
'/usr/bin/python2'
Python installations found:
2.7.5
:/usr/bin/python2.7
PEP 508 Information:
System environment variables:
HISTTIMEFORMAT
PYTHONDONTWRITEBYTECODE
LESSOPEN
SSH_CLIENT
SELINUX_USE_CURRENT_RANGE
LOGNAME
USER
PATH
HOME
LANG
TERM
SHELL
SHLVL
HISTSIZE
XDG_RUNTIME_DIR
SSH_AUTH_SOCK
SELINUX_ROLE_REQUESTED
PIP_PYTHON_PATH
XDG_SESSION_ID
_
SSH_CONNECTION
SSH_TTY
OLDPWD
HOSTNAME
SELINUX_LEVEL_REQUESTED
HISTCONTROL
PWD
CPATH
PIP_SHIMS_BASE_MODULE
MAIL
LS_COLORS
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/vagrant/.local/bin:/home/vagrant/bin
SHELL
:/bin/bash
LANG
:en_US.UTF-8
PWD
:/home/vagrant/src
Contents of
Pipfile
('/home/vagrant/src/Pipfile'):The text was updated successfully, but these errors were encountered: