pipenv: v11.10.1: initial `pipenv install` in existing virtualenv fails
$ python -m pipenv.help output
Pipenv version: '11.10.1'
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.16.3-1-ARCH',
'platform_system': 'Linux',
'platform_version': '#1 SMP PREEMPT Thu Apr 19 09:17:56 UTC 2018',
'python_full_version': '3.6.5',
'python_version': '3.6',
'sys_platform': 'linux'}
System environment variables:
HOSTNAME
GPG_KEY
TERM
PYTHON_VERSION
PATH
PWD
LANG
PYTHON_PIP_VERSION
SHLVL
HOME
_
OLDPWD
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
:/app
Expected result
Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead.
Creating a Pipfile for this project…
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Using pip: -i https://pypi.python.org/simple
ROUND 1
Current constraints:
Finding the best candidates:
Finding secondary dependencies:
------------------------------------------------------------
Result of round 1: stable, done
Locking [packages] dependencies…
Using pip: -i https://pypi.python.org/simple
ROUND 1
Current constraints:
Finding the best candidates:
Finding secondary dependencies:
------------------------------------------------------------
Result of round 1: stable, done
Updated Pipfile.lock (625834)!
Installing dependencies from Pipfile.lock (625834)…
Actual result
Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead.
Creating a Pipfile for this project…
Warning: --system is intended to be used for Pipfile installation, not installation of specific packages. Aborting.
See also: --deploy flag.
Steps to replicate
Requires pipenv v11.10.1. Not reproducible in v11.10.0. In an empty directory, run:
$ virtualenv env
$ source env/bin/activate
$ pipenv install
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 19 (10 by maintainers)
Commits related to this issue
- Make sure we are not in a virtualenv if aborting - Fixes #2078 Signed-off-by: Dan Ryan <dan@danryan.co> — committed to pypa/pipenv by techalchemy 6 years ago
- Remove py34 from tox for pinned version tests - Removes py34 environment for tox envs that use the requirements-dev.txt. It seems that in python 3.4 a sphinx requirement does not have all their depen... — committed to cenotes/cenotes by ioparaskev 6 years ago
- Remove py34 from tox for pinned version tests - Removes py34 environment for tox envs that use the requirements-dev.txt. It seems that in python 3.4 a sphinx requirement does not have all their depen... — committed to cenotes/cenotes by ioparaskev 6 years ago
- Work around pipenv bug See: https://github.com/pypa/pipenv/issues/2078 — committed to FlowFX/flowfx.de by FlowFX 6 years ago
- Fix issue with travis builds - Keeps pipenv to 11.10.0 in tox ini due to existing issue with travis and tox (https://github.com/pypa/pipenv/issues/2078) — committed to cenotes/cenotes-lib by ioparaskev 6 years ago
- Fix issue with travis builds - Keeps pipenv to 11.10.0 in tox ini due to existing issue with travis and tox (https://github.com/pypa/pipenv/issues/2078) — committed to cenotes/cenotes-lib by ioparaskev 6 years ago
For everybody having problems with pipenv: try poetry https://github.com/sdispater/poetry
I was waiting for a whole month for this fix, but after pipenv disappointed me several times now, i switched … pipenv still has not earned its 1.0 release number!
Please release this.
yep, release is coming out tomorrow, many changes and improvements.
@kakulukia If you aren’t able to contribute in a mature and productive way, please refrain from contributing at all. Packaging is a complicated subject and the tooling is quite difficult; the next release of pipenv brings many internal changes and improvements, including an upgrade to pip 10 and an upgrade to piptools. As we are all volunteers, this took considerable time and effort on the side.
FYI: this is blowing up on me, and I worked around it as described by @pegler , so hopefully this re-fixed fix can be released soon.
@pegler thanks for the fix and sorry for the logic error!
Based on reading your PR you passed
—system
which, as the warning states, can’t be used to install individual packages or to do anything besides take a lockfile and put it into a docker container basically.You’re running inside a virtualenv I can see, so passing
—system
is almost certainly not what you want to do unless your goal is actually to install packages in your systems site packages directory. These warnings are there in this version for a reason