You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running pipenv upgrade django==4.2.18 it only updates the default package and ignores the duplicate reference in the develop package.
In our Pipfile we currently have django==4.2.16 pinned. In our dev-packages we have packages that depend on django but the version is not explicitly specified. If we modify the Pipfile to be 4.2.18 and run pipenv lock it will correctly update the reference to django in the default and dev-packages sections, but it also pulls in the latest changes for all implicit dependencies.
Running pipenv upgrade django==4.2.18 upgrades django without pulling in any unrelated changes which is exactly what we are after, but it fails to update dev-packages.
Expected result
I would expect that since the lock command keeps the common dependencies between default and dev-packages in sync that the upgrade command would do the same.
Actual result
Here is the resulting diff when running pipenv upgrade django==4.2.18:
Issue description
When running
pipenv upgrade django==4.2.18
it only updates thedefault
package and ignores the duplicate reference in thedevelop
package.In our
Pipfile
we currently havedjango==4.2.16
pinned. In ourdev-packages
we have packages that depend ondjango
but the version is not explicitly specified. If we modify thePipfile
to be4.2.18
and runpipenv lock
it will correctly update the reference todjango
in thedefault
anddev-packages
sections, but it also pulls in the latest changes for all implicit dependencies.Running
pipenv upgrade django==4.2.18
upgradesdjango
without pulling in any unrelated changes which is exactly what we are after, but it fails to updatedev-packages
.Expected result
I would expect that since the
lock
command keeps the common dependencies betweendefault
anddev-packages
in sync that theupgrade
command would do the same.Actual result
Here is the resulting diff when running
pipenv upgrade django==4.2.18
:The
django
packages on line Pipfile.lock:2469 is still version4.2.16
. When we didn't notice this and did the following:We end up with the downgraded version.
Steps to replicate
Use attached files and just run
pipenv upgrade django==4.2.18
.Pipfile.txt
Pipfile.lock.txt
$ pipenv --support
Pipenv version:
'2024.4.1'
Pipenv location:
'/usr/local/lib/python3.11/site-packages/pipenv'
Python location:
'/usr/local/bin/python3.11'
OS Name:
'posix'
User pip version:
'24.3.1'
user Python installations found:
PEP 508 Information:
System environment variables:
PYTHON_SHA256
HOSTNAME
PYTHON_VERSION
PWD
HOME
LANG
GPG_KEY
TERM
SHLVL
PATH
_
OLDPWD
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PYTHONFINDER_IGNORE_UNSUPPORTED
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
:/src
Contents of
Pipfile
('/src/Pipfile'):Contents of
Pipfile.lock
('/src/Pipfile.lock'): (See attachment)The text was updated successfully, but these errors were encountered: