[MM3-users] Re: Upgrading other python packages than the mailman ones in a venv results in dependency conflicts

On Montag, 16. Dezember 2024 11:52:25 CET Odhiambo Washington via Mailman- users wrote:

On Mon, Dec 16, 2024 at 1:39 PM Ulf R. <ulf.rapphahn@offis.de> wrote:

...

Hello, I know this should be the way to upgrade: https://docs.mailman3.org/en/latest/upgrade-guide.html I have 3.3.10 installed. I saw that some python packages are outdated an tried this which install all outdated packages in a row: pip list --outdated --format=json | jq '.[].name' | xargs -n1 pip install -U One outdated package was django and this part happened:

vDownloading Django-5.1.4-py3-none-any.whl (8.3 MB) Installing collected packages: Django

Attempting uninstall: Django

Found existing installation: Django 4.2.16
Uninstalling Django-4.2.16:

  Successfully uninstalled Django-4.2.16

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. hyperkitty 1.3.12 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. mailman-web 0.0.9 requires django<4.3,>=4.0, but you have django 5.1.4 which is incompatible. postorius 1.3.13 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. django-mailman3 1.3.15 requires django<5.1,>=4.2, but you have django 5.1.4 which is incompatible. Successfully installed Django-5.1.4

So I made a roll back.

Is this really the only secure way to update the venv?: pip install -U mailman postorius django-mailman3 hyperkitty mailman-web

Correct!

...

May be yes and I have to ignore the rest? ;-)

Yes. Let them pull their own versions of dependencies.

OK. So what about --upgrade-strategy eager:

pip install -U --upgrade-strategy eager mailman postorius django-mailman3 hyperkitty mailman-web

Is that allowed/supported?

-- Best regards, Odhiambo WASHINGTON,

Mit freundlichen Gruessen, Andreas Vetter