I installed 3.9 with pip last week, but i want to upgrade to 3.10. But pip install -U mailman postorius django-mailman3 hyperkitty mailman-web doesn't upgrade it.
Requirement already satisfied: mailman in ./venv/lib/python3.13/site-packages (3.3.9) Collecting mailman Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) ... a bunch of these ... INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) ...a bunch more...
-- Paul Tomblin
On 3/2/26 18:21, Paul Tomblin via Mailman-users wrote:
I installed 3.9 with pip last week, but i want to upgrade to 3.10. But pip install -U mailman postorius django-mailman3 hyperkitty mailman-web doesn't upgrade it.
Mailman core 3.3.10 was released to PyPI in October 2024 at any time
thereafter pip install mailman should have installed Mailman 3.3.10.
Requirement already satisfied: mailman in ./venv/lib/python3.13/site-packages (3.3.9)
I don't know why 3.3.9 would have been installed at all.
Collecting mailman Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB)
But it looks like here it's trying to install 3.3.10.
Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) ... a bunch of these ... INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) ...a bunch more...
Is there any conflict reported in this bunch more to force 3.3.9? What
if you do pip install mailman==3.3.10?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Tue, Mar 3, 2026, at 12:30 AM, Mark Sapiro wrote:
But it looks like here it's trying to install 3.3.10.
Requirement already satisfied: postorius in ./venv/lib/python3.13/site-packages (1.3.13) ... a bunch of these ... INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. Requirement already satisfied: python-dateutil>=2.0 in ./venv/lib/python3.13/site-packages (from mailman) (2.9.0.post0) ...a bunch more...
Is there any conflict reported in this
bunch moreto force 3.3.9? What if you dopip install mailman==3.3.10?
All the "...a bunch more..." lines are "Requirement already satisfied".
And here's what happens when I try to do as you suggested: (venv) $ pip install mailman==3.3.10 Collecting mailman==3.3.10 Using cached mailman-3.3.10-py3-none-any.whl.metadata (2.4 kB) Requirement already satisfied: aiosmtpd>=1.4.3 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.4.6) Requirement already satisfied: alembic!=1.7.0,>=1.6.2 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.18.4) Requirement already satisfied: atpublic in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (7.0.0) Requirement already satisfied: authheaders>=0.16 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (0.16.3) Requirement already satisfied: authres>=1.0.1 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (1.2.0) Requirement already satisfied: click>=8.0.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (8.3.1) Requirement already satisfied: dnspython>=1.14.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (2.8.0) Requirement already satisfied: falcon>=3.1.3 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (4.2.0) Requirement already satisfied: flufl.bounce>=4.0 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (4.0) Requirement already satisfied: flufl.i18n>=3.2 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (6.0.0) Requirement already satisfied: flufl.lock>=5.1 in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (9.0.0) Requirement already satisfied: gunicorn in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (25.1.0) Requirement already satisfied: lazr.config in ./venv/lib/python3.13/site-packages (from mailman==3.3.10) (3.1) INFO: pip is looking at multiple versions of mailman to determine which version is compatible with other requirements. This could take a while. ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13"
I guess I need to upgrade my python version?
-- Paul Tomblin
On 3/3/26 12:24, Paul Tomblin via Mailman-users wrote:
ERROR: Could not find a version that satisfies the requirement nntplib; python_version >= "3.13" (from mailman) (from versions: none) ERROR: No matching distribution found for nntplib; python_version >= "3.13"
I guess I need to upgrade my python version?
At
<https://gitlab.com/mailman/mailman/-/blob/master/pyproject.toml?ref_type=hea...>
we require standard-nntplib if the python version is >= 3.13. However
in Mailman 3.3.10 this line erroneously required nntplib rather than
standard-nntplib. Thus the failure.
I have noted before there are incompatibilities between Mailman <= 3.3.10 and Python 3.13. This is one of them. You could downgrade your Python to 3.12, but I recommend installing Mailman core from gitlab with
pip install git+https://gitlab.com/mailman/mailman@master
That version is compatible with Python 3.13.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro -
Paul Tomblin