Bug: Downloading mail archives from Mailman3 often times out
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the July 2001 download from https://mail.python.org/archives/list/python-list@python.org/ and compare complete, monthly, and smaller archive requests. Trace the archive download path and its timeout or generation behavior; done means the requested archive downloads successfully without timing out.
Written by the indexing model from the issue text.
Description
Describe the bug
I've been trying to download the mail archive for the python-list (comp.lang.python mirror) via https://mail.python.org/archives/list/python-list@python.org/ for history research purposes.
- The complete download directly fails with a message that the request will time out.
- The monthly download times out for a lot of months.
- Using the URL parameters, I then tried half month downloads and even weekly downloads, but still get time outs.
In essence there appears to be no usable way to download the complete archive using this Mailman3 interface.
Using the old Mailman2 interface from https://mail.python.org/pipermail/python-list/, the downloads succeed without any problems - essentially those are static files, not files which the server needs to generate upon request.
Is there anything which could be done about this (e.g. extending timeouts or increasing VM sizing parameters) ?
Thanks.
To Reproduce
- Go to https://mail.python.org/archives/list/python-list@python.org/
- Try to download e.g. July 2001
Expected behavior
A working download without timeouts.
URL to the issue
https://mail.python.org/archives/list/python-list@python.org/
Screenshots
""
Browsers
Chrome
Operating System
Windows
Browser Version
No response
Relevant log output
Additional context
No response
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 700
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 14
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/pythondotorg
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
python/pythondotorg#3137 · 2 comments ·
-
app/pages bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
python/pythondotorg#2677 · 3 comments ·
-
backend easy
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
python/pythondotorg#2453 · 8 comments ·
-
bug good-first-issue
Difficulty 4/5 3-5 days Newbie friendliness 30/100
python/pythondotorg#3125 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 74/100
python/pythondotorg#3094 · 5 comments ·
All issues in python/pythondotorg
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/skills#1811 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
speaches-ai/speaches#678 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
datalayer/mcp-compose#42 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UKGovernmentBEIS/inspect_evals#2523 ·