uranusjr
commented
6 years ago Tracked in upstream repo (referenced above).
Closed rafaelcaricio closed 6 years ago
uranusjr
commented
6 years ago Tracked in upstream repo (referenced above).
uranusjr
commented
6 years ago On second thought, I’m going to keep this open so people don’t open duplicates.
nikovitto
commented
6 years ago Same problem here. See attach log. pipenverror.log
mbarneyjr
commented
6 years ago Same problem here
Froskekongen
commented
6 years ago This is extremely aggravating. Can you please try to coordinate releases of pip and pipenv?
nealedj
commented
6 years ago Workaround for typical virtualenv setup:
pip install pipenv
pipenv run pip install pip==18.0
pipenv install
techalchemy
commented
6 years ago Hmm is this actually moved?
uranusjr
commented
6 years ago @Froskekongen Please try to avoid non-constructive messages. We understand this is frustrating, but interrogation doesn’t help. If you feel we need to improve, consider offering help instead of shouting at the sideline. “We” (whoever you are referring to) are always short of resources, and would gladly use your help.
pfwnicks
commented
6 years ago same issue here but only for new pipenv environments, installs still work on the old ones as I have not updated to the newest pip in there.
@nealedj suggestion worked
https://github.com/pypa/pipenv/issues/2924#issuecomment-427351356
allen-fisher-spok
commented
6 years ago I'm seeing this issue as well. @nealedj 's suggestion worked correctly, although if you're working around this in a build environment that already has pipenv installed, you don't need to re-install pipenv. Only lines 2 and 3 of his workaround are needed.
bweigel
commented
6 years ago same issue
Also @nealedj 's fix doesn't work for me... :frowning_face:
Ok...maybe it does...I was running tox and and needed to add the line pipenv run pip install pip==18.0 in the commands section:
[tox]
envlist = py36, flake8
[testenv:flake8]
basepython = python
deps = flake8
commands = flake8 .
[testenv]
passenv = AWS_PROFILE
AWS_DEFAULT_REGION
AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
deps =
pipenv
commands =
pipenv run pip install pip==18.0
pipenv install --dev --ignore-pipfile
pipenv run py.test -vYou can also fix this by setting the environment variable PIP_SHIMS_BASE_MODULE=pipenv.patched.notpip as a temporary workaround. I will cut a release of all of the involved libraries today including pipenv.
franknarf8
commented
6 years ago And for Windows machines you can use the following workaround :
pipenv run python -m pip install -U pip==18.0
fbidu
commented
6 years ago Had the same issue here
massenz
commented
6 years ago If you installed pipenv directly (with sudo -H pip install pipenv) @nealedj solution may not work.
What worked for me was:
sudo -H pip install pip==18.0(and I had to do that, as homebrew install pipenv tries to install Python 3.7 on top of my existing Python 3.6, which is extremely unwanted -- and also fails, too.)
skinitimski
commented
6 years ago If you happen to be using --system, then you will need to downgrade your system/global pip to 18.0 as well. I am new to pipenv as of today (what a tough day to get started!) and this was not immediately apparent to me.
ghost
commented
6 years ago I'm still running into issues with both pip version 18 and 10.0.1 along with pipenv 2018.7.1:
Before I cleared out the cache:
ligemer@ligemer:~/Development/.circleci$ pip --version
pip 18.0 from /home/ligemer/.local/lib/python3.5/site-packages/pip (python 3.5)
ligemer@ligemer:~/Development/.circleci$ pipenv --version
pipenv, version 2018.7.1
ligemer@ligemer:~/Development/.circleci$ pipenv update
Running $ pipenv lock then $ pipenv sync.
Locking [dev-packages] dependencies...
Locking [packages] dependencies...
ckages/pipenv/utils.py", line 402, in resolve_deps
req_dir=req_dir
File "/home/ligemer/.local/lib/python3.5/site-packages/pipenv/utils.py", line 250, in actually_resolve_deps
req = Requirement.from_line(dep)
File "/home/ligemer/.local/lib/python3.5/site-packages/pipenv/vendor/requirementslib/models/requirements.py", line 704, in from_line
line, extras = _strip_extras(line)
TypeError: 'module' object is not callableFresh shell worked with:
pip install -U pip==18.0
pip install pipenv
dowinweb
commented
6 years ago pip install pipenv pipenv run pip install pip==18.0 pipenv install
do not work for me any other solutions? okay, i solve this by using this command: python3 -m pip install pipenv==2018.5.18
jlsneto
commented
6 years ago Thannnks! Work for me!
pip install pipenv pipenv run pip install pip==18.0 pipenv install
amqdn
commented
6 years ago Following on as @skinitimski has said --
On Windows 10, even if I had the local pip in my working pipenv downgraded to 18.0 via pipenv run pip install pip==18.0, I still could not install dependencies for a project using pipenv because, it appears, I needed the system pip to be downgraded as well.
For me, that was:
python -m pip install pip==18.0
pipenv install --dev@amqdn that is correct, the system pip is the one that installs packages for you, around the system and unless you make other tweaks, until we get the release cut you'll have the most success pinning this
Swoorup
commented
6 years ago Doesn't pipenv have unittest to avoid these kinds of errors upon release?
fbidu
commented
6 years ago Doesn't pipenv have unittest to avoid these kinds of errors upon release?
AFAIK it wasn't a Pipenv release that broke stuff but a pip one.
techalchemy
commented
6 years ago As in all cases it's a bit more complicated, we are using pip internals which is not a great practice, and as part of our slow process of splitting out pipenv's rather complex code we've left a few loose ends where we aren't gracefully handling the switch.
In addition there was a gap in the test coverage of our main compatibility library, which wasn't building against pip's master branch for whatever reason. You can see here that this is now corrected, we should capture any upstream issues before they become a problem. This is on a daily cron, so hopefully we will avoid this going forward.
We have an ongoing discussion about how to refactor some internals to avoid importing things directly from pip, and that will be the long term solution, but for now this will provide some short term security
amqdn
commented
6 years ago Great! Thanks for your work and attention!
-----Original Message----- From: "Dan Ryan" notifications@github.com Sent: 10/7/2018 2:51 PM To: "pypa/pipenv" pipenv@noreply.github.com Cc: "amqdn" amqdnguyen@gmail.com; "Mention" mention@noreply.github.com Subject: Re: [pypa/pipenv] pip 18.1 causes "TypeError: 'module' object is notcallable" (#2924)
As in all cases it's a bit more complicated, we are using pip internals which is not a great practice, and as part of our slow process of splitting out pipenv's rather complex code we've left a few loose ends where we aren't gracefully handling the switch. In addition there was a gap in the test coverage of our main compatibility library, which wasn't building against pip's master branch for whatever reason. You can see hare that this is now corrected, we should capture any upstream issues before they become a problem. This is on a daily cron, so hopefully we will avoid this going forward. We have an ongoing discussion about how to refactor some internals to avoid importing things directly from pip, and that will be the long term solution, but for now this will provide some short term security — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
nki13
commented
6 years ago I cannot get pipenv install to run to save my life right now. Here is what it shows me...Any suggestions? Help really appreciated!
vagrant@ubuntu-xenial:/vagrant/HW2/wolfit$ pipenv install
Installing dependencies from Pipfile.lock (b9d8dc)...
Traceback (most recent call last):▉▉▉▉ 0/48 — 00:00:00
File "/home/vagrant/.local/bin/pipenv", line 11, in
Figured it out by typing this: $ pip install --user pip==18.0
longfellowone
commented
6 years ago pip install --user pip==18.0
Worked for me on Ubuntu
piccolbo
commented
6 years ago Workaround doesn't work for me on travis. https://travis-ci.org/piccolbo/altair_recipes/jobs/438443134
jarebear6expepjozn6rakjq5iczi3irqwphcvb
commented
6 years ago TypeError: 'module' object is not callableInstalled via curl https://raw.githubusercontent.com/pypa/pipenv/master/get-pipenv.py | python
pip install --user pip==18.0 resolves it.
abhi-jha
commented
6 years ago pip install --user pip==18.0 resolves it
castarco
commented
6 years ago I'm suffering this problem even with pip 18.0 , I scanned my full system to see if there's a "hidden" pip somewhere with version 18.1 ... and nothing, the system's pip is at version 9.0.1, my user's pip is 18.0, my project's virtualenv's pip is at 18.0.
gsemet
commented
6 years ago I now freeze pip and pipenv in all my projects (in a makefile), for the same reason all my pipfile packages are frozen in the lockfile: we cannot have our CI breaks overnight because pip or pipenv broke something. This is clearly a weakness of this "let's ditch the semver" recent trend. I understand both are intimately linked, maybe too much, but damned, such a regression happen at every releases !
I know you guys do a lot of work on pipenv, and it is a really great tool, but isn't there a way we can protect against such issues from happening over and over? Maybe move most of the logic to inside the virtualenv and not rely on the user's pip + pipenv installations? It would allow pipenv to freeze its own pip and validate it after each pip release? Probably a better option exists.
My solution is ugly, but work: freeze the pipenv and pip in the makefile, and maintain them. This also means two different projects on the same machine cannot use two different pip+pipenv versions combination.
ben-g-
commented
6 years ago Setting the environment variable PIP_SHIMS_BASE_MODULE=pipenv.patched.notpip didn't work for me, but pipenv run pip install pip==18.0 does.
stefan-it
commented
6 years ago 18.0 did not work for me. So I tried the following:
pip install --user --upgrade pip # to install latest 18.1
pip install --user git+https://github.com/pypa/pipenv.gitThis uses latest master of pipenv and it worked :confetti_ball:
sultaniman
commented
6 years ago Our CI was broken today and here is .travis.yml adjustments
language: python
python:
- "3.6.6"
install:
- pip install pipenv codecov -U
- pipenv install pip==18.0 # pin pip
- pipenv install
- pipenv install --dev
script:
- bin/run_tests
dci-aloughran
commented
6 years ago Hey guys, Silly question - why has this bug been closed? I see the workaround is either using pipenv from master or installing an older version of pip - is there going to be a fix released too?
baby5
commented
6 years ago i think pipenv should specify pip version when create virtualenv to avoid problems like this.
encukou
commented
6 years ago @dci-aloughran Usually, issues are closed when the fix is merged in the master branch, not when a release is made. That's the case here – the code is in, but a release on PyPI isn't ready yet.
codingjoe
commented
6 years ago @dci-aloughran Usually, issues are closed when the fix is merged in the master branch, not when a release is made. That's the case here – the code is in, but a release on PyPI isn't ready yet.
True, but it still maybe a good idea to publish a bug fix release, since this is affecting a lot of folks.
gsemet
commented
6 years ago semver would have helped a lot here...
encukou
commented
6 years ago @codingjoe As I understand, a release is in the works. I can imagine it's been a wild weekend for the volunteers, especially @techalchemy; please give them a bit more time.
@gsemet Actually, in this case it would not – semver doesn't cover private API. How much have you studied the issue?
codingjoe
commented
6 years ago Limiting the the pip version could be an option, similar to how PyCQA does it with flake8. Even tho flake8 and all of it's dependencies are maintained by the same group of people they limit dependencies.
encukou
commented
6 years ago I'm not a PyPA contributor, but I'd like to suggest, in general: Before offering solutions, please take the time to read the existing discussion to make sure you're contributing something new. The discussion is, unfortunately, scattered all over the place and there's quite a lot of it already – see links to the various issues and PRs above.
gsemet
commented
6 years ago @encukou This would have allowed to quicky release a fix on the current version of pipenv without having to update with all new (potentially breaking) features. Now we have a "every update might break, deal with it" mentality, so people freeze pip and pipenv to at least control when the update happen. With semver we can accept bugfixes while refusing major change pretty easily.
And please avoid personal attack.
PhilipAbed
commented
6 years ago i tried work around,, see down there i put pip --version and it shows 18.0 still didnt help, i re-installed python/pip/pipenv.. all of them for nothing.. still getting error, note: it worked before, suddenly today pipenv stopped working
C:\Users\PhilipAbed\Downloads\test\GithubProjects\whois-master-python>pipenv install django Installing django... Looking in indexes: https://pypi.python.org/simple Collecting django Downloading https://files.pythonhosted.org/packages/32/ab/22530cc1b2114e6067eece94a333d6c749fa1c56a009f0721e51c181ea53/Django-2.1.2-py3-none-any.whl (7.3MB) Collecting pytz (from django) Using cached https://files.pythonhosted.org/packages/30/4e/27c34b62430286c6d59177a0842ed90dc789ce5d1ed740887653b898779a/pytz-2018.5-py2.py3-none-any.whl Installing collected packages: pytz, django Successfully installed django-2.1.2 pytz-2018.5
Adding django to Pipfile's [packages]... Pipfile.lock (f6afc3) out of date, updating to (10a1c3)... Locking [dev-packages] dependencies... oaming\Python\Python37\site-packages\pipenv\utils.py", line 402, in resolve_deps req_dir=req_dir File "C:\Users\PhilipAbed\AppData\Roaming\Python\Python37\site-packages\pipenv\utils.py", line 250, in actually_resolve_deps req = Requirement.from_line(dep) File "C:\Users\PhilipAbed\AppData\Roaming\Python\Python37\site-packages\pipenv\vendor\requirementslib\models\requirements.py", line 704, in from_line line, extras = _strip_extras(line) TypeError: 'module' object is not callable
C:\Users\PhilipAbed\Downloads\test\GithubProjects\whois-master-python>pip --version pip 18.0 from c:\users\philipabed\appdata\local\programs\python\python37-32\lib\site-packages\pip (python 3.7)
C:\Users\PhilipAbed\Downloads\test\GithubProjects\whois-master-python>
sbruno
commented
6 years ago @StinkyLord123 I had problems going back to pip 18.0 so I hacked the installed pipenv code in order to not be blocked. I know this is a dirty workaround and not recommended, but if you just need it locally for your development environment it may work.
I edited the _compat.py file in the requirementslib folder, that based on your traceback it should be
"C:\Users\PhilipAbed\AppData\Roaming\Python\Python37\site-packages\pipenv\vendor\requirementslib\_compat.py"
There, I located the line:
_strip_extras = do_import("req.req_install", "_strip_extras")
That is the one that imports incorrectly, and after that, I just copied the code of the function that should be imported:
import re
def _strip_extras(path):
m = re.match(r'^(.+)(\[[^\]]+\])$', path)
extras = None
if m:
path_no_extras = m.group(1)
extras = m.group(2)
else:
path_no_extras = path
return path_no_extras, extrasThis could be a workaround if you need it for a development environment and not to release anything, until it gets officially fixed.
BeyondEvil
commented
6 years ago Workaround doesn't work for me.
I'm using pipenv in a docker image.
Here's what the RUN target looks like with the workaround:
&& pipenv run pip install --upgrade pip==18.0 \
&& pipenv --site-packages install --skip-lock```
And here's the relevant output:
```Collecting PyYAML<=3.13,>=3.10 (from awscli===1.16.21)
Downloading https://files.pythonhosted.org/packages/9e/a3/1d13970c3f36777c583f136c136f804d70f500168edc1edea6daa7200769/PyYAML-3.13.tar.gz (270kB)
Collecting certifi (from pipenv===2018.7.1)
Downloading https://files.pythonhosted.org/packages/df/f7/04fee6ac349e915b82171f8e23cee63644d83663b34c539f7a09aed18f9e/certifi-2018.8.24-py2.py3-none-any.whl (147kB)
Collecting virtualenv (from pipenv===2018.7.1)
Downloading https://files.pythonhosted.org/packages/b6/30/96a02b2287098b23b875bc8c2f58071c35d2efe84f747b64d523721dc2b5/virtualenv-16.0.0-py2.py3-none-any.whl (1.9MB)
Collecting virtualenv-clone>=0.2.5 (from pipenv===2018.7.1)
Downloading https://files.pythonhosted.org/packages/6d/c2/dccb5ccf599e0c5d1eea6acbd058af7a71384f9740179db67a9182a24798/virtualenv_clone-0.3.0-py2.py3-none-any.whl
Requirement already satisfied, skipping upgrade: setuptools>=36.2.1 in /usr/local/lib/python3.7/site-packages (from pipenv===2018.7.1) (40.4.3)
Collecting python-dateutil<3.0.0,>=2.1; python_version >= "2.7" (from botocore==1.12.11->awscli===1.16.21)
Downloading https://files.pythonhosted.org/packages/cf/f5/af2b09c957ace60dcfac112b669c45c8c97e32f94aa8b56da4c6d1682825/python_dateutil-2.7.3-py2.py3-none-any.whl (211kB)
Collecting urllib3<1.24,>=1.20 (from botocore==1.12.11->awscli===1.16.21)
Downloading https://files.pythonhosted.org/packages/bd/c9/6fdd990019071a4a32a5e7cb78a1d92c53851ef4f56f62a3486e6a7d8ffb/urllib3-1.23-py2.py3-none-any.whl (133kB)
Collecting jmespath<1.0.0,>=0.7.1 (from botocore==1.12.11->awscli===1.16.21)
Downloading https://files.pythonhosted.org/packages/b7/31/05c8d001f7f87f0f07289a5fc0fc3832e9a57f2dbd4d3b0fee70e0d51365/jmespath-0.9.3-py2.py3-none-any.whl
Collecting pyasn1>=0.1.3 (from rsa<=3.5.0,>=3.1.2->awscli===1.16.21)
Downloading https://files.pythonhosted.org/packages/d1/a1/7790cc85db38daa874f6a2e6308131b9953feb1367f2ae2d1123bb93a9f5/pyasn1-0.4.4-py2.py3-none-any.whl (72kB)
Collecting six>=1.5 (from python-dateutil<3.0.0,>=2.1; python_version >= "2.7"->botocore==1.12.11->awscli===1.16.21)
Downloading https://files.pythonhosted.org/packages/67/4b/141a581104b1f6397bfa78ac9d43d8ad29a7ca43ea90a2d863fe3056e86a/six-1.11.0-py2.py3-none-any.whl
Building wheels for collected packages: PyYAML
Running setup.py bdist_wheel for PyYAML: started
Running setup.py bdist_wheel for PyYAML: finished with status 'done'
Stored in directory: /root/.cache/pip/wheels/ad/da/0c/74eb680767247273e2cf2723482cb9c924fe70af57c334513f
Successfully built PyYAML
Installing collected packages: six, python-dateutil, urllib3, docutils, jmespath, botocore, s3transfer, pyasn1, rsa, colorama, PyYAML, awscli, certifi, virtualenv, virtualenv-clone, pipenv
Successfully installed PyYAML-3.13 awscli-1.16.21 botocore-1.12.11 certifi-2018.8.24 colorama-0.3.9 docutils-0.14 jmespath-0.9.3 pipenv-2018.7.1 pyasn1-0.4.4 python-dateutil-2.7.3 rsa-3.4.2 s3transfer-0.1.13 six-1.11.0 urllib3-1.23 virtualenv-16.0.0 virtualenv-clone-0.3.0
Removing intermediate container 3510df0aee94
---> d679fad77207
Step 3/10 : ARG APP_DIR=/app/dpo-automation/
---> Running in 9e7d6ed45d46
Removing intermediate container 9e7d6ed45d46
---> b12adce64976
Step 4/10 : COPY ./Pipfile ${APP_DIR}
---> 32f53411f8f7
Step 5/10 : ENV PATH="/root/.local/bin:${PATH}"
---> Running in 244eecc7ab46
Removing intermediate container 244eecc7ab46
---> c1852122736a
Step 6/10 : RUN cd ${APP_DIR} && pipenv run pip install --upgrade pip==18.0 && pipenv --site-packages install --skip-lock
---> Running in 0a9fb979bfa5
Creating a virtualenv for this project...
Pipfile: /app/dpo-automation/Pipfile
Using /usr/local/bin/python (3.7.0) to create virtualenv...
Already using interpreter /usr/local/bin/python
Using base prefix '/usr/local'
/usr/local/lib/python3.7/site-packages/virtualenv.py:1041: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp
New python executable in /root/.local/share/virtualenvs/dpo-automation-b0iFxfPY/bin/python
Installing setuptools, pip, wheel...done.
Setting project for dpo-automation-b0iFxfPY to /app/dpo-automation
Virtualenv location: /root/.local/share/virtualenvs/dpo-automation-b0iFxfPY
Collecting pip==18.0
Downloading https://files.pythonhosted.org/packages/5f/25/e52d3f31441505a5f3af41213346e5b6c221c9e086a166f3703d2ddaf940/pip-18.0-py2.py3-none-any.whl (1.3MB)
Installing collected packages: pip
Found existing installation: pip 18.1
Uninstalling pip-18.1:
Successfully uninstalled pip-18.1
Successfully installed pip-18.0
Virtualenv already exists!
Removing existing virtualenv...
Creating a virtualenv for this project...
Pipfile: /app/dpo-automation/Pipfile
Using /usr/local/bin/python (3.7.0) to create virtualenv...
Already using interpreter /usr/local/bin/python
Using base prefix '/usr/local'
/usr/local/lib/python3.7/site-packages/virtualenv.py:1041: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp
New python executable in /root/.local/share/virtualenvs/dpo-automation-b0iFxfPY/bin/python
Installing setuptools, pip, wheel...done.
Setting project for dpo-automation-b0iFxfPY to /app/dpo-automation
Making site-packages available...
Virtualenv location: /root/.local/share/virtualenvs/dpo-automation-b0iFxfPY
Installing dependencies from Pipfile...
Traceback (most recent call last):
File "/usr/local/bin/pipenv", line 11, in <module>
sys.exit(cli())
File "/usr/local/lib/python3.7/site-packages/pipenv/vendor/click/core.py", line 722, in __call__
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/pipenv/vendor/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python3.7/site-packages/pipenv/vendor/click/core.py", line 1066, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python3.7/site-packages/pipenv/vendor/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python3.7/site-packages/pipenv/vendor/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/pipenv/cli.py", line 435, in install
selective_upgrade=selective_upgrade,
File "/usr/local/lib/python3.7/site-packages/pipenv/core.py", line 1943, in do_install
pypi_mirror=pypi_mirror,
File "/usr/local/lib/python3.7/site-packages/pipenv/core.py", line 1322, in do_init
pypi_mirror=pypi_mirror,
File "/usr/local/lib/python3.7/site-packages/pipenv/core.py", line 807, in do_install_dependencies
pypi_mirror=pypi_mirror,
File "/usr/local/lib/python3.7/site-packages/pipenv/core.py", line 1375, in pip_install
package_name.split('--hash')[0].split('--trusted-host')[0]
File "/usr/local/lib/python3.7/site-packages/pipenv/vendor/requirementslib/models/requirements.py", line 704, in from_line
line, extras = _strip_extras(line)
TypeError: 'module' object is not callable
The command '/bin/sh -c cd ${APP_DIR} && pipenv run pip install --upgrade pip==18.0 && pipenv --site-packages install --skip-lock' returned a non-zero code: 1What I believe to be the problem are these lines:
Virtualenv already exists!
Removing existing virtualenv...
Creating a virtualenv for this project...
andrii-rubtsov
commented
6 years ago @BeyondEvil Try RUN pip install pip==18.0 before RUN pip install.
jayprakashdutta
commented
6 years ago File "/usr/local/lib/python3.6/dist-packages/pipenv/vendor/requirementslib/_compat.py", line 33, in do_import
_tmp = importlib.import_module(internal)
File "/usr/lib/python3.6/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "
During handling of the above exception, another exception occurred
whg517
commented
6 years ago https://pipenv.readthedocs.io/en/latest/advanced/#tox-automation-project
I also ran into this problem when I used pipenv on tox as a reference. I just installed dependent packages and haven't started doing anything else yet
tox.ini
[tox]
envlist = pipenv_test
[testenv:pipenv_test]
deps =
pipenv
commands =
pipenv install --dev$ tox --recreate
GLOB sdist-make: D:\workspace\development\python\pytest\mysite\setup.py
pipenv_test create: D:\workspace\development\python\pytest\mysite\.tox\pipenv_test
pipenv_test installdeps: pipenv
pipenv_test inst: D:\workspace\development\python\pytest\mysite\.tox\dist\mysite-0.1.zip
pipenv_test installed: certifi==2018.8.24,mysite==0.1,pipenv==2018.7.1,virtualenv==16.0.0,virtualenv-clone==0.3.0
pipenv_test run-test-pre: PYTHONHASHSEED='272'
pipenv_test runtests: commands[0] | pipenv install --dev
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.
Pipfile.lock (e7cb29) out of date, updating to (75f29b)...
Locking [dev-packages] dependencies...
ython\pytest\mysite\.tox\pipenv_test\lib\site-packages\pipenv\utils.py", line 402, in resolve_deps
req_dir=req_dir
File "d:\workspace\development\python\pytest\mysite\.tox\pipenv_test\lib\site-packages\pipenv\utils.py", line 250, in actually_resolve_deps
req = Requirement.from_line(dep)
File "d:\workspace\development\python\pytest\mysite\.tox\pipenv_test\lib\site-packages\pipenv\vendor\requirementslib\models\requirements.py", line 704, in from_line
line, extras = _strip_extras(line)
TypeError: 'module' object is not callable
ERROR: InvocationError for command 'D:\\workspace\\development\\python\\pytest\\mysite\\.tox\\pipenv_test\\Scripts\\pipenv.EXE install --dev' (exited with code 1)
___________________________________ summary ___________________________________
ERROR: pipenv_test: commands failedIs there any way to just solve it? thanks
Be sure to check the existing issues (both open and closed!), and make sure you are running the latest version of Pipenv.
Check the diagnose documentation for common issues before posting! We may close your issue if it is very similar to one of them. Please be considerate, or be on your way.
Make sure to mention your debugging experience if the documented solution failed.
Issue description
New version of pip breaks pipenv, exactly on this line https://github.com/pypa/pipenv/blob/51cbc2e2f76a7c60f879a608fd96e95faca35f2e/pipenv/vendor/pip_shims/shims.py#L101
Expected result
The
_strip_extrasnot be a module.Actual result
Steps to replicate
Provide the steps to replicate (which usually at least includes the commands and the Pipfile).
Please run
$ pipenv --support, and paste the results here. Don't put backticks (`) around it! The output already contains Markdown formatting.If you're on macOS, run the following:
If you're on Windows, run the following:
If you're on Linux, run the following: