I noticed that Django 4.2 is nearing EOL status in April (no specific day in April is given):
https://www.djangoproject.com/download/
I also noticed that there's a planned update to add support for 5.2 to mailman-web:
https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst
Is this expected to be released before 4.2 goes EOL? Is there a rough time line?
Thanks!
Let me expand on this, in that I am failing to get django 5.2 and mailman 3 components to work together in a python3.12 venv. Specifically, despite PIP looking like it understands that the requirements indicate that the allowable range for it's dependency on django is <5.3, pip uninstalls 5.2 and puts in 5.0.14
""" $ pip install git+https://gitlab.com/mailman/postorius@master Collecting git+https://gitlab.com/mailman/postorius@master Cloning https://gitlab.com/mailman/postorius (to revision master) to /tmp/pip-req-build-pq79umwc Running command git clone --filter=blob:none --quiet https://gitlab.com/mailman/postorius /tmp/pip-req-build-pq79umwc warning: redirecting to https://gitlab.com/mailman/postorius.git/ Resolved https://gitlab.com/mailman/postorius to commit 0eef9e5b1e36f9e630fe807d407e6ddcfd8e2bf6 Installing build dependencies ... done Getting requirements to build wheel ... done Preparing metadata (pyproject.toml) ... done Requirement already satisfied: django-mailman3>=1.3.13 in ./lib64/python3.12/site-packages (from postorius==1.3.13) (1.3.15) Requirement already satisfied: django<5.3,>=4.2 in ./lib64/python3.12/site-packages (from postorius==1.3.13) (5.2.11) Requirement already satisfied: mailmanclient>=3.3.3 in ./lib64/python3.12/site-packages (from postorius==1.3.13) (3.3.5) ... Collecting django<5.3,>=4.2 (from postorius==1.3.13) Downloading Django-5.0.14-py3-none-any.whl.metadata (4.1 kB) ... Downloading Django-5.0.14-py3-none-any.whl (8.2 MB) ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 8.2/8.2 MB 34.7 MB/s 0:00:00 Installing collected packages: django Attempting uninstall: django Found existing installation: Django 5.2.11 Uninstalling Django-5.2.11: Successfully uninstalled Django-5.2.11 Successfully installed django-5.0.14 """
Am I doing something wrong?
On 3/13/26 09:09, via Mailman-users wrote:
Let me expand on this, in that I am failing to get django 5.2 and mailman 3 components to work together in a python3.12 venv. Specifically, despite PIP looking like it understands that the requirements indicate that the allowable range for it's dependency on django is <5.3, pip uninstalls 5.2 and puts in 5.0.14
You have to also install django-mailman3 and hyperkitty from Gitlab as the released versions of these require django>=4.2,<5.1
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thank you! I didn't realize I had to update them simultaneously. I'll make note of that in the future.
To follow up on this. I was able to install all of these tools (postorius, hyperkitty, django-mailman3, etc.) through gitlab to run the latest version, but I'm hoping to get our instance to run on an official release, rather than directly from the master branch. Are there plans to have this in PyPI before Django 5.2 goes EOL next month?
Thanks
participants (2)
-
dlb-ml＠anl.gov -
Mark Sapiro