--selective-upgrade does not update hashes in Pipfile.lock #4626
Comments
|
I see this behavior too, with simply a $ pipenv --supportPipenv version: Pipenv location: Python location: Python installations found:
PEP 508 Information: |
|
I got still the same problem with pipenv version 2022.1.8. |
matteius
added
Type: Possible Bug
|
I was seeing a similar behaviour to what @jnsnow reported (i.e with Since there's no fix as of yet, my workaround was simply just deleting from the Pipfile.lock the block(s) of the package(s) that you actually wanna update. Seems when you run Disclaimer: I did not delete the blocks of their transitive dependencies in the Pipfile.lock, and they weren't changed after I ran Anyway, hope this helps. |
|
Sorry I haven't gotten back around to this yet, but this is really useful feedback. I am not sure that dropping those flags is going to make everyone happy, but I do know that the implementations of them are flawed, and its essentially pretty challenging to support such a feature. I personally think correct usage should be to set the specifiers in |
|
As long as dropping support does not entail removing the feature altogether. It is a pretty useful feature honestly when all your package versions are pinned, so I'd rather it be kept unsupported, than entirely removed. Anyway, I'll leave the contribution guidelines here in case anyone decides to work on it: |
|
My team has run into this a few times now when trying to upgrade only one package using This issue has caused us enough problems that we are considering moving away from |
|
@yodaldevoid I believe the issue is that |
|
@matteius If I understand correctly, you are suggesting that we pin dependencies in our Pipfile rather than relying on the pined versions in Pipfile.lock in conjunction with |
|
@yodaldevoid I am suggesting not to Pin all of your dependencies in your Pipfile, but rather figure out which ones are the reason why you are using The only reason I can see people are using this and keep-outdated, is they have things in the past that upgraded when locking the whole package group, that they feared are going to get changed, but this is due to not understanding what those things are and creating reasonably specifiers in the Pipfile. Another possible work around is move sensitive dependencies you don't want upgraded into their own package category and when you lock you exclude that category from being locked, but I still think Pipfile specifiers for top level dependencies make the most sense. |
|
|
Issue description
If I update a package with --selective-upgrade, I can not install the update with sync.
Steps to replicate
pipenv install 'django==2.2.18'
pipenv install --selective-upgrade 'django==2.2.19'
pipenv --rm
pipenv sync
Expected result
pipenv sync should install all packages from Pipfile.lock.
Actual result
$ pipenv --support
Pipenv version:
'2020.11.15'Pipenv location:
'/home/mogoh/.local/lib/python3.8/site-packages/pipenv'Python location:
'/usr/bin/python3'Python installations found:
3.8.6:/usr/bin/python3.83.8.6:/usr/bin/python3PEP 508 Information:
System environment variables:
SHELLSESSION_MANAGERWINDOWIDQT_ACCESSIBILITYKDED_STARTED_BY_KDEINITCOLORTERMXDG_CONFIG_DIRSXDG_SESSION_PATHNVM_INCGTK_IM_MODULELANGUAGEQT4_IM_MODULEMANDATORY_PATHJAVA_HOMESSH_AUTH_SOCKSHELL_SESSION_IDXMODIFIERSDESKTOP_SESSIONSSH_AGENT_PIDGTK_RC_FILESXCURSOR_SIZEXDG_SEATPWDXDG_SESSION_DESKTOPLOGNAMEXDG_SESSION_TYPEGPG_AGENT_INFOXAUTHORITYVIRTUALENVWRAPPER_SCRIPTGTK2_RC_FILESHOMELANGLS_COLORSXDG_CURRENT_DESKTOPKONSOLE_DBUS_SERVICEVIRTUALENVWRAPPER_WORKON_CDKONSOLE_DBUS_SESSIONDENO_INSTALLPROFILEHOMEXDG_SEAT_PATHKONSOLE_VERSIONCLUTTER_IM_MODULEKDE_SESSION_UIDNVM_DIRWORKON_HOMELESSCLOSEXDG_SESSION_CLASSPYTHONPATHTERMDEFAULTS_PATHLESSOPENUSERCOLORFGBGKDE_SESSION_VERSIONPAM_KWALLET5_LOGINVIRTUALENVWRAPPER_PROJECT_FILENAMEDISPLAYSHLVLNVM_CD_FLAGSQT_IM_MODULEXDG_VTNRXDG_SESSION_IDXDG_RUNTIME_DIRELECTRON_TRASHQT_AUTO_SCREEN_SCALE_FACTORXCURSOR_THEMEXDG_DATA_DIRSKDE_FULL_SESSIONPATHVIRTUALENVWRAPPER_HOOK_DIRDBUS_SESSION_BUS_ADDRESSKDE_APPLICATIONS_AS_SCOPENVM_BINOLDPWDKONSOLE_DBUS_WINDOW_PIP_DISABLE_PIP_VERSION_CHECKPYTHONDONTWRITEBYTECODEPIP_SHIMS_BASE_MODULEPIP_PYTHON_PATHPYTHONFINDER_IGNORE_UNSUPPORTEDPipenv–specific environment variables:
Debug–specific environment variables:
PATH:/home/mogoh/.yarn/bin:/home/mogoh/.deno/bin:/home/mogoh/.nvm/versions/node/v15.8.0/bin:/home/mogoh/.gem/ruby/2.5.0/bin:/home/mogoh/.cargo/bin:/home/mogoh/.local/bin:/home/mogoh/.cargo/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/binSHELL:/bin/bashLANG:de_DE.UTF-8PWD:/home/mogoh/tempContents of
Pipfile('/home/mogoh/temp/Pipfile'):Contents of
Pipfile.lock('/home/mogoh/temp/Pipfile.lock'):{ "_meta": { "hash": { "sha256": "931594d6e3f80b678b899b9419026dedb97c8880fe21c17c4297f8ed2ad1ee3e" }, "pipfile-spec": 6, "requires": { "python_version": "3.8" }, "sources": [ { "name": "pypi", "url": "https://pypi.org/simple", "verify_ssl": true } ] }, "default": { "django": { "hashes": [ "sha256:0eaca08f236bf502a9773e53623f766cc3ceee6453cc41e6de1c8b80f07d2364", "sha256:c9c994f5e0a032cbd45089798b52e4080f4dea7241c58e3e0636c54146480bb4" ], "index": "pypi", "version": "==2.2.19" }, "pytz": { "hashes": [ "sha256:83a4a90894bf38e243cf052c8b58f381bfe9a7a483f6a9cab140bc7f702ac4da", "sha256:eb10ce3e7736052ed3623d49975ce333bcd712c7bb19a58b9e2089d4057d0798" ], "version": "==2021.1" }, "sqlparse": { "hashes": [ "sha256:017cde379adbd6a1f15a61873f43e8274179378e95ef3fede90b5aa64d304ed0", "sha256:0f91fd2e829c44362cbcfab3e9ae12e22badaa8a29ad5ff599f9ec109f0454e8" ], "markers": "python_version >= '3.5'", "version": "==0.4.1" } }, "develop": {} }The text was updated successfully, but these errors were encountered: