Pipfile.lock out of date, but installation uses --system... re-building lockfile must happen in isolation. #2273
Comments
- Fixes #2219, #2273 Signed-off-by: Dan Ryan <[email protected]>
|
No idea if this is related, but I'm getting a version mismatch error when I run EDIT: I noticed in the trials that are succeeding, our pipenv is changing its version from 2018.05.18 to 11.10.1 (because someone pinned our pipenv version in the Pipfile to 11.10.1--not sure how it got installed since all of the previous |
|
@techalchemy I installed the latest master branch, but the issue is still present. |
|
Ok thanks for the update, guess this one wasn’t as simple. Still need to capture these with test coverage |
techalchemy
added
Type: Bug 🐛
|
@max-arnold are you still experiencing this? I can't reproduce this. |
|
Yes |
- Fixes #2273 - Hopefully for real this time Signed-off-by: Dan Ryan <[email protected]>
|
Can you try the fix I jsut put up? I'm not 100% sure it will work but hopefully |
|
|
Thanks. Guess I didn’t quite fix it ;) |
|
I'm also experiencing this. I'm on linux and used plain old virtualenv to create my env. python version is 3.5.3. Installed pipenv (pipenv==2018.5.18) inside the virtualenv and running it form there. |
|
@atleta You can work around this bug right now. Pipenv detects it is run in a virtualenv automatically and does the right thing. You don’t need to use |
|
@max-arnold ok, the new version definitely fixes it for real, I actually tested it first this time, sorry about that :) will have it in the release |
|
Thank you Dan! Works for me too: |
|
@uranusjr Maybe I'm misunderstanding the original report, but I haven't used the system flag. |
|
@atleta If you didn’t use |
|
@uranusjr @atleta there were a bunch of bugs with this implementation actually and they are all at least sort of related, but depending which bug you're talking about you might have seen an error message without passing in |
Brother! can you find any solution to this problem so please tell me that |
|
@MAbdullahAlvi I am not sure seeing as how the latest published version of pipenv Also I noticed you are using python 3.6 which is no longer supported. Best regards. |
pipenvcomplains about installation using --system flag and does not update lock file on subsequent package installs.$ python -m pipenv.help output
Pipenv version:
'2018.05.18'Pipenv location:
'/Users/user/.virtualenvs/quicktest/lib/python3.6/site-packages/pipenv'Python location:
'/Users/user/.virtualenvs/quicktest/bin/python'Other Python installations in
PATH:2.6:/opt/local/bin/python2.62.6:/opt/local/bin/python2.62.7:/opt/local/bin/python2.72.7:/opt/local/bin/python2.72.7:/usr/bin/python2.73.6:/opt/local/bin/python3.6m3.6:/Users/user/.virtualenvs/quicktest/bin/python3.63.6:/opt/local/bin/python3.63.6.5:/Users/user/.virtualenvs/quicktest/bin/python3.6.5:/opt/local/bin/python2.7.10:/usr/bin/python2.7.15:/opt/local/bin/python23.6.5:/Users/user/.virtualenvs/quicktest/bin/python33.6.5:/opt/local/bin/python3PEP 508 Information:
System environment variables:
TERM_SESSION_IDSSH_AUTH_SOCKCOLORFGBGITERM_PROFILEXPC_FLAGSLANGPWDSHELLTERM_PROGRAM_VERSIONTERM_PROGRAMPATHDISPLAYCOLORTERMCOMMAND_MODETERMHOMETMPDIRUSERXPC_SERVICE_NAMELOGNAMESHLVLOLDPWDHISTSIZEHISTFILESAVEHISTWORDCHARSEDITORDJROOTPYROOTPYLROOTJAVA_HOMEFPATHVIRTUALENV_PYTHONVIRTUALENVWRAPPER_PROJECT_FILENAMEVIRTUALENVWRAPPER_WORKON_CDVIRTUALENVWRAPPER_SCRIPTWORKON_HOMEVIRTUALENVWRAPPER_HOOK_DIRDOCBOOK_XSL_URLXML_CATALOG_FILESES_HOMEGOPATHNVM_DIRPS1VIRTUAL_ENV_PYTHONDONTWRITEBYTECODEPIP_PYTHON_PATHPipenv–specific environment variables:
Debug–specific environment variables:
PATH:/Users/user/.virtualenvs/quicktest/bin:/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/binSHELL:/opt/local/bin/zshLANG:ru_RU.UTF-8PWD:/tmpVIRTUAL_ENV:/Users/user/.virtualenvs/quicktestContents of
Pipfile('/private/tmp/Pipfile'):Contents of
Pipfile.lock('/private/tmp/Pipfile.lock'):{ "_meta": { "hash": { "sha256": "4fef9e909141947fb573b0345f2129099de0f89c3f36a5b8164a15fcc0fea9e8" }, "pipfile-spec": 6, "requires": { "python_version": "3.6" }, "sources": [ { "name": "pypi", "url": "https://pypi.org/simple", "verify_ssl": true } ] }, "default": { "pygments": { "hashes": [ "sha256:78f3f434bcc5d6ee09020f92ba487f95ba50f1e3ef83ae96b9d5ffa1bab25c5d", "sha256:dbae1046def0efb574852fab9e90209b23f556367b5a320c0bcb871c77c3e8cc" ], "index": "pypi", "version": "==2.2.0" } }, "develop": {} }Steps to replicate
The first installed package is locked just fine:
Subsequent package installs do complain about
--systemflag:The text was updated successfully, but these errors were encountered: